agentleFS
KhaledSaeed18KhaledSaeed18/deck-kit/.agents/skills/add-slide/SKILL.md

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
  1. Very specific:

    Read docs/authoring.md, and docs/brief.md plus docs/decisions.md if they exist.

    line 8
  2. Very specific:

    If asked, <details> with sources

    line 22
  3. Very specific:

    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.

    line 24
  4. Very specific:

    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).

    line 29

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Add or rewrite a slide

  1. Read docs/authoring.md, and docs/brief.md plus docs/decisions.md if they exist. Look at the neighbouring slides in src/slides/ so the new one matches their voice and notes depth. examples/wifi/slides/ and examples/crypto/slides/ have worked examples of every slide type.
  2. 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 text data-todo="new claim, needs approval" until the speaker approves it.
  3. Write src/slides/NN-<id>.html:
    • pick the data-type that matches the content's shape (comparison: comparison-table; sequence: timeline; relation: diagram; two or three parallel points: two-column or three-column; one idea: statement; closing points: takeaway)
    • about 30 words on screen; detail goes in the notes
    • build steps with data-fragment where revealing in order helps the story
    • notes: Script with one data-step block 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)
  4. 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 its data-profile variants).
  5. New icons go in src/assets/icons.ts; new dgm-* classes or layout classes get styles in src/theme/ using existing tokens only.
  6. 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). Fix and repeat until clean.
  7. Report what changed, the new profile times, any data-todo left, and the check output.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.