See what content is possible

Give your AI a brief about your product and readers, and see the formats, channels and routes that fit, each with what it takes.

How Content Atlas is built

AGENTS.md — content-atlas
content-atlas › AGENTS.md
1# AGENTS: content-atlas23Operating procedure for this worker. [PROFILE.md](PROFILE.md) owns its declaration, interfaces and authority. [INVARIANTS.md](INVARIANTS.md) owns required properties and verification. This file owns routing, execution, recovery and delivery.45## Routing67| Request / condition | Execution path / stop point |8| --- | --- |9| "What can we do for …", "what content works at …", a requirement without existing content | `.claude/skills/resolve-possibilities` → artifact with Steps, Links, checked Routes |10| Existing content supplied (list, sitemap, inventory), "what do we have", "what is missing", "where can this go" | `.claude/skills/map-existing-content` → artifact with Placement, Coverage, Steps, Links, checked Routes |11| A focus on a finished result ("owned and earned channels", "written formats", "B2B", "Secondary and Primary fits") | `.claude/skills/filter-possibilities` on that artifact → new artifact |12| A requirement with a focus and no artifact yet | resolve-possibilities or map-existing-content first, then filter-possibilities; the focus goes into filter.json |13| Which pieces to make, when, in what order | out of scope: planner; return the possibilities artifact as its input |14| Messages, claims, copy, production | out of scope: message owner, content producer |15| Adding or changing atlas values, fits, transformations, recipes | out of scope for a request; record the proposal in `handoff.md` |1617Use the simplest supported executor. Do not create additional agents or workflows for a request that a skill can complete.
mainUTF-8 · Markdown
SkillTransformation
filter-possibilitiesPossibilities artifact × params → a narrower possibilities artifact
map-existing-contentExisting pieces × atlas → placement, coverage and possibilities anchored on the pieces
resolve-possibilitiesRequirement × atlas → possibilities

Example

The LeanOS venture's content possibilities, produced with Content Atlas.

Claude CodeContent Atlas
Give me content possibilities for LeanOS as a whole venture. We build systems that operate with AI and engineer with AI, and we run our own venture that way. The aim is adoption of this way of working and my recognition as a practitioner, through practice in public on constructions that run. Our readers are practitioners developing AI workers and engineers building with coding agents. Show the reader states, formats, channels and routes that could reach them, so I can choose what to make.

Possibilities

artifacts/leanos-venture/possibilities.json

  • Customer States7Unaware · Problem-aware · Solution-aware · Product-aware
  • Audiences6Prospect user · Prospect champion · Prospect buyer · Prospect blocker
  • Formats78Blog post / article · Pillar page / topic hub · Case study · Whitepaper
  • Channels74Homepage · Blog · Resource / content hub · Product pages
  • Surfaces73Audio ad slot · Booth · Definition page · Email slot
  • Steps175Problem-led short video · Paid reach to a defined segment
  • Routes10Practitioners developing AI workers: explanation of a real construction → live workshop comparing approaches → the construction open to examination
What you getYou’ll need
The atlas: 148 formats, 175 channels and 11 reader stages, for your AI to work from.An agent that reads skills, such as Claude Code or Codex
3 skills: explore a content question, map the content you have, narrow a result.Python 3.10 or later, with openpyxl
Format transformations, to see what one piece can become.Git, to copy the repository
Each result as a workbook to read, JSON to reuse and a summary.

Get it

Licence
MIT, for your own ventures and client work. Copy, change and share it.
Access
The public GitHub repository, with no purchase or sign-up.
Updates
Released to the public repository.
Help
Raise an issue on the repository.