Agent Skills: dot-skills — Airbnb iOS SwiftUI Animations Best Practices

Clinic-architecture-aligned iOS animation craft guidelines for SwiftUI (iOS 26 / Swift 6.2) covering motion tokens, spring physics, gesture continuity, spatial transitions, micro-interactions, and accessibility. Enforces @Equatable on animated views and keeps animation state aligned with Domain/Data feature boundaries. Use when writing, reviewing, or refactoring SwiftUI animation code under the clinic modular MVVM-C architecture.

UncategorizedID: pproenca/dot-skills/ios-animations

Install this agent skill to your local

pnpm dlx add-skill https://github.com/pproenca/dot-skills/tree/HEAD/skills/.experimental/ios-animations

Skill Files

Browse the full folder contents for ios-animations.

Download Skill

Loading file tree…

skills/.experimental/ios-animations/SKILL.md

Skill Metadata

Name
ios-animations
Description
Clinic-architecture-aligned iOS animation craft guidelines for SwiftUI (iOS 26 / Swift 6.2) covering motion tokens, spring physics, gesture continuity, spatial transitions, micro-interactions, and accessibility. Enforces @Equatable on animated views and keeps animation state aligned with Domain/Data feature boundaries. Use when writing, reviewing, or refactoring SwiftUI animation code under the clinic modular MVVM-C architecture.

dot-skills — Airbnb iOS SwiftUI Animations Best Practices

Opinionated, strict animation craft guide for SwiftUI iOS 26 / Swift 6.2 apps. Contains 50 rules across 8 categories, prioritized by impact. Derived from Airbnb Engineering motion patterns, Apple WWDC sessions, and Apple Human Interface Guidelines. Mandates @Equatable on every animated view, motion tokens for all spring/timing values, and design system tokens for layout.

Mandated Architecture Alignment

This skill is designed to work alongside swift-ui-architect and ios-design-system. All code examples follow the same non-negotiable constraints:

  • @Equatable macro on every view (Airbnb measured 15% scroll hitch reduction)
  • @Observable for complex animation state that involves business logic triggers
  • @State for view-owned animation state (toggle booleans, drag offsets)
  • Design system tokens: Spacing.xs/sm/md/lg, Radius.sm/md/lg — zero hardcoded layout numbers
  • Motion tokens: Motion.standard/responsive/playful — zero scattered spring literals
  • Semantic colors: .backgroundSurface, .accentPrimary — no raw Color literals in views
  • Feature animations remain presentation-only; data/network concerns stay in Data package

Scope & Relationship to Sibling Skills

This skill is the motion layer — it teaches how to BUILD fluid, performant animations. When loaded alongside sibling skills:

| Sibling Skill | Its Focus | This Skill's Focus | |---------------|-----------|-------------------| | swift-ui-architect | Architecture (modular MVVM-C, route shells, protocol boundaries) | Animation architecture (motion tokens, spring selection, orchestration) | | ios-design-system | Design system infrastructure (tokens, styles, governance) | Motion tokens and animated component patterns | | ios-hig | HIG compliance patterns | Motion-specific HIG (reduce motion, spatial continuity) |

Out of scope: Designer-authored vector animations (use Lottie for After Effects exports). Complex UIKit transition controllers (see Airbnb's declarative transition framework). This skill covers programmatic SwiftUI animations only.

Clinic Architecture Contract (iOS 26 / Swift 6.2)

All guidance in this skill assumes the clinic modular MVVM-C architecture:

  • Feature modules import Domain + DesignSystem only (never Data, never sibling features)
  • App target is the convergence point and owns DependencyContainer, concrete coordinators, and Route Shell wiring
  • Domain stays pure Swift and defines models plus repository, *Coordinating, ErrorRouting, and AppError contracts
  • Data owns SwiftData/network/sync/retry/background I/O and implements Domain protocols
  • Read/write flow defaults to stale-while-revalidate reads and optimistic queued writes
  • ViewModels call repository protocols directly (no default use-case/interactor layer)

When to Apply

Reference these guidelines when:

  • Adding animations to SwiftUI views or transitions
  • Building gesture-driven interactions (drag, swipe, pan)
  • Connecting views with spatial transitions (expand/collapse, navigation morphs)
  • Designing micro-interactions (button press, toggle, loading states)
  • Making content changes feel physical (number rolls, symbol replacements)
  • Choreographing multi-element animation sequences (KeyframeAnimator, PhaseAnimator)
  • Defining motion tokens for a design system
  • Reviewing animation code for performance, accessibility, and architecture compliance

Rule Categories by Priority

| Priority | Category | Impact | Prefix | Rules | |----------|----------|--------|--------|-------| | 1 | Spring Physics | CRITICAL | spring- | 8 | | 2 | Timing & Feel | CRITICAL | feel- | 6 | | 3 | Gesture Continuity | HIGH | gesture- | 7 | | 4 | Spatial Transitions | HIGH | spatial- | 6 | | 5 | Micro-interactions | HIGH | micro- | 6 | | 6 | Orchestration | HIGH | orch- | 5 | | 7 | Craft & Polish | HIGH | craft- | 5 | | 8 | Content Motion | MEDIUM-HIGH | content- | 5 |

Quick Reference

1. Spring Physics (CRITICAL)

2. Timing & Feel (CRITICAL)

3. Gesture Continuity (HIGH)

4. Spatial Transitions (HIGH)

5. Micro-interactions (HIGH)

6. Orchestration (HIGH)

7. Craft & Polish (HIGH)

8. Content Motion (MEDIUM-HIGH)

How to Use

Read individual reference files for detailed explanations with incorrect/correct code examples:

Reference Files

| File | Description | |------|-------------| | references/_sections.md | Category definitions and ordering | | assets/templates/_template.md | Template for new rules | | metadata.json | Version and reference information |