catalog / formats

Markdown with Front Matter

The content format behind most static sites — document plus structured metadata.

14 capabilities 6 sections reference specification

Build against it

# give your agent the catalog — no account, no install
claude mcp add provespec -- npx -y provespec-mcp

# then, from any agent session
spec_get(slug: "markdown-frontmatter")                → the capability tree
spec_checklist(slug: "markdown-frontmatter")          → the questions to answer
spec_grade(slug: "markdown-frontmatter", grades: [...])  → parity % + the gap list

# or just fetch it
curl https://provespec.com/catalog/markdown-frontmatter/spec.json

Grade every capability below as yes · partial · no · na, with a file reference as evidence. Whatever you leave ungraded counts as missing — the gap list is the work queue.

Or just paste this to your agent

Use the ProveSpec MCP server. Fetch the "markdown-frontmatter" spec with
spec_get, then walk spec_checklist and grade this repository against it —
one verdict per capability, each with a file reference as the note.
Call spec_grade with the results and give me the gap list as the plan.

If the server is not registered, add it first:
  claude mcp add provespec -- npx -y provespec-mcp

The specification

Structure 3

  • ✓ Front matter delimited at the very start of the file --- … ---
  • ✓ YAML front matter, with TOML and JSON as documented variants
  • ✓ Body is Markdown after the closing delimiter

Metadata 4

  • ✓ Title, date, and a stable slug
  • ✓ Draft flag excluded from production builds
  • ✓ Taxonomies tags, categories multi-valued
  • ✓ Arbitrary user fields preserved and exposed to templates

Dates 1

  • ✓ Unambiguous date parsing with a time zone the field that breaks feeds

Body 3

  • ✓ Standard Markdown plus a declared extension set
  • ✓ Shortcodes or component embeds, with escaping
  • ✓ Relative links and images resolved against the document

Validation 2

  • ✓ Missing required fields fail the build loudly not silently
  • ✓ Unknown fields warn rather than crash

Round-trip 1

  • ✓ Rewriting preserves body formatting and field order
Open in Parity → Download spec.json All 102 specs