AugmentClaude

Animate

Add, fix, or remove animations from your UI with purpose and restraint.

Installation

  1. Make sure Claude is on your device and in your terminal.

    Skills load from ~/.claude/skills/ when Claude Code starts up β€” so you need it on your machine first. If you don't have it yet, install it once with the command below, then run claude in any terminal to verify.

    One-time setup
    npm i -g @anthropic-ai/claude-code

    Already have it? Skip ahead.

  2. Paste into Claude Code or into your terminal.

    This copies the whole skill folder into ~/.claude/skills/animate-educlopez/ β€” the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Safe default: works for every skill.

    Faster alternative (instruction-only skills)

    Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates β€” they won't be downloaded and the skill will fail when it tries to load them.

    Quick install (SKILL.md only)
    Sign up to copy
  3. Restart Claude Code.

    Quit and reopen Claude Code (or any other agent that loads from ~/.claude/skills/). New skills are picked up on startup.

  4. Just ask Claude.

    Skills auto-activate when your request matches the skill's description β€” no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the β€œWhat this skill does” section above.

Prefer to read the source first? Open on GitHub.

When Claude uses it

Motion design pass β€” adds purposeful animations or removes excessive ones, respecting MOTION_INTENSITY and the project's animation stack. Use when the user asks to add animation, "make it feel smoother", fix janky transitions, or trim motion that's distracting. Invoke when the user asks for animate on their UI, or mentions 'animate' alongside design / UI / frontend work.

What this skill does

<!-- HARNESS MIRROR β€” do not edit here. Canonical source: skills/ or commands/. After editing source, copy into cli/assets/<harness>/ and repo-root harness mirrors. -->

Context: this sub-skill is one lens of the broader ui-craft skill. If the ui-craft skill is also installed, read its SKILL.md first for Discovery + Anti-Slop + Craft Test, then apply the specific lens below.

Add or fix animations in $ARGUMENTS. Load the ui-craft skill.

Step 1 β€” Decision Ladder: run the Decision Ladder from references/motion.md first. Anything that fails it gets removed, not improved.

Step 2 β€” Pick the library:

  • If user opted into a stack during Discovery β†’ read references/stack.md. Use the matching section (Motion, GSAP, or Three.js). Never mix libraries on the same property.
  • Otherwise β†’ CSS transitions / @keyframes / animation-timeline: view() only.

Step 3 β€” Apply motion budget:

ElementBudget
Color/opacity100-150ms
Small UI (tooltips, dropdowns)150-200ms
Medium UI (modals, panels)200-300ms
Large UI (page transitions, drawers)300-400ms

Exit β‰ˆ 75% of entrance duration (shorter, same ease-out β€” or a flatter tail like cubic-bezier(0.4, 0, 1, 1) for a softer exit). Never ease-in on UI (see references/motion.md). cubic-bezier(0.22, 1, 0.36, 1) is a safe spring-like default.

Step 4 β€” Multi-stage sequences β†’ read ../examples/animation-storyboard.md. Stagger 30-80ms, not 200ms.

Step 5 β€” Respect the knobs:

  • MOTION_INTENSITY ≀ 3 β†’ hover states only, no entrances, no scroll-triggered.
  • MOTION_INTENSITY 4-7 β†’ standard entrances + hover, one scroll reveal max per section.
  • MOTION_INTENSITY 8+ β†’ scroll-linked, page transitions, magnetic cursor OK (still honor reduced-motion).

Output: edit code directly. After each file, print the Review Format table. Flag any animation you removed and why.

Next step: /polish β€” the compound details around the motion you just added (rung 1).

Related skills