Slide Decks
Overview
The craft of making a slide deck shareable and readable, worked on as text and structure: the brief, the story spine, per-slide claims, chart choice, reading load, projection typography, exported-file accessibility, and recurring quality control. The reader is a general agent drafting or reviewing a deck's text and outline, not a binary editor.
When to use
- Drafting, outlining, or restructuring a slide deck.
- Reviewing a deck someone else wrote, at the text level.
- Turning a recurring report into a reusable deck template.
- Choosing or challenging the charts inside a deck.
When NOT to use
Talk scripts and speaker notes are outside this skill; ac-narrative-writing covers that craft. Document typesetting and the README/how-to/reference doc set are outside; ac-technical-writing covers those. Binary manipulation of a .pptx file is outside by design: this skill works on the deck as text, structure, and chart decisions.
Precedence
The deepest loaded instruction governs its uniquely-claimed scope; every
scope:string is claimed by exactly one file in this tree; no leaf may widen a prohibition declared by an ancestor: leaves narrow, never override upward.
Subskill index
| subskill file | when to load |
|---|---|
subskills/brief-and-audience.md |
starting a deck; the audience or the decision is unclear |
subskills/narrative-spine.md |
structuring the deck; the story drifts |
subskills/slide-grammar.md |
slides carry topic labels or stacked bullets |
subskills/charts-per-claim.md |
a datum needs the right chart, or no chart |
subskills/density-and-reading.md |
slides are crowded; live versus leave-behind split |
subskills/type-and-media.md |
type size, layout, imagery, animation questions |
subskills/accessibility.md |
the deck is exported and shared as a file |
subskills/recurring-qa.md |
naming, versioning, templates, the pre-send check |