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.
Build prompts that produce documents in a fixed structure — headings, sections, and tables.
The contract that stops AI documents from restructuring themselves: a pinned section skeleton, forced tables, and strict consistency rules.
Overview, Installation, Usage, Examples, Configuration — the README skeleton with required, runnable code examples.
Overview, Authentication, Endpoints, Error Handling, Rate Limits — endpoint docs in an identical structure, with parameter tables and runnable examples forced.
Added, Changed, Fixed, Removed, Security — changelog entries written as user-visible changes, not commit messages.
Ship a schema change without downtime or data loss — an expand-migrate-contract migration plan with backward compatibility, ordering, and a reversal path.
Turn a deploy into a runbook anyone can execute — ordered steps, preconditions, verification at each gate, and the rollback hook, instead of tribal knowledge.
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.
Every entry a "## Question?" heading with a self-contained answer — FAQs grouped by topic, phrased the way users actually ask.
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.
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.
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.
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.
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.
Purpose, Highlights, Details, Recommendations, Next Steps — recurring business reports with conclusions first and numbers in context.
Attendees, Decisions, Discussion, Action Items, Next Meeting — the notes document every meeting fills the same way.
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.
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.
Confirm a deploy is actually healthy — a short, ordered smoke-test checklist of the critical paths to verify in the first minutes after shipping.
Problem, Goals, Non-Goals, numbered Requirements, Risks, Timeline — PRDs identical in structure across every author and feature.
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.
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.
Objective, Background, Findings, Recommendations, Open Questions — briefs where what was found and what to do stay clearly separated.
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.
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.
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.
Overview, Key Concepts, How It Works, Usage, Troubleshooting — docs pages with the same shape for every feature, and code in every usage section.
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.