Prompt Engineering

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.

Open in Markdown Output Builder

Overview

Ask a model for "a comparison document" five times and you get five structures. The markdown output contract fixes that: a "# " title rule, named "## " sections in a pinned order, table rules that refuse prose-collapse, and a strict consistency block — every section used, exact heading text, nothing merged. This resource loads the structure-enforcement showcase: a feature comparison whose Comparison Table section MUST come back as a real markdown table, identical columns every run.

How to use this resource

Generate once per document type

The prompt is the template — reuse it every time that document gets written.
Watch the table contract

Header row, separator row, one row per item, same columns, "—" for blanks — the rules that keep a table a table.
Keep Strict for parseable docs

Exact heading text is what lets scripts, diffs, and reviewers rely on the structure.

Why This Works

Named sections with jobs beat "structure it nicely" by an order of magnitude
The never-collapse rule directly counters the model's strongest formatting habit
Strict consistency turns a one-off document into a reusable template

Best for

Documents that get diffed, templated, or parsed downstream
Teams generating the same document type repeatedly
Anyone whose comparison tables keep dissolving into paragraphs

Not for

Compressing an existing text — that's the Structured Summary Prompt
Machine-parseable data contracts — that's the JSON Output Prompt Builder

Use cases

Getting the same document skeleton on every run
Forcing real markdown tables for comparisons
Pinning heading text so downstream tooling can parse it

FAQ

How do I stop AI comparison tables from collapsing into paragraphs?

The TABLE RULES block forces a real table wherever content compares items. It requires a header row, a separator row, one row per item, the same columns every run, and '—' for empty cells, and states you must never collapse a table into prose. Generate this prompt once, paste it into your assistant, and the Comparison Table section comes back as an actual markdown table.

How do I make an AI document use the same headings every time?

The DOCUMENT STRUCTURE pins four sections in order — ## Overview, ## Comparison Table, ## Strengths & Trade-offs, ## Recommendation — and the CONSISTENCY RULES demand the exact heading text with no rewording, no merging, and no omitting. That fixed skeleton is what lets a downstream diff, script, or reviewer rely on the structure across runs.

Should I use this or a JSON output prompt for machine-parseable data?

Use this for human-readable markdown documents; for a strict data contract reach for the JSON Output Prompt Builder instead. This template locks prose sections and tables with OUTPUT RULES like 'Do not wrap the document in code fences' and a MARKDOWN RULE of 'No HTML tags — pure markdown', which is document structure, not a typed data schema a program consumes directly.

Customize This Resource

Opens this setup in Markdown Output Builder. Generate to get the full markdown prompt — then adjust the sections, table rules, and consistency level.

Open in Markdown Output Builder

Prompt Template

Copy it as-is, or use Open in Markdown Output Builder to load it pre-filled and customize it with your own context.

TASK
Compare competing options feature by feature for a buying decision.
Produce a new markdown document — there is no source text to summarize.

DOCUMENT
The document follows a custom structure defined below.

DOCUMENT STRUCTURE
Start with one "# " title line, then use exactly these sections, in this order:
## Overview
What is being compared and why.
## Comparison Table
Feature-by-feature comparison of all options.
## Strengths & Trade-offs
Where each option wins and loses.
## Recommendation
Which option for which situation.

MARKDOWN RULES
- One "# " title at the top; every section below it is a "## " heading.
- Use markdown lists for enumerations — no walls of prose.
- No HTML tags — pure markdown.

TABLE RULES
- Where content compares items, options, or features, you MUST use a markdown table.
- Every table needs a header row, a separator row, and one row per item — never collapse a table into prose.
- Keep the same columns for every row; use "—" for cells with no value.

CODE RULES
- Do not include code blocks.

CONSISTENCY RULES
- Use every section defined above.
- Keep the section order exactly as given.
- Do not omit headings, even when a section is short.
- Do not merge sections.
- Use the exact heading text as defined — no rewording.

OUTPUT RULES
- Return only the markdown document — no preamble, no closing commentary.
- Start directly with the "# " title line.
- Do not wrap the document in code fences.

More resources from Markdown Output Builder

Resource

README Prompt Template

Overview, Installation, Usage, Examples, Configuration — the README skeleton with required, runnable code examples.

Engineering

Resource

API Documentation Prompt

Overview, Authentication, Endpoints, Error Handling, Rate Limits — endpoint docs in an identical structure, with parameter tables and runnable examples forced.

Engineering

Resource

Changelog Prompt — User-Readable Change Logs

Added, Changed, Fixed, Removed, Security — changelog entries written as user-visible changes, not commit messages.

Engineering

Resources that pair well

Resource

Executive Summary Prompt

Summary, Why It Matters, What Happens Next — the executive summary contract for readers who will never open the source.

Operations

Resource

Force JSON Output from AI

Stop getting 'Sure, here is the JSON…' — the output-contract pattern that forces models to return only parseable JSON: schema, example, and a strict rule block.

Prompt Engineering

Resource

Fix Invalid JSON from AI

The JSON won't parse and you can't see why. Deterministic cause-sniffing — trailing commas, single quotes, unclosed brackets — and the repair prompt that fixes it.

Engineering

Related tools

Tool

Markdown Output Builder

Build prompts that produce documents in a fixed structure — headings, sections, and tables.

Structured Output

Projects that use this resource

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.

6 stages Content & SEO

Guides for this resource

Guide

How to Keep AI Output Format Consistent

The AI nails your format once, then the next output adds a "Sure, here's…" wrapper, renames a field, turns the table into bullets, and drops a section. Here's how to write the format as a contract and catch the drift when it happens anyway.

Structured Outputs & JSON

Tip: Save time by exploring related resources and tools that integrate with this resource.