deck-narrativelisted

# deck-narrative Deck-building skills in this system (e.g. `skill-tekki-strategic-deck`, `marp`, or whichever visual/deck skill your setup uses) are all **visual systems** — CSS classes, palettes, fonts, slide-type names, build mechanics. None of them say anything about whether the *content* is any good: whether the title makes a claim, whether the deck argues top-down, whether a table should have been a chart. This skill is the missing layer underneath all of them. It is a **reasoning discipline, not a template.** ## Read this first: architecture vs visual system | Layer | Decides | Owned by | |---|---|---| | **Architecture** (this skill) | What goes on the slide, in what order, and whether it makes an argument | `deck-narrative` | | **Visual system** | What it looks like — color, type, layout, motion | `skill-tekki-strategic-deck` / `marp` / whichever visual skill your setup uses | **Co-load, don't choose.** When building or reviewing a deck, load `deck-narrative` alongside whichever visual skill applies (your project's routing convention decides which visual skill to co-load). This skill never touches CSS, `pptxgenjs` calls, or slide-type names — it decides the titles, the sequence, and whether a slide should be a table or a chart, then hands the visual skill the content to lay out. Running a visual deck skill without this one is how decks get built by instinct: correct fonts, no argument. **The one narrow exception (Rule 9):** which brand font to use, its weight, its