apple-design-react-native

Installation
SKILL.md

Apple Design for React Native

Core Idea

Make the interface feel like a responsive physical system whose behavior clarifies state and preserves user agency. Start from the interaction's cause, spatial model, and platform evidence; add polish only when it strengthens hierarchy, continuity, or feedback. Treat delight as the outcome of coherence and craft, not an effect to sprinkle on top.

Stay within Expo and React Native implementation. Translate principles into the project's installed native-capable stack rather than inventing SwiftUI/UIKit equivalents.

Decision Workflow

Follow this order deterministically:

  1. Gate scope. Continue only for Expo or React Native targeting iOS or Android. Apply the hard stops in Routing before analysis or code.
  2. Inspect evidence. Read package.json, the lockfile, Expo config, native folders when present, and relevant source. Record the installed Expo, React Native, Reanimated, and Gesture Handler versions before naming APIs.
  3. State the contract. Define initiation, continuous feedback, gesture ownership, bounds, release prediction, snap/commit rules, cancellation, interruption, completion, and accessible alternatives.
  4. Choose behavior. Prefer direct tracking during input, a spring for retargetable settling, and projected momentum only when release velocity should matter. Establish spatial origin, hierarchy, and boundary behavior.
  5. Map to the stack. Reuse existing primitives and version-gate every proposed API. Read fluid-interactions.md when implementing gesture math, interruption, reduced motion, materials, haptics, or verification.
  6. Verify. Test behavior, not just compilation. Separate code-supported expectations from simulator/device observations and from unverified claims.
Installs
4
First Seen
Jul 13, 2026