add-slide
Skill0 starsChanged 13 days agoMITView on GitHub
Add, rewrite, split or merge a slide in this deck kit, with notes, build steps, manifest entry and checks. Use when the user asks for a new slide, a profile-specific slide, a diagram slide, or a rework of one existing slide.
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 0 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Read docs/authoring.md, and docs/brief.md plus docs/decisions.md if they exist.
- Very specific: line 22
If asked, <details> with sources
- Very specific: line 24
Add it to every profile that should show it in src/deck.ts, with a target time, and rebalance times so each profile still fits its length.
- Very specific: line 29
Check: pnpm check, pnpm test:deck, then pnpm shots and look at the new slide's images in out/shots/ (fully built and step 1).
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Add or rewrite a slide
- Read
docs/authoring.md, anddocs/brief.mdplusdocs/decisions.mdif they exist. Look at the neighbouring slides insrc/slides/so the new one matches their voice and notes depth.examples/wifi/slides/andexamples/crypto/slides/have worked examples of every slide type. - Settle the content. Facts and numbers must come from the brief, the decisions or
docs/fact-log.md. If the slide needs a new claim, research it (with a source), add it to the fact log, and mark the on-screen textdata-todo="new claim, needs approval"until the speaker approves it. - Write
src/slides/NN-<id>.html:- pick the
data-typethat matches the content's shape (comparison:comparison-table; sequence:timeline; relation:diagram; two or three parallel points:two-columnorthree-column; one idea:statement; closing points:takeaway) - about 30 words on screen; detail goes in the notes
- build steps with
data-fragmentwhere revealing in order helps the story - notes: Script with one
data-stepblock per step (0 to the last), Next, Acronyms, If asked,<details>with sources - number the file to sit in talk order (renaming neighbours is fine; ids do not change)
- pick the
- Add it to every profile that should show it in
src/deck.ts, with a target time, and rebalance times so each profile still fits its length. Fix the Next line of the slide before it (and itsdata-profilevariants). - New icons go in
src/assets/icons.ts; newdgm-*classes or layout classes get styles insrc/theme/using existing tokens only. - Check:
pnpm check,pnpm test:deck, thenpnpm shotsand look at the new slide's images inout/shots/(fully built and step 1). Fix and repeat until clean. - Report what changed, the new profile times, any
data-todoleft, and the check output.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

