Markdown templates
Ready-made Markdown documents that open straight into the editor, filled in and named. Each one is a structure worth getting right — a README that answers the questions people actually arrive with, a changelog someone can upgrade from. Everything happens in your browser; nothing is uploaded.
-
README template
Install, usage, an API table and contributing notes — the sections that stop your issue tracker filling up.
Open in the editor README.md
-
Markdown resume template
A CV in plain text: version it, diff it, and export a clean PDF whenever you need one.
Open in the editor resume.md
-
Meeting notes template
Decisions first, discussion second, actions in a table with owners and dates.
Open in the editor meeting-notes.md
-
Blog post template
Front matter, a structure that opens with the answer, and the sections readers actually quote.
Open in the editor blog-post.md
-
Changelog template
Keep a Changelog structure, semantic version headings, and comparison links that stay correct.
Open in the editor CHANGELOG.md
-
CLAUDE.md template
Commands, layout, conventions and the gotchas — the context an agent needs before its first edit.
Open in the editor CLAUDE.md
-
AGENTS.md template
Setup, commands, style and explicit boundaries — one file instead of a paragraph re-pasted into every prompt.
Open in the editor AGENTS.md
-
llms.txt template
Title, one-blockquote summary, annotated link sections — the proposed format, filled in.
Open in the editor llms.txt
What a template is here
A starting document, not a wizard. Opening one creates an ordinary tab in the editor with the text already in it — you rewrite the parts that matter, delete the parts that do not, and export whatever you end up with. There is no lock-in and nothing to undo, because it is just a Markdown file from the first keystroke.
The structures are opinionated on purpose. A README template that is only a heading and a blank line saves nobody any time; the value is in knowing which sections earn their place and what order a reader wants them in.
Why plain text for documents like these
A resume, a changelog and a set of meeting notes have the same three problems in common: they are edited under time pressure, they need to outlive whichever app you wrote them in, and they are often private. Markdown answers all three — the layout cannot break while you type, the file opens in anything, and here the conversion to PDF or Word happens on your own device rather than on someone's server.
Common questions
- How do I use one of these templates?
- Open it and the editor loads a copy pre-filled, named and ready to edit. It becomes an ordinary document in your list of open tabs — rename it, rewrite it, export it, or close it without saving.
- Do I need an account?
- No. There are no accounts on this site at all. The template is fetched by your browser and filled into the editor locally; nothing about it reaches a server.
- Will my edits be saved?
- Yes, in this browser. Documents autosave to local storage on your own device, so closing the tab and coming back keeps your work. They are not synced anywhere and are not readable by us.
- Can I export the finished document?
- Yes — PDF, Word, standalone HTML or Markdown, all from the editor's Export menu. Every conversion runs in your browser, which is what keeps an unpublished draft or a private resume off the network.
- Are the AI templates different from the others?
- Only in subject. CLAUDE.md, AGENTS.md and llms.txt are ordinary Markdown files that happen to be read by coding assistants and language models rather than by people, so the conventions around them are newer and less settled.
- Can I suggest a template?
- The list follows what people actually search for, so the useful ones tend to surface on their own. A template earns a place here when it has a real structure worth getting right, rather than being a blank file with a heading.