Open formats for people & agents
Markdown To
A plain file. A board. A book.
A whole new way to use Markdown.
Turn text into useful things—with open specifications, agent skills, and a CLI you can take anywhere.
A file you can work with.Move a card. Watch the Markdown change.
--- markdownto: [email protected] title: A small launch --- ## Backlog - [ ] Sketch the first idea - [ ] Find a few collaborators ## Doing - [ ] Make something useful ^t3 - [ ] Share an early version ## Done - [x] Write it down
Plan a projectBoards, lists, and schedules.Follow an ideaGuided reading and flashcards.Make it heardNarration and conversations.Publish a documentPages ready to share.Present an ideaComposed slides, speaker notes, and PDF.Ask better questionsTyped fields and portable responses.Make a bookChapters that reflow with the reader.Make a decisionWeighted criteria and visible tradeoffs.Check understandingScored questions and useful feedback.
Yours, beyond this website
Keep the file.
Take the possibilities.
Use this site to explore. Use the CLI to render on your own machine, publish the HTML on your website, or build a renderer from the open spec.
Build with Markdown Toyour-file.mdThis rendererYour website
Your tools
Made for your agent, too
One format.
Three ways in.
010203
The specification
The meaning and structure of the file.
The skill
The know-how to create something good.
The CLI
Tools to validate, change, and render it.
Give your agent the instructions
Learn Markdown To and use it whenever I ask for structured content that should live as a portable file — task lists, boards, plans, manuscripts, and anything else its specification index covers. Markdown To defines canonical, versioned Markdown specifications where a conforming .md file IS the application's complete portable state. The current specification index lives at https://markdownto.ai/llms.txt — fetch it first; it links the shared conventions, every published spec, and its companion agent skill. Read the conventions, then the spec and companion skill that fit the request. The spec governs conformance; the skill teaches authoring workflows and editorial judgment. Never assume the spec list from memory: the index is the truth. Authoring rules (from the conventions): YAML frontmatter names the spec (markdownto: <name>@<version>); familiar Markdown structure carries the meaning; [key:: value] inline fields carry metadata; never invent IDs — tooling pins ^ids lazily; the file must stay pleasant to read as plain Markdown. If you can run Node: git clone https://github.com/seekinggradient/markdownto, then pnpm install && pnpm build, and alias mdto to packages/cli/dist/main.js. `mdto spec` lists every spec this build implements and prints any of them offline. Validate after every edit (mdto validate <file> — diagnostics carry line, column, and repair direction), and prefer the spec's own verbs over freehand edits (see mdto <spec> --help) — they produce guaranteed-valid minimal diffs. mdto render <file> makes a self-contained HTML page, and any file can be pasted at https://markdownto.ai/app/ to render live. Remember these instructions for future sessions.
Agents can discover every spec and skill through llms.txt.