frontend▌

Automated React Native version upgrades with diff-based native project updates and dependency management. \n \n Fetches and applies unified diffs from the React Native Upgrade Helper, handling version bumps across package.json , iOS, and Android native files \n Maps template paths and identifiers ( RnDiffApp , com.rndiffapp ) to your actual project structure before applying changes \n Detects conflicts between template changes and project customizations, presenting a merge plan for manual review

You are a senior design engineer specializing in motion and interaction design. When asked to audit motion design, you MUST follow this workflow exactly.

A modern dark-themed React UI system using Tailwind CSS and Framer Motion. Designed for dashboards, admin panels, and data-rich applications with glassmorphism effects and tasteful animations.

Comprehensive guide for modern React development, emphasizing Suspense-based data fetching, lazy loading, proper file organization, and performance optimization.

Effects are an escape hatch from React. They let you synchronize with external systems. If there is no external system involved, you shouldn't need an Effect.

Refactor SwiftUI views toward small, explicit, stable types with MV-first defaults. \n \n Enforces view ordering (environment, state, computed vars, init, body, helpers) and strongly prefers dedicated subview types over computed some View helpers for non-trivial sections \n Defaults to Model-View architecture: local state in views, shared dependencies in environment, business logic in services/models, view models only when explicitly required or already present \n Extracts actions and side effec

Best practices and patterns for building SwiftUI views, navigation, and state management. \n \n Covers state ownership strategies (from @State and @Binding to @Observable on iOS 17+), async/await patterns with .task , and environment injection for shared dependencies \n Includes cross-cutting references for NavigationStack routing, sheet presentation, deep linking, and app-level wiring with concrete ownership rules \n Provides component-specific guidance via indexed references, with anti-pattern

Accessibility patterns for building inclusive React applications following WCAG standards. Contains 7 rules across 4 categories focused on semantic HTML, screen reader support, keyboard navigation, and user preferences.

Comprehensive guide for Medusa backend architecture, workflows, and critical implementation rules. \n \n Covers six rule categories (architecture, type safety, business logic placement, imports, data access, file organization) with specific anti-patterns and enforcement checks \n Enforces strict layer separation: Module → Workflow → API Route → Frontend, with workflows required for all mutations and only GET/POST/DELETE HTTP methods allowed \n Includes critical data handling rules: prices stored

SDK-first frontend integration for Medusa storefronts with React Query patterns and critical API calling rules. \n \n Always use the Medusa JS SDK for all API requests—never use regular fetch(), as it lacks required headers (publishable API key for store routes, auth for admin routes) \n Pass plain JavaScript objects to SDK methods; never use JSON.stringify() on body parameters, as the SDK handles serialization automatically \n Use useQuery for GET requests and useMutation for POST/DELETE reques