API Documentation Prompt
Overview, Authentication, Endpoints, Error Handling, Rate Limits — endpoint docs in an identical structure, with parameter tables and runnable examples forced.
View Resource →Structured Output
Markdown Output Builder
Stop documents that reorder themselves every run. Define the document type and its section skeleton, set the table, code, and consistency rules — and get a markdown prompt that returns the same structure every time. READMEs, PRDs, docs, reports. Runs entirely in your browser.
What gets produced, and for whom? E.g. "Create consistent product requirement documents."
Document Sections *
The document's heart: every section with a title and the job it must do. Reorder with ↑ ↓.
Suggested for Custom
Document Preview (live skeleton — not the output)
Markdown Output Prompt
Changelog Prompt — User-Readable Change Logs
Added, Changed, Fixed, Removed, Security — changelog entries written as user-visible changes, not commit messages.
View Resource →FAQ Documentation Prompt
Every entry a "## Question?" heading with a self-contained answer — FAQs grouped by topic, phrased the way users actually ask.
View Resource →Markdown Output Prompt — Lock the Document Structure
The contract that stops AI documents from restructuring themselves: a pinned section skeleton, forced tables, and strict consistency rules.
View Resource →Markdown Report Prompt
Purpose, Highlights, Details, Recommendations, Next Steps — recurring business reports with conclusions first and numbers in context.
View Resource →Meeting Notes Document Prompt
Attendees, Decisions, Discussion, Action Items, Next Meeting — the notes document every meeting fills the same way.
View Resource →PRD Prompt — Consistent Product Requirement Documents
Problem, Goals, Non-Goals, numbered Requirements, Risks, Timeline — PRDs identical in structure across every author and feature.
View Resource →README Prompt Template
Overview, Installation, Usage, Examples, Configuration — the README skeleton with required, runnable code examples.
View Resource →Research Brief Prompt
Objective, Background, Findings, Recommendations, Open Questions — briefs where what was found and what to do stay clearly separated.
View Resource →Technical Documentation Prompt
Overview, Key Concepts, How It Works, Usage, Troubleshooting — docs pages with the same shape for every feature, and code in every usage section.
View Resource →AI Production Incident Workflow
Work a live production incident in the right order — triage and stabilize first, then find the cause, then write the summary and postmortem — so the fire is out before the writeup begins.
View Playbook →AI Meeting Notes Workflow
Turn a meeting transcript into notes people actually use — a faithful summary, the action items pulled out and assigned, and a clean shareable format.
View Playbook →AI Code Documentation Workflow
Generate documentation that matches the code instead of drifting from it — have AI explain what the code really does, write it up as structured docs, then validate the format holds.
View Playbook →How it works
Describe the document goal, pick the document type — README, PRD, technical documentation, report, FAQ, changelog, meeting notes, research brief, blog outline, or custom — and build the section skeleton: every section with a title and the job it must do. The document type adds type-specific rules to the prompt (FAQs force the "## Question?" format, PRDs number their requirements) and suggests the sections that type usually carries — add them with one click. Set the table mode (Required forces real markdown tables for comparisons), code block handling (Require suits READMEs and tech docs), and the consistency level — the tool's core value, with Strict pinning every section, the exact order, and the exact heading text. The live preview shows the document skeleton your prompt will enforce. Click Generate Markdown Prompt and reuse the result for every document of that type. Nothing leaves your browser.
Use cases
- READMEs and technical docs with the same structure across every project
- PRDs whose sections never go missing between authors
- Reports and research briefs that look identical every cycle
- Changelogs and FAQs that keep their format at volume
Pro tips
- Section descriptions are contracts, not labels: "Decisions made, one per bullet" produces a different document than a bare "Decisions" heading. Write what the section must contain — and what it must not.
- Use Strict consistency when documents get compared or diffed — identical structure is what makes ten PRDs reviewable in one sitting.
- Required Tables earns its keep on comparisons: models love collapsing tables into prose, and the "never collapse a table into prose" rule is the counterweight.
- For API docs and READMEs, pair Require Code Examples with Strict: "usable as written — no pseudo-code" stops the placeholder-snippet habit.
FAQ
Does this tool generate the document?
No — it generates the markdown PROMPT. You define the document's structure once (sections, tables, code, consistency), generate, and reuse the prompt every time that document type gets written. The payoff is consistency: the model returns the same skeleton every run instead of reinventing the structure.
How is this different from the Structured Summary Prompt?
Direction. The Structured Summary Prompt compresses an EXISTING source — every rule it has exists because there's a text to stay faithful to. This tool structures NEW documents the model writes from scratch: there's no source, so the rules are about structure, format, and consistency instead of fidelity. Same family, opposite direction.
And how is it different from the Prompt Formatter?
The Prompt Formatter restructures the PROMPT itself — your messy instructions become organized instructions. This tool defines the structure of the AI's ANSWER. One works on what you send; the other contracts what comes back.
What does the consistency level actually change?
The CONSISTENCY RULES block. Flexible treats your sections as a guide. Standard requires every section in order and bans new top-level sections. Strict adds the full pin: no omitted headings even when short, no merged sections, and the exact heading text as defined — the level you want when documents get compared, diffed, or templated.
When should I force tables?
Whenever the content compares things: feature matrices, option comparisons, parameter lists, PRD requirement tables. Models habitually collapse tables into paragraphs; Required Tables makes the table a contract — header row, separator row, one row per item, same columns throughout, "—" for empty cells.
Why does the document type matter if I define my own sections?
Because the type carries rules that aren't sections: an FAQ must format every entry as a "## Question?" heading, a changelog writes user-visible changes instead of commit messages, a PRD numbers its requirements so reviews can reference them. The type also suggests the standard sections — but your section list always wins; the suggestions are one-click additions, not impositions.