slide-deck
Skill3 starsChanged 27 days agoMITView on GitHub
Write a slide deck as one self-contained HTML file with animation, step reveals, reduced motion and a print style sheet for PDF. Use when the user asks for a deck, slides or a presentation.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- easedup/educator-skillstheir own version, first seen Oct 17, 2026
- prestarius/jet-skills-stacktheir own version, first seen Oct 11, 2026
- coreyhaines31/makerskillstheir own version, first seen Oct 8, 2026
- hsienchiaolee/agent-skillstheir own version, first seen Sep 23, 2026
- modinc01/claude-skillstheir own version, first seen Sep 9, 2026
- GPTtang/skill-atlastheir own version, first seen Mar 22, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- coreyhaines31/makerskills★ 893same name
- easedup/educator-skills★ 4same name
- GPTtang/skill-atlas★ 4same name
- christyjacob4/claude-tricks★ 2same name
- prestarius/jet-skills-stack★ 1same name
- hsienchiaolee/agent-skills★ 0same name
- modinc01/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository25 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- adrSkill
- api-contract-syncSkill
- architecture-advisorSkill
- ci-triageSkill
- compassSkill
- debugSkill
- delivery-digestSkill
- design-taste-skillsSkill
- grillSkill
- harness-improveSkill
- harness-loopSkill
- impact-analysisSkill
- native-mobile-skillsSkill
- plugin-authorSkill
- pr-flowSkill
- project-memorySkill
- remaining-workSkill
- reviewSkill
- spec-flowSkill
- task-flowSkill
- ui-conformanceSkill
- working-style-skillsSkill
The file
We split this skill into the rules it gives an agent
12 rules. 0 are common, 4 are distinctive, and 8 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Write a deck as one .html file in {{SLIDES_DIR}}/.
- Distinctive: line 19
Ask for the content (the points, the numbers, the audience) and the feeling, unless the user gave them.
- Distinctive: line 23
Write the slides. Remove the sample slides that you do not use.
- Distinctive: line 24
Run the checks below. Fix each failure before you report.
- Very specific: line 32
Use semantic HTML: h1 on the title slide, h2 on the other slides, ul for lists.
- Very specific: line 39
Write each element in its final state.
- Very specific: line 40
Start an animation only under .slide.active, so it plays when the slide shows.
- Very specific: line 44
Do not use <canvas> for content: the PDF shows no script output.
- Very specific: line 45
Keep the prefers-reduced-motion: reduce block of the template.
- Very specific: line 54
Keep the message listener and the Escape message of the template: the host frame sends the arrow keys and leaves its present mode with …
- Very specific: line 55
Keep the @media print block and @page { size: 1920px 1080px.
- Distinctive: line 59
Run each check on the deck.
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
slide-deck
Write a deck as one .html file in {{SLIDES_DIR}}/. All CSS and JavaScript are inline. The deck fetches nothing when a person views it.
A host can show the deck in a sandboxed frame with no origin, and print it to PDF with JavaScript off. The rules below keep the deck working in both.
Based on frontend-slides by Zara Zhang (MIT): https://github.com/zarazhangrui/frontend-slides. The diagram patterns take ideas from visual-explainer by Nico Bailon (MIT): https://github.com/nicobailon/visual-explainer.
Steps
- Ask for the content (the points, the numbers, the audience) and the feeling, unless the user gave them. Ask one question at a time.
- Pick one preset from references/presets.md. Say which one and why in one line.
- Copy references/template.html to
{{SLIDES_DIR}}/<kebab-name>.html. Keep its header comment. - Set
<title>and<html lang>. Change only the:rootvalues for the preset. - Write the slides. Remove the sample slides that you do not use.
- Run the checks below. Fix each failure before you report.
To convert a Markdown deck, keep each slide and its text. Each --- separator starts a new <section class="slide">. Do not delete the Markdown file: the user decides.
Slides
- One idea per slide. Six bullet lines or fewer. The body text is 28 px or more on the 1920 x 1080 stage.
- Each slide is
<section class="slide" aria-label="<n>">. The first slide also has the classactive. - Use semantic HTML:
h1on the title slide,h2on the other slides,ulfor lists. - Give each SVG
role="img"and anaria-labelthat says what it shows. - Contrast: 4.5:1 or more for text on its background.
- Pictures go inline as
data:URLs or as inline SVG. Keep a picture under 300 KB.
Motion
- Write each element in its final state. Animate only from a start state:
@keyframes x { from { ... } }withanimation-fill-mode: backwards. - Start an animation only under
.slide.active, so it plays when the slide shows. - A step reveal is an element with
data-step. The script hides the later steps. Without the script, every step shows. - Diagrams: inline SVG. Lines draw in with
stroke-dasharrayandstroke-dashoffset; boxes fade in after them. - Charts: inline SVG bars or lines. Bars grow with
transform: scaleY(0)as the start state andtransform-origin: bottom. - Do not use
<canvas>for content: the PDF shows no script output. - Keep the
prefers-reduced-motion: reduceblock of the template. It removes every animation and transition. - Motion matches the feeling of the preset. A slide has three moving groups or fewer.
Sandbox and print
- No
fetch,XMLHttpRequest,WebSocket,EventSourceornavigator.sendBeacon. - No
localStorage,sessionStorage,indexedDBor cookies. A frame with no origin throws on them. - No
<link rel="stylesheet">, no@import, no web font URL, no remotesrcorhref. Use system font stacks. - No
alert,confirm,prompt,window.openor forms. - Keep the
messagelistener and the Escape message of the template: the host frame sends the arrow keys and leaves its present mode with Escape. - Keep the
@media printblock and@page { size: 1920px 1080px; margin: 0 }. Each slide prints on its own page, with every step and animation in its final state.
Checks
Run each check on the deck. Each one must pass.
f={{SLIDES_DIR}}/<name>.html
# 1. No network: prints nothing.
grep -nE '(src|href)=["'"'"']?(https?:)?//|url\(["'"'"']?(https?:)?//|@import|<link[^>]+stylesheet' "$f"
# 2. No storage, no request, no dialog: prints nothing.
grep -nE '\b(fetch|XMLHttpRequest|WebSocket|EventSource|sendBeacon|localStorage|sessionStorage|indexedDB|document\.cookie|alert|confirm|prompt|window\.open)\b' "$f"
# 3. Each of these prints a count of 1 or more.
grep -c '<title>' "$f"; grep -c 'prefers-reduced-motion: reduce' "$f"; grep -c '@media print' "$f"
grep -c '@page' "$f"; grep -c 'class="slide active"' "$f"; grep -c 'deckKey' "$f"Then open the file in a browser with the network off:
- The arrow keys, Space, Home and End move through the slides and the steps.
- With reduced motion on in the system, nothing moves.
- The print preview shows one slide per page and every step.
Report
Give the path of the deck, the preset, the number of slides, and the result of each check.
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.

