| name | swiftui-animation-match |
| description | Match UI/UX interaction needs to proven SwiftUI animation patterns from curated open-source catalogs. Use when planning or building iOS/macOS screens where an interaction should feel alive - loaders, likes, toggles, card decks, reveals, shaders - or when asked which animation fits a moment. Recommends system-first restraint before custom motion. |
SwiftUI Animation Match
Use this skill to turn a vaguely felt interaction wish ("saving should feel
more satisfying", "this list is boring while it loads") into a concrete,
proven SwiftUI animation pattern — or into the deliberate decision to use
what the system already provides.
The skill is a matcher, not a snippet dump. Its value is the judgment step:
name the interaction moment first, check what the OS gives you for free,
and only then reach into the cataloged sources for custom motion that earns
its place. Animations add juice that makes a product feel human; forcing
one where the platform already shines makes it feel worse.
First move
- Name the moment. Translate the request into: what is the user doing,
what should they feel, and how often does this happen? Read
references/matching-playbook.md —
it has the moment taxonomy and the system-first checklist.
- Decide system vs custom. If a system affordance covers the moment
(Liquid Glass chrome,
.symbolEffect, springs, .contentTransition,
zoom navigation transitions, .sensoryFeedback), prefer it and stop.
- If custom motion earns its place, search the catalogs (below) by
interaction pattern and keywords, not by animation name.
- Adapt, never paste. Every catalog entry has lift notes and each catalog
ends with a lift checklist (dependencies to replace, old patterns to
modernize, Reduce Motion).
- Verify in motion. Build and watch it in Previews or Simulator; motion
cannot be judged from code. If the app repo has build/test skills
(for example ), use them.
