explainer-animation
Skill2 starsChanged 4 months agoMITView on GitHub
Generate structured animation prompts for Claude Design. Structure, layout, box formatting, pacing, and on-screen text only — never colors, fonts, or styling. The user's uploaded design system owns all visual style. Use when asked for a Claude Design prompt, animation for a concept, explainer video prompt, or to visualize a technical idea.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- c-kick/hnl-agent-skillstheir own version, first seen May 1, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- c-kick/hnl-agent-skills★ 56same 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 repository2 other files it gives its agents.
- html2deckSkill
- visual-style-lawsSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 30
Do not load every reference for a one-line fix.
- Distinctive: line 49
Always create a NEW canvas file.
- Distinctive: line 50
Do not export until you say it looks good.
- Distinctive: line 52
Not a guarantee. Batch fixes.
- Very specific: line 54
When writing the prompt, follow the load table → references/prompt-template.md, then the teaching test in references/principles.md before …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Explainer Animation Prompt Generator
Produces a paste-ready prompt for Claude Design (or a similar design canvas).
Always follow the style tokens already loaded in the design project.
The prompt owns structure, layout, boxes, motion, and text. Never invent a palette,
never name a design-system project, never specify colors, fonts, or CSS.
Load only what you need
| Task | Read |
| Write a new prompt | this file → references/principles.md → layout.md → pacing.md → text.md → prompt-template.md |
| Fix teaching / empty lesson / vague headers | references/principles.md + references/text.md |
| Fix layout / overlaps / arrows / fills | references/layout.md |
| Fix timing / reveals / interaction | references/pacing.md |
| Fix on-screen wording | references/text.md |
| Review before paste | references/review.md + references/principles.md (+ the prompt file) |
Do not load every reference for a one-line fix.
Absolute: never style
Forbidden in the prompt: color names, hex codes, palettes, fonts, backgrounds, borders, shadows, CSS, or a named design-system / template.
Required instead: match the reference file’s export contract; use the design system already in this project for colors, fonts, and components.
Layout geometry (bands, gaps, box sizing from labels) is formatting — keep it.
Process
- Have an idea — a claim worth teaching (doc, paste, or verbal). Pull claim + stakes
before any geometry (
references/principles.md). - Invoke this skill — it writes a paste-ready Claude Design prompt (structure, layout, motion, on-screen text only — never colors or fonts).
- Paste into Claude Design — project already has your design system / template. Always create a NEW canvas file. Match the reference file’s export contract. Do not export until you say it looks good.
- Iterate on the live render — hope for something that works in under five passes. Not a guarantee. Batch fixes; scrub transitions; keep the tab focused on export.
When writing the prompt, follow the load table → references/prompt-template.md, then
the teaching test in references/principles.md before paste.
Hard principles (always on)
Full text: references/principles.md. Short list:
- Content spine before geometry (claim + stakes + show plan)
- Titles and headers: concise but specific — name the thing, do not be vague
- Cold-viewer test (mute jargon; domain still obvious)
- Labels are not the diagram (mechanism first)
- Diagram + motion fit the claim (travel / flow / settle+interact — choose, don’t default)
- Highlight matches the box (exact segment geometry)
- Title card = title + simple static through-line diagram
- Form still matters (no invented style, timing, listed text only, no labeled tracker)
Teaching test: cold viewer can state the claim; each scene advances a stake; jargon-covered picture still makes sense. Geometry-only form passes are fails.
Iterate
Step 4 above. Batch change requests. Scrub transitions (ghost cards, detached arrowheads, text over lines, frozen tails, fills that miss their box).
Keeping this current
Edit the smallest reference that owns the rule. Solidified teaching/clarity rules live
in references/principles.md. Keep this router short.
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.