How do I install the Design Animation skill?

Run npx skillmds@latest add coreyone/design-animation in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Design Animation safe to use?

SkillMD's automated safety review verdict for this skill is PASS. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Design Animation?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Design Animation free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Design Animation?

coreyone (@coreyone) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Design Animation by coreyone — Agent Skill

Name: Design Animation
Rating: 4.2 (5 reviews)
Author: coreyone

Design Animation

Design, implement, audit, and plan interface animation and motion systems. Use for animation reviews, motion audits, easing and duration decisions, gesture physics, transform origins, reduced-motion behavior, animation performance, SvelteKit or Motion integration, perceptual feel checks, or self-contained animation improvement plans.

coreyone Updated Aug 19, 2026 1 repo stars

File contents

▣ Key takeaway

When to use

Use this skill when the task is primarily about design and this guidance is the most relevant operating rule set.

When not to use

Do not use this skill as the primary guide when another skill has a tighter domain fit for the requested output.

Trigger cues

Request explicitly references design-animation or this source file.
Request language includes terms like: design, animation.
Keywords include: IA, usability, responsive layout, design system, aesthetic direction, motion.

Routing boundary

Primary for UX architecture, visual hierarchy, responsiveness, and interface behavior.
Do not use as primary for backend architecture, threat modeling, or release operations.

Inputs required

Goal or task request
Current constraints (time, scope, platform, risk)
Existing artifacts (code, docs, screenshots, metrics) when available
Source of truth: subagents/rules/design/design-animation.md

Instructions

Read references/source.md first.
Extract the non-negotiable rules and translate them into a short execution checklist.
Apply the checklist to the current task, produce concrete outputs, and avoid abstract recommendations.
Validate outcomes with evidence (tests, screenshots, logs, diffs, or written audit findings).
Record decisions and tradeoffs so another engineer can continue without re-discovery.

Output format

Primary decision/output: User flow clarity, interaction model, and visual system constraints.
Summary: one-paragraph decision or result
Actions: compact checklist with owners and status
Evidence: links/paths to artifacts proving completion

---name: design-animationdescription: Design, implement, audit, and plan interface animation and motion systems. Use for animation reviews, motion audits, easing and duration decisions, gesture physics, transform origins, reduced-motion behavior, animation performance, SvelteKit or Motion integration, perceptual feel checks, or self-contained animation improvement plans.---# ▣ Key takeaway## When to useUse this skill when the task is primarily about design and this guidance is the most relevant operating rule set.## When not to useDo not use this skill as the primary guide when another skill has a tighter domain fit for the requested output.## Trigger cues- Request explicitly references `design-animation` or this source file.- Request language includes terms like: design, animation.- Keywords include: IA, usability, responsive layout, design system, aesthetic direction, motion.## Routing boundary- Primary for UX architecture, visual hierarchy, responsiveness, and interface behavior.- Do not use as primary for backend architecture, threat modeling, or release operations.## Inputs required- Goal or task request- Current constraints (time, scope, platform, risk)- Existing artifacts (code, docs, screenshots, metrics) when available- Source of truth: `subagents/rules/design/design-animation.md`## Instructions1. Read [references/source.md](references/source.md) first.2. Extract the non-negotiable rules and translate them into a short execution checklist.3. Apply the checklist to the current task, produce concrete outputs, and avoid abstract recommendations.4. Validate outcomes with evidence (tests, screenshots, logs, diffs, or written audit findings).5. Record decisions and tradeoffs so another engineer can continue without re-discovery.## Output format- Primary decision/output: User flow clarity, interaction model, and visual system constraints.- Summary: one-paragraph decision or result- Actions: compact checklist with owners and status- Evidence: links/paths to artifacts proving completion

Frequently asked questions