Ui Animation Pipeline logo

Ui Animation Pipeline

Community
MRCalderon3D
ui-animation-pipeline

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

Overview

PublisherMRCalderon3D
Repositoryeverything-game-dev-code
Skill nameui-animation-pipeline
Stars
85
Forks
13
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by MRCalderon3D on GitHub. Read the source before you install it.

Installation

Install the Ui Animation Pipeline AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/MRCalderon3D/everything-game-dev-code.git /tmp/everything-game-dev-code
mkdir -p .claude/skills
cp -r /tmp/everything-game-dev-code/skills/art-audio-content/ui-animation-pipeline .claude/skills/ui-animation-pipeline
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Ui Animation Pipeline in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Ui Animation Pipeline on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Ui Animation Pipeline is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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.

Frequently asked questions

What does the Ui Animation Pipeline AI skill do?

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

Why use Ui Animation Pipeline on TypingMind?

Because you install it once and use it with any model. Ui Animation Pipeline is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Ui Animation Pipeline in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/MRCalderon3D/everything-game-dev-code/tree/main/skills/art-audio-content/ui-animation-pipeline. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Ui Animation Pipeline?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Ui Animation Pipeline?

As many as you like. As long as a model supports skills, you can use Ui Animation Pipeline with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Ui Animation Pipeline AI skill free?

Yes. It is published on GitHub by MRCalderon3D under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇