plannotator-visual-explainerlisted

# Plannotator Visual Explainer Three paths depending on content type. Each has its own references and structure. ## Route by content type **Implementation plan, design doc, or proposal** → Follow the [Plan path](#plan-path). Read `references/design-system.md` and `references/svg-patterns.md`. Prescriptive structure. **PR explainer, diff review, or code change walkthrough** → Follow the [PR path](#pr-path). Read `references/design-system.md` and `references/pr-components.md`. Prescriptive structure. **Everything else** (architecture diagrams, data tables, slide decks, project recaps, general visual explanations) → Follow the [Visual explainer path](#visual-explainer-path). Delegates to nicobailon/visual-explainer with Plannotator theme tokens. ## Delivery Always deliver via Plannotator's annotation UI. Do NOT use `open` or `xdg-open`. **Plans/proposals** (user should approve/deny): ```bash plannotator annotate <file> --render-html --gate ``` **Everything else** (informational): ```bash plannotator annotate <file> --render-html ``` --- ## Plan path For implementation plans, design docs, feature specs, migration guides, and proposals. **Before generating, read:** 1. `references/design-system.md` — Plannotator theme tokens, typography, component patterns 2. `references/svg-patterns.md` — inline SVG building blocks for architecture diagrams, flowcharts, data flow **Document structure (in order, pick what fits):** 1. **Header** — eyebrow label (mono, uppercase), titl