agentleFS
Sign inStart free
MRCalderon3DMRCalderon3D/everything-game-dev-code/skills/art-audio-content/ui-animation-pipeline/SKILL.md

ui-animation-pipeline

Skill105 starsChanged 8 months agoMITView on GitHub

Define transition, feedback, and state-driven animation rules for UI elements.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 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.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    every UI animation has a defined duration and easing — no magic numbers in code

    line 40
  2. Distinctive:

    no reduced-motion fallback, failing accessibility requirements

    line 50
  3. Distinctive:

    Keep this skill aligned with the relevant rules layer and current project documentation.

    line 68
  4. Distinctive:

    If engine-specific constraints materially change the workflow, hand off to the matching engine skill or engine-specific reviewer.

    line 69
  5. Distinctive:

    Prefer code-driven animations (tween systems, animation state machine triggers, scripted easing) over baked sprite sheet animations for UI.

    line 70

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

UI Animation Pipeline

Purpose

Define transition, feedback, and state-driven animation rules for UI elements so interactions feel responsive, screens transition smoothly, and animations stay within performance budgets.

Use When

  • UI elements need hover, press, focus, or disabled state feedback
  • screen transitions need standardization (fade, slide, scale)
  • UI animations are inconsistent in timing, easing, or direction across screens
  • new UI screens are being added and need animation behavior that follows project conventions

Inputs

  • UI flow map (screens, transitions, popups)
  • interaction states per element type (normal, hover, pressed, focused, disabled)
  • target frame rate and animation budget
  • accessibility requirements (reduced motion preference)

Process

  1. define animation categories: state feedback (hover, press), screen transitions (in/out), attention (pulse, bounce), progress (fill, count)
  2. set duration, easing curve, and delay rules per category
  3. establish a reduced-motion fallback for each animation (instant cut or opacity-only)
  4. configure animation via code (tweens, coroutines, or animation system) — not baked sprite sheets
  5. validate animation timing, overlap behavior, and cancellation safety

Outputs

  • UI animation convention document (durations, easings, directions per category)
  • state feedback specification per element type
  • screen transition specification (in/out pairs)
  • reduced-motion fallback map
  • validation checklist for new UI animations

Quality Bar

  • every UI animation has a defined duration and easing — no magic numbers in code
  • state feedback is immediate (under 100ms response time)
  • screen transitions do not block input for more than 300ms
  • reduced-motion fallback exists for every animation
  • animations cancel cleanly when interrupted (no stuck states)

Common Failure Modes

  • inconsistent easing curves that make the UI feel disjointed
  • animations that block input, making the UI feel sluggish
  • missing cancellation logic that leaves elements in mid-animation state
  • no reduced-motion fallback, failing accessibility requirements
  • overlapping animations that compete for the same element

Related Agents

  • 2d-artist
  • ui-programmer
  • ui-ux-designer
  • accessibility-reviewer

Related Commands

  • ui-asset-pass
  • ui-flow-review
  • verify

Related Skills

  • ui-hud-patterns

Notes

  • Keep this skill aligned with the relevant rules layer and current project documentation.
  • If engine-specific constraints materially change the workflow, hand off to the matching engine skill or engine-specific reviewer.
  • Prefer code-driven animations (tween systems, animation state machine triggers, scripted easing) over baked sprite sheet animations for UI. Code-driven animations are resolution-independent and easier to tune. Pick the concrete tween library or animation system from the active engine layer.
  • Boundary: this skill owns UI motion authoring and tuning conventions; ui-hud-patterns owns runtime HUD architecture and data binding.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free