Concept Explainer Template
What makes a concept page reusable?
A concept page explains one idea well enough that a reader can reuse it.
Use this when the page job is concept.
Frontmatter
type: concept
template: concept-explainer-template
template_url: /playbook/standards/templates/concept-explainer-template
loop_phase: evolution
level: working
Shape
- Name the idea in one plain sentence.
- Explain the core move.
- Say what it replaces.
- Show how to apply it.
- Name where it breaks.
- End with the next question.
Skeleton
TITLE
ONE-SENTENCE IDEA.
## Core Move
What changes when the reader understands this idea?
## Why It Matters
What does this make easier, safer, faster, or clearer?
## How to Use
What should the reader do with it?
## Limits
Where does the idea fail or need context?
## Context
- [Related page](/playbook/)
## Questions
What should the next loop ask?
Checks
- The page teaches one model, not a list of facts.
- The first screen names the idea and why it matters.
- Every section advances the same concept.
- Links add context instead of replacing the explanation.
Failure Modes
- The page becomes a hub and routes before it explains.
- It acts like a playbook and gives steps before meaning.
- Definitions pile up without showing why the idea matters.
Context
- Page Types - full page-type catalogue.
- Index Page Standard - use when the route is an index.
- Purpose - keep the concept tied to intent.
Questions
What must the reader understand after this page?
- Can the reader restate the idea in one sentence?
- Does the page explain one model, or does it hide a list?
- Which linked page should handle action, evidence, or routing?