Prompt Anatomy spans education, field notes, and implementation tools. Each property has a job. The mistake teams make is treating every URL as the same product—copying playbook text into training slides, or buying a subscription when a free framework article already answers the design question. This map clarifies where to read, where to discover, where to practice, and what to ignore when you are building governed AI workflows under real compliance pressure.
Four properties that matter first
Most readers need four surfaces to start. For framework reading paths by role, see Prompt Anatomy Foundations. Everything else in the table below is a specialized workflow product—not a substitute for the blog or the app.
promptanatomy.blog (this site)
Role: Read. Long-form frameworks, governance playbooks, templates, case studies, and opinion primers that explain why and how to implement AI with owners, eval gates, and audit trails. Content is free, searchable, and updated in place as the field matures.
Use the blog when you are diagnosing chaos, designing a workflow, writing a RACI, or preparing a risk forum agenda. Articles link to each other in hub-and-spoke clusters—start with 10 Signs Your Company Is Vibe Prompting if you are not sure where you sit.
The blog does not host hands-on labs, graded exercises, or account-based progress tracking. It also does not replace Legal review or your internal policy packs—it gives you the vocabulary and checklists to have those conversations with IT and counsel in the same room.
promptanatomy.app
Role: Practice and buy. Paid training, methodology modules, and pricing for teams that want structured practice after reading frameworks on the blog. The app is where prompts, context layers, and workflow steps become repeatable drills—not one-off chat experiments.
Use .app when a playbook on the blog resonated and you need your team to execute the same steps under feedback: registry discipline, canvas completion, eval case design. Free blog content points here when standardization is the next stage; it is the intentional conversion surface, not a duplicate article archive. For what shipped on the hub—checkout, access model, and six-module training—see Shipping Prompt Anatomy.
If you are deciding whether to subscribe, read the relevant playbook first on .blog. Training without a documented workflow ID on your side still produces enthusiastic individuals—not operational AI.
promptanatomy.site
Role: Discover and try. Official marketing site with the nine-domain journey map, interactive five-part Anatomizer (Persona, Context, Variables, Instructions, Constraints), and a 60-second maturity quiz with tier and domain recommendation. Launched 2025-04-12; see Prompt Anatomy Marketing Site Launch for the field note and sister repo.
Use .site when a sponsor or new teammate needs the ecosystem story in one sitting—not when you need eval gates, RACI worksheets, or audit trail templates. Those live on .blog. The Anatomizer teaches prompt shape; production still requires registry discipline and owners documented in your playbooks.
promptanatomy.cloud
Role: Enter — first AI lesson. promptanatomy.cloud is a free, no-account interactive lesson: five-part prompt framework, 2-minute practice, quick send check before depth templates, dual prompt library, and a short quiz. Launched 2026-04-29; see Quick Send Check First — The First AI Lesson on promptanatomy.cloud for the field note and sister repo DITreneris/lead. The site does not call an AI API; visitors copy prompts into external tools.
Use .cloud when someone needs structured first steps and a send gate habit—not when you need K–12 prompt structure (.online), executive brief cadence (.ceo), or team governance playbooks alone. Optional EN/LT PDF summaries ship from the same property; they do not replace blog frameworks or .app training.
promptanatomy.ceo
Role: Manage — executive operations brief. AI Operations Center is a free, no-account web app that assembles structured CEO/COO prompts across DAILY, WEEKLY, and STRATEGIC modes with Fast, Deep, and Board output depth. Launched 2026-04-09; see The Weekly CEO Brief Pattern for the playbook and sister repo DITreneris/ceo. The site does not call an AI API; executives copy prompts into ChatGPT, Claude, or Gemini and log decisions themselves.
Use .ceo when leadership needs a weekly operating cadence—not when you need K–12 prompt structure (.online) or team governance playbooks alone. Optional paid PDF playbooks ship from the same property; they do not replace blog frameworks or .app training.
promptanatomy.online
Role: Try (K–12 vertical). Classroom Prompt Builder is a free, no-account web app that assembles structured prompts for US K–12 teachers across five modes—lesson, assessment, tasks, presentation, and strategy. Launched 2026-05-15; see Classroom Prompt Builder Launch for the field note and sister repo. The site does not call an AI API; teachers copy prompts into ChatGPT, Claude, or Gemini and verify output before classroom use.
Use .online when the question is teacher-facing prompt structure—not when you need enterprise governance playbooks or team training checkout. Those stay on .blog and .app. Optional paid PDF guides ship from the same property; they do not replace blog frameworks.
promptanatomy.info
Role: Use — daily workflow library. promptanatomy.info is a free, no-account static library with eight org-analysis prompts across LT, EN, ET, LV, and JA. Visitors copy structured prompts into external AI tools; the site does not call an AI API. Production cutover shipped 2026-05-29 (v1.4.0); see Who Orchestrates the Builders — Shipping promptanatomy.info for the field note and sister repo DITreneris/automation.
Use .info when practitioners need org-context prompts and a daily library—not when you need first-touch onboarding (.cloud), executive cadence (.ceo), or team governance playbooks alone. A closed-loop builder agent system localized UI, UX, and prompt copy across five locales; finishing the library does not replace workflow IDs or eval gates on your side.
promptanatomy.help
Role: Hire — HR hiring prompts. promptanatomy.help is a free, EN-only static site with ten structured hiring prompts for US recruiters—sourcing, screening, structured interviews, scorecards, and decision messaging. Launched 2026-06-24; see Hiring Prompts Without the Data Leak for the field note and sister repo DITreneris/personalas. The site does not call an AI API; recruiters copy prompts into ChatGPT, Claude, or Gemini and keep candidate data out of the builder.
Use .help when the question is recruiter-facing prompt structure with candidate-data boundaries—not when you need enterprise governance playbooks or an applicant-tracking system. Optional paid PDF guides ship from the same property; they do not replace blog frameworks.
promptanatomy.pro
Role: Decide — executive decision OS. promptanatomy.pro is an open-source (MIT) Executive OS that compiles CEO/COO decision prompts—Global Context, executive modules, clarity practice, a safety check, and a printable Max Value Kit. Launched 2026-07-16; see The Prism Test for Executive Decisions for the field note and sister repo DITreneris/leader. The site does not call an AI API; leaders copy prompts into external tools and own the decision.
Use .pro for higher-stakes allocation and scaling decisions—not the weekly operating cadence, which lives on .ceo (The Weekly CEO Brief Pattern). Manage and Decide are different jobs; do not merge the two executive surfaces.
@prompt_anatomy (Telegram channel)
Role: Broadcast / Learn — curriculum CMS. The open sister repo DITreneris/telegram collects 234 micro-lessons—copy, PNGs, and polls—on Vercel (web/, publish API), syncs them to a delivery manifest, and broadcasts today via @prompt_anatomy. An admin-only queue bot on Railway orchestrates /next, schedule, and persisted state. See Manifest Before You Broadcast for the field note.
Use the channel when you want habit-shaped exposure—short lessons between meetings, not a forty-five-minute LMS block. It is not training checkout (.app), the enter lesson (.cloud), or satirical play (.lol). Primary conversion CTA remains promptanatomy.app; curated posts may link to .blog deep reads via the sister repo crosswalk.
promptanatomy.lol
Role: Play. Corporate Ladder is a satirical office-climb game in Telegram—entertainment and brand flavor, not an implementation path. It soft-launched 2026-06-15 and is listed on tApps Center; see Corporate Ladder Soft Launch for the live field note. For the deployment stack, see Telegram Game Stack.
Treat .lol as optional. Leaders and implementers should not confuse game engagement with implementation maturity. If your team cites .lol in a procurement deck, you are probably avoiding the canvas.
Full property map
The table below lists specialized surfaces. They extend the core read → practice path; they do not replace it.
| Property | Role |
|---|---|
| promptanatomy.app | Practice — training, methodology, pricing |
| promptanatomy.blog (this site) | Read — frameworks, field notes, templates, case studies |
| promptanatomy.site | Discover — ecosystem story, Anatomizer, maturity quiz |
| promptanatomy.online | Try (K–12) — free Classroom Prompt Builder; optional PDF guides |
| promptanatomy.lol | Play — Corporate Ladder (satirical; not for ops) |
| promptanatomy.cloud | Enter — first AI lessons; see field note |
| promptanatomy.info | Use — daily workflow library; see field note |
| promptanatomy.space | Create — marketing content system |
| promptanatomy.help | Hire — HR hiring prompts; see field note |
| promptanatomy.ceo | Manage — operations center |
| promptanatomy.pro | Decide — executive decision OS; see field note |
| @prompt_anatomy | Broadcast / Learn — curriculum channel; see field note |
How to navigate without duplication
Follow this sequence once—not every property on day one.
- Diagnose with 10 Signs and the Foundations series.
- Design one workflow on the AI workflow canvas using blog playbooks.
- Practice the same workflow in training on promptanatomy.app when your team is ready to standardize.
- Specialize into
.info,.space, or other products only when a named workflow needs that vertical—not because a new domain appeared in a vendor demo.
For outcome framing before you buy anything, read From Prompts to Business Outcomes.
Rule of thumb: if two properties answer the same question, prefer the blog for depth and .app for drills. Never copy playbook prose into Slack and call it training—link the article, then assign the lab.
Operator lab builds (sister repos, not promptanatomy.* domains) are documented as Implementation Notes field notes—e.g. the Critique Agent trilogy (Part 1 measurement, Part 2 validation, Part 3 cross-repo field test), BTC Buzz Bot, and the Telegram curriculum CMS (DITreneris/telegram). They prove publish loops, manifest discipline, and audit patterns; the curriculum channel is also listed in the table above.
