build-slide
Skill1 starsChanged 2 days agoMITView on GitHub
Plan and build a bespoke slide for the user's presentation using its active template's typography and visual references. Loaded by /opp-propose (Plan) and /opp-apply (Implement) for deck changes.
In this repository23 other files it gives its agents.
- AGENTS.mdAGENTS.md
- core/AGENTS.mdAGENTS.md
- presentation/AGENTS.mdAGENTS.md
- showcase/AGENTS.mdAGENTS.md
- build-templateSkill
- openprezSkill
- openspec-apply-changeSkill
- openspec-archive-changeSkill
- openspec-bulk-archive-changeSkill
- openspec-continue-changeSkill
- openspec-exploreSkill
- openspec-ff-changeSkill
- openspec-new-changeSkill
- openspec-onboardSkill
- openspec-proposeSkill
- openspec-sync-specsSkill
- openspec-update-changeSkill
- openspec-verify-changeSkill
- opp-applySkill
- opp-archiveSkill
- opp-exploreSkill
- opp-proposeSkill
- promote-to-coreSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
17 rules. About 0 are common, 5 are distinctive, and 12 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
12
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Before planning typography or visual styling:
- Very specific: line 18
Read app/main.tsx and resolve its active template import to templates/<name>/.
- Very specific: line 19
Read that template's STYLEGUIDE.md in full.
- Very specific: line 22
Read AGENTS.md, presentation/AGENTS.md, the change artifacts (approved ones when applying), and the relevant deck source and slide code.
- Distinctive: line 27
Use the approved change and canonical presentation source for facts, scope and intended transitions.
- Very specific: line 43
Follow the active template's visual references and color guidance.
- Very specific: line 44
Use the template's font roles through font-body, font-display and font-mono where appropriate.
- Distinctive: line 45
Keep all slide content within the fixed 1920x1016 slide area above the 64px footer.
- Very specific: line 46
Use build steps to guide attention, not to hide necessary context: reveal one idea at a time and keep each build coherent.
- Distinctive: line 47
Keep diagrams and interactions within the slide.
- Very specific: line 53
Put slide components under presentation/slides/ and slide assets under presentation/assets/.
- Very specific: line 54
When reusing artwork documented in the active template guide, copy the source file or recreate the artwork under presentation/assets/.
- Very specific: line 56
Keep SVG diagrams local and export-safe: use SVG-native shapes and text for essential content, avoid <foreignObject>, and provide …
- Very specific: line 61
Import it from @core and render it inside an SVG.
- Very specific: line 68
Put each slide in presentation/slides/ and register it in presentation/deck.tsx with a unique ID, the approved steps, relevant keyFrames, …
- Very specific: line 72
Keep any foundation work separate from deck work.
- Distinctive: line 73
Do not commit. Report what changed, what was validated and any unresolved content or visual question.
≈ “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
Build a slide
This skill guides slide design and implementation in the user's presentation/ deck. It does not replace the /opp-* workflow or authorize unplanned edits. The workflow loads it for a change whose proposal records Type: deck: /opp-propose follows Plan, and /opp-apply follows both sections, implementing only the approved change. Never use this skill to author the showcase/ deck.
Plan
1. Read the active template reference first
Before planning typography or visual styling:
- Read
app/main.tsxand resolve its active template import totemplates/<name>/. - Read that template's
STYLEGUIDE.mdin full. Use its font roles, palette, tones, motifs and asset references before introducing other styles. - If the active template or guide cannot be resolved, or the guide is missing, stop before visual planning and ask for the template/reference to be clarified or created through a template change in
/opp-propose(see.agents/skills/build-template/SKILL.md). Do not guess that the default template is active.
Read AGENTS.md, presentation/AGENTS.md, the change artifacts (approved ones when applying), and the relevant deck source and slide code. The template guide is a design reference only: deck code must not import from templates/.
2. Frame the slide's message
- State the single audience takeaway in one sentence and place it in the deck's narrative, accounting for what comes before and after it.
- Use the approved change and canonical presentation source for facts, scope and intended transitions. If a claim, source or content requirement is unclear, stop and ask rather than inventing it.
- Decide what the audience should see first, what can be revealed later, and what belongs in concise speaker notes.
3. Choose a visual idea
Choose a bespoke visual form that makes the message obvious. Use the showcase as an example of foundation capabilities, not as a source of stock layouts.
| Message | Possible visual direction |
| Something flows or transforms | FlowLine paths between bespoke stations |
| A system or process | A custom SVG composition with local nodes and FlowLine connectors |
| A contrast | Opposing compositions or distinct template tones |
| A few key numbers | Large figures revealed one per build step |
| Detail on demand | Clickable cards that open a panel without taking over player navigation |
- Make the visual form serve the message. Prefer a bespoke React/SVG composition over stock title-and-bullet or two-column layouts; existing components are optional behavior primitives, not required layouts. Compose the visual metaphor, nodes and spacing for the message.
- Follow the active template's visual references and color guidance. Use declared tone names and shared surface tokens (
surfaceandon-surface) for slide backgrounds and foregrounds. Use palette theme tokens for accents rather than hardcoding replacements for the template palette. - Use the template's font roles through
font-body,font-displayandfont-monowhere appropriate. Establish hierarchy with size, weight, line height and spacing. Never request fonts at runtime. - Keep all slide content within the fixed 1920x1016 slide area above the 64px footer. Use stage pixels; do not add responsive or mobile layouts. A slide's fixed-position elements stay inside its slide area and must not cover the footer.
- Use build steps to guide attention, not to hide necessary context: reveal one idea at a time and keep each build coherent. Keep the declared step count,
useStep()usage andkeyFramesconsistent so forward and reverse navigation restore the intended states. - Keep diagrams and interactions within the slide. Do not take over player navigation or add internal pan, zoom, selection or diagram-canvas navigation. A slide that listens for keys must not capture player navigation keys unless an input inside it has focus.
Implement
4. Keep artwork local and credited
- Put slide components under
presentation/slides/and slide assets underpresentation/assets/. Import foundation APIs only from@core, and use relative imports only withinpresentation/. - When reusing artwork documented in the active template guide, copy the source file or recreate the artwork under
presentation/assets/. Never import a file, component or deep module fromtemplates/. Use shared foundation components only through their public@coreexports. - Confirm that source terms allow the intended redistribution and retain required attribution. Add or update
presentation/assets/CREDITS.mdwith the asset path, title/creator, source, license, modifications and required credit. If terms or provenance are unclear, do not use the asset until resolved. - Keep SVG diagrams local and export-safe: use SVG-native shapes and text for essential content, avoid
<foreignObject>, and provide accessible labels for meaningful graphics. Use active theme CSS variables for theme-colored strokes and fills. - For custom motion, use
useMotionAllowance(),stepTransition()andEASE_OUTfrom@corewhere appropriate, honor reduced-motion preferences, and useuseExportMode()to render settled content for static PDF capture. Do not rely on remote images, remote fonts, or runtime asset fetching.
FlowLine
- Import it from
@coreand render it inside an SVG. - Pass SVG path data through
d; usestepto choose when the connector draws. - Optional
color,width,duration, andflowingprops control its treatment. - It draws and retracts with step navigation, disables pulses for reduced motion, and settles for static PDF export. It does not arrange nodes or choose a diagram structure.
5. Implement and validate
- Put each slide in
presentation/slides/and register it inpresentation/deck.tsxwith a unique ID, the approvedsteps, relevantkeyFrames, selected tone, concisenotesand its component. - Derive concise speaker notes from the approved content and note intent; for multi-step slides, use
[[step:N]]markers and keep all passages visible. Keep the richer narrative inopenprez/specs/presentation.md. - Preview the affected slide and changed steps or interactions, including step progression and rewind; do not repeat a full-deck walkthrough. Check typography, contrast, cropping, footer clearance and the active template references at presentation scale.
- After slide-code changes, run
pnpm checkand focused tests relevant to the changed behavior. Do not refresh dependencies for deck authoring;pnpm update --latestis reserved for actual application-foundation or explicit dependency work, as described incore/AGENTS.md. Generate a PDF only when export-sensitive rendering, settled animation, capture-sensitive assets or the export path changed, or when requested. - Keep any foundation work separate from deck work. If the slide requires a reusable
core/change, surface that as a separate foundation change rather than importing template internals or silently expanding the approved deck scope. - Do not commit. Report what changed, what was validated and any unresolved content or visual question.
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.

