Resource
API Documentation Prompt
Overview, Authentication, Endpoints, Error Handling, Rate Limits — endpoint docs in an identical structure, with parameter tables and runnable examples forced.
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.
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
Resource
Changelog Prompt — User-Readable Change Logs
Added, Changed, Fixed, Removed, Security — changelog entries written as user-visible changes, not commit messages.
Resource
Database Migration Plan Prompt
Ship a schema change without downtime or data loss — an expand-migrate-contract migration plan with backward compatibility, ordering, and a reversal path.
Resource
Deployment Runbook Prompt
Turn a deploy into a runbook anyone can execute — ordered steps, preconditions, verification at each gate, and the rollback hook, instead of tribal knowledge.
Resource
Design System Spec Prompt — Components, States, and Accessibility
Turn UI requirements and component needs into a design-system spec: a component inventory with states, variants, responsive behavior, accessibility requirements, microcopy rules, and developer handoff notes.
Resource
FAQ Documentation Prompt
Every entry a "## Question?" heading with a self-contained answer — FAQs grouped by topic, phrased the way users actually ask.
Resource
Feature Flag Release Prompt
Decouple deploy from release — a feature-flag rollout plan with the flag's default, targeting, kill switch, and the cleanup that stops flags becoming permanent debt.
Resource
Handoff Completeness Review Prompt — What's Missing Before You Continue
Review a project handoff or onboarding package for what's missing — decisions, files, assumptions, constraints, risks, and next actions — and return a completeness score and a ready / not-ready verdict.
Resource
Landing Page Benefits Copy Prompt — Features Into Outcomes
Turn features, pains, and outcomes into benefit-led landing-page sections: a benefit headline, three to five benefit blocks, outcome bullets, objection handling, and the proof each claim still needs.
Resource
Landing Page Hero Copy Prompt — Headline, Subhead, and CTA
Turn product positioning into above-the-fold hero copy: a headline, subheadline, primary and secondary CTA, a trust cue, an objection-handling line, and three alternative headline angles to test.
Resource
Landing Page Social Proof & Objection Copy Prompt
Write trust, social proof, risk reversal, and objection-handling copy for a landing page — with proof placeholders and an explicit do-not-invent rule, so nothing is fabricated.
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.
Resource
Markdown Report Prompt
Purpose, Highlights, Details, Recommendations, Next Steps — recurring business reports with conclusions first and numbers in context.
Resource
Meeting Notes Document Prompt
Attendees, Decisions, Discussion, Action Items, Next Meeting — the notes document every meeting fills the same way.
Resource
Monitoring & Alerting Plan Prompt
Decide what to watch before you ship — the signals, thresholds, and alerts for a release, so a silent failure pages you instead of surfacing in a support ticket.
Resource
Permission Matrix Prompt
Make access auditable — a roles-by-actions matrix that shows exactly who can do what, exposes the gaps and over-grants, and becomes the spec the code is checked against.
Resource
Post-Deploy Smoke Test Prompt
Confirm a deploy is actually healthy — a short, ordered smoke-test checklist of the critical paths to verify in the first minutes after shipping.
Resource
PRD Prompt — Consistent Product Requirement Documents
Problem, Goals, Non-Goals, numbered Requirements, Risks, Timeline — PRDs identical in structure across every author and feature.
Resource
Product Validation Report Prompt
Consolidate the whole validation into one shareable report — the success metric, the evidence, the hit / partial / miss verdict, and the iterate / pivot / scale decision, in a form the team and stakeholders can act on.
Resource
README Prompt Template
Overview, Installation, Usage, Examples, Configuration — the README skeleton with required, runnable code examples.
Resource
Release Readiness Checklist Prompt
A go/no-go checklist for a release — config, secrets, migrations, comms, rollback, and monitoring all confirmed ready before you ship, ending in a clear GO or NO-GO.
Resource
Research Brief Prompt
Objective, Background, Findings, Recommendations, Open Questions — briefs where what was found and what to do stay clearly separated.
Resource
Schema Design & ERD Prompt — Entities, Relationships, and Keys
Turn product requirements and key entities into an ERD-ready schema spec: tables, fields, primary and foreign keys, relationships with cardinality, indexes, and constraints — with the modeling gaps named as open questions.
Resource
Sitemap & Site IA Spec Prompt — Pages, Navigation, and Structure
Turn website goals, audiences, content types, and conversion paths into a sitemap and information-architecture spec: navigation, a page inventory, hierarchy, URLs, user journeys, and an internal-linking plan.
Resource
Staged & Canary Rollout Prompt
Ship to a few before the many — a canary/staged rollout plan with cohorts, the metrics that gate each stage, and the auto-rollback condition.
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.
Resource
Zero-Downtime Deployment Prompt
Ship without a maintenance window — a deployment strategy (blue-green or rolling) that keeps the service up, handles in-flight requests, and stays compatible across versions.
Workflow
AI Project Architecture Workflow
Design a system's architecture on its real trade-offs instead of a confident diagram — put the model in an architect's seat, work the decisions one at a time, and write down the why.
Workflow
AI Database Design Workflow
Design a schema on its data, not a hunch — model the entities and relationships, set the constraints that protect integrity, plan indexes around real queries, then document the schema and migration.
Workflow
AI Auth & Identity Workflow
Design access control before you build it, not after a breach — choose the authentication approach, model the roles and permissions, review the design for gaps, then document the identity model.
Workflow
AI Integration & Webhook Workflow
Connect systems so they don't break each other — map the integration boundaries, design the event and webhook contracts, plan retries and failure handling, then document the integration.
Workflow
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.
Workflow
AI Architecture Recovery Workflow
Recover a legacy system's architecture before you change it — package the codebase context, explain the current structure, surface the risks and seams, then document the recovered architecture.
Workflow
AI Deployment & Release Workflow
Cross the gap between 'tests pass' and 'safe in production' — assess release readiness, plan the deploy and its rollback, and set up the monitoring and launch checks before you ship, not after.
Workflow
AI Project Handoff Workflow
Carry a project into a new chat, model, or teammate without the context evaporating — capture the state, distill what's worth keeping, and rebuild it as durable context on the other side.
Workflow
AI Product Validation Workflow
Find out whether the thing you shipped actually worked — define the success metric, plan the measurement, classify the real evidence, then render a verdict and an iterate / pivot / scale decision.
Workflow
AI Data Pipeline & ETL Workflow
Design a pipeline that moves data without corrupting it — map the sources and ingestion, design the transformation stages, set validation and quality gates, then document the pipeline and monitoring.
Workflow
AI Content Writing Workflow
Turn source material and a target audience into clear docs, help, or knowledge-base content — gather the material, outline the piece, write it section by section, then check it for clarity and gaps.
Workflow
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.
Workflow
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.
Workflow
AI Product Requirements Workflow
Turn a fuzzy business need into requirements a team can build from — interrogate the need into concrete requirements, shape them as user stories, and write the PRD.
Workflow
AI Content Strategy Workflow
Decide what to publish and why before you write a word — set the business goals and audience, map needs to topics, brief the priority pieces, then turn it into a content plan you publish against.
Workflow
AI Website Structure Workflow
Organize a site so people and crawlers find things — inventory the content, group it into a real hierarchy, design the sitemap and navigation, then document the information architecture for the build.
Workflow
AI Landing Page Copywriting Workflow
Write a landing page that converts, not one that just describes — sharpen the value proposition, draft the hero and benefits, answer objections at the CTA, then A/B the variants to pick the stronger.
Workflow
AI UI & Component Design Workflow
Structure a UI so it stays consistent as it grows — inventory the screens, break them into reusable components, specify the component system and its rules, then review the structure for drift.
Project
Build a SaaS MVP with AI
The full path from idea to a shipped SaaS MVP — define and scope the requirements, design the architecture, API, and data model, then build it reviewed, tested, secured, cost-controlled, and deployed.
Project
Build an AI Support Agent with AI
The full path to a support agent you can put in front of customers — write its instructions, ground it in your docs, route and handle tickets, then evaluate and cost-control it before it goes live.
Project
Build an AI Document Processing System with AI
The full path to an AI document processing system — define the use case, design the intake pipeline, extract fields from unstructured documents, classify and route them, pin the output contract, evaluate accuracy, then ship it monitored.
Project
Build an AI Content Moderation System with AI
The full path to an AI content moderation system — define the policy and label taxonomy, extract signals from user content, classify it against policy, emit structured decisions, evaluate false positives and negatives, wire enforcement and review queues, review abuse risks, then ship.
Project
Build an AI Research Assistant with AI
The full path to an AI research assistant — define its scope, organize the source corpus, ground responses in references, extract key facts, synthesize findings, check groundedness, then validate it for use.
Project
Build an AI Meeting Assistant with AI
The full path to an AI meeting assistant — define the use case, turn transcripts into structured notes, extract decisions and action items, classify follow-ups, write a shareable summary, evaluate accuracy, then ready it for the team.
Project
Build an API Backend with AI
The full path to a backend you can put clients on — define the requirements, design the architecture, API contract, data model, and access control, then build it reviewed, tested, secured, and shipped.
Project
Build a Company Website with AI
The full path to a business website that holds together — plan the content, structure the site, design the components, write the page copy, then ship it as one coherent whole.
Project
Modernize a Legacy Codebase with AI
The full path to taming an inherited codebase — understand it, document its architecture, pin its behavior with tests, then refactor, modernize, review, speed up, and ship it without breaking what works.
Project
Build a Documentation Website with AI
The full path to docs people can actually navigate — plan the doc set, structure the site, write the guides and the API reference, then ship it as a coherent documentation site.
Project
Build an AI Content Engine with AI
The full path to a content operation that runs, not a pile of posts — set the editorial strategy, research the topics, build a reusable template, then produce and QA structured pieces on repeat.
Project
Build a Programmatic SEO Site with AI
The full path to pages that rank at scale, not penalty bait — map the intents, build the data set, structure it, template the page, then QA before publishing hundreds.
Project
Build an AI Workflow Automation System with AI
The full path to automation that survives the real world — wire the integrations and triggers, design the control API, move the data through validated stages, evaluate the AI steps, then deploy.
Project
Build a Customer Support System with AI
The full path to a support operation, not just a bot — stand up the knowledge base, route the tickets, add the AI agent, integrate your stack, close the feedback loop, evaluate, and deploy.
Project
Build an Applicant Tracking System with AI
The full path to an applicant tracking system — model jobs, candidates, and hiring stages, generate job descriptions and screening prompts, parse résumés into structured data, design the hiring API, set roles, review security, then ship.
Project
Build a Booking System with AI
The full path to a booking and reservation system — model resources, availability, and reservations, design the booking API, set customer accounts, wire calendar and notification integrations, design the UI, review security, then ship.
Project
Build an Inventory Management System with AI
The full path to an inventory management system — model products, stock, locations, and movements, design the inventory API, set roles, plan supplier and POS integrations, design the UI, review data-integrity risks, then ship.
Project
Build an Internal Admin Panel with AI
The full path to an internal admin panel — model the operational data it manages, design the management API, define RBAC and admin permissions, design the tables and forms, review risky admin actions, then ship to trusted internal users.
Project
Build a Knowledge Base with AI
The full path to knowledge that's findable by people and AI — plan the taxonomy, structure it for search, write the articles, tag the metadata, make it retrievable, then ship it maintainable.
Project
Build a Marketplace with AI
The full path to a two-sided platform — define the buyer-and-seller requirements, model the data, design the API, build roles and permissions, wire integrations, design the UI, then test, secure, and ship it.
Project
Build a CRM with AI
The full path to a CRM that fits your sales process — define the contacts, deals, and pipeline, model the data that ties them together, then build the roles, integrations, and pipeline UI, and ship.
Project
Build an E-commerce Store with AI
The full path to a store you own end to end — model the catalog and orders, design the storefront and checkout, add customer accounts and payments, then secure it, test it, and ship.
Project
Build a Data Pipeline with AI
The full path to a pipeline that moves data without corrupting it — design the ingestion and transforms, extract and structure the sources, gate the quality, store it, then deliver and ship it monitored.
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.
Best for
- Producing documents in a fixed structure — headings, sections, and tables
- Consistent Markdown formatting across generated docs
- Output meant to drop straight into a README, wiki, or docs site
Not for
- Returning data for a program to parse — that is the JSON Output Prompt Builder
- Summarizing with fidelity rules — that is the Structured Summary Prompt
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.