react-native-expo
Build React Native 0.76+ apps with Expo SDK 52. Covers mandatory New Architecture (0.82+), React 19 changes (propTypes/forwardRef removal), new CSS (display: contents, mixBlendMode, outline), Swift iOS template, and DevTools migration. Use when: building Expo apps, migrating to New Architecture, or troubleshooting "Fabric component not found", "propTypes not a function", "TurboModule not registered", or Swift AppDelegate errors.
What this skill does
# React Native Expo (0.76-0.82+ / SDK 52+) **Status**: Production Ready **Last Updated**: 2025-11-22 **Dependencies**: Node.js 18+, Expo CLI **Latest Versions**: [email protected], expo@~52.0.0, [email protected] --- ## Quick Start (15 Minutes) ### 1. Create New Expo Project (RN 0.76+) ```bash # Create new Expo app with React Native 0.76+ npx create-expo-app@latest my-app cd my-app # Install latest dependencies npx expo install react-native@latest expo@latest ``` **Why this matters:** - Expo SDK 52+ uses React Native 0.76+ with New Architecture enabled by default - New Architecture is **mandatory** in React Native 0.82+ (cannot be disabled) - Hermes is the only supported JavaScript engine (JSC removed from Expo Go) ### 2. Verify New Architecture is Enabled ```bash # Check if New Architecture is enabled (should be true by default) npx expo config --type introspect | grep newArchEnabled ``` **CRITICAL:** - React Native 0.82+ **requires** New Architecture - legacy architecture completely removed - If migrating from 0.75 or earlier, upgrade to 0.76-0.81 first to use the interop layer - Never try to disable New Architecture in 0.82+ (build will fail) ### 3. Start Development Server ```bash # Start Expo dev server npx expo start # Press 'i' for iOS simulator # Press 'a' for Android emulator # Press 'j' to open React Native DevTools (NOT Chrome debugger!) ``` **CRITICAL:** - Old Chrome debugger removed in 0.79 - use React Native DevTools instead - Metro terminal no longer streams `console.log()` - use DevTools Console - Keyboard shortcuts 'a'/'i' work in CLI, not Metro terminal --- ## Critical Breaking Changes (Dec 2024+) ### ๐ด New Architecture Mandatory (0.82+) **What Changed:** - **0.76-0.81**: New Architecture default, legacy frozen (no new features) - **0.82+**: Legacy Architecture **completely removed** from codebase **Impact:** ```bash # This will FAIL in 0.82+: # gradle.properties (Android) newArchEnabled=false # โ Ignored, build fails # iOS RCT_NEW_ARCH_ENABLED=0 # โ Ignored, build fails ``` **Migration Path:** 1. Upgrade to 0.76-0.81 first (if on 0.75 or earlier) 2. Test with New Architecture enabled 3. Fix incompatible dependencies (Redux, i18n, CodePush) 4. Then upgrade to 0.82+ ### ๐ด propTypes Removed (React 19 / RN 0.78+) **What Changed:** React 19 removed `propTypes` completely. No runtime validation, no warnings - silently ignored. **Before (Old Code):** ```typescript import PropTypes from 'prop-types'; function MyComponent({ name, age }) { return <Text>{name} is {age}</Text>; } MyComponent.propTypes = { // โ Silently ignored in React 19 name: PropTypes.string.isRequired, age: PropTypes.number }; ``` **After (Use TypeScript):** ```typescript type MyComponentProps = { name: string; age?: number; }; function MyComponent({ name, age }: MyComponentProps) { return <Text>{name} is {age}</Text>; } ``` **Migration:** ```bash # Use React 19 codemod to remove propTypes npx @codemod/react-19 upgrade ``` ### ๐ด forwardRef Deprecated (React 19) **What Changed:** `forwardRef` no longer needed - pass `ref` as a regular prop. **Before (Old Code):** ```typescript import { forwardRef } from 'react'; const MyInput = forwardRef((props, ref) => { // โ Deprecated return <TextInput ref={ref} {...props} />; }); ``` **After (React 19):** ```typescript function MyInput({ ref, ...props }) { // โ ref is a regular prop return <TextInput ref={ref} {...props} />; } ``` ### ๐ด Swift iOS Template Default (0.77+) **What Changed:** New projects use Swift `AppDelegate.swift` instead of Objective-C `AppDelegate.mm`. **Old Structure:** ``` ios/MyApp/ โโโ main.m # โ Removed โโโ AppDelegate.h # โ Removed โโโ AppDelegate.mm # โ Removed ``` **New Structure:** ```swift // ios/MyApp/AppDelegate.swift โ import UIKit import React @main class AppDelegate: UIResponder, UIApplicationDelegate { func application(_ application: UIApplication, ...) -> Bool { // App initialization return true } } ``` **Migration (0.76 โ 0.77):** When upgrading existing projects, you **MUST** add this line: ```swift // Add to AppDelegate.swift during migration import React import ReactCoreModules RCTAppDependencyProvider.sharedInstance() // โ ๏ธ CRITICAL: Must add this! ``` **Source:** [React Native 0.77 Release Notes](https://reactnative.dev/blog/2025/01/14/release-0.77) ### ๐ด Metro Log Forwarding Removed (0.77+) **What Changed:** Metro terminal no longer streams `console.log()` output. **Before (0.76):** ```bash # console.log() appeared in Metro terminal $ npx expo start > LOG Hello from app! # โ Appeared here ``` **After (0.77+):** ```bash # console.log() does NOT appear in Metro terminal $ npx expo start # (no logs shown) # โ Removed # Workaround (temporary, will be removed): $ npx expo start --client-logs # Shows logs, deprecated ``` **Solution:** Use React Native DevTools Console instead (press 'j' in CLI). **Source:** [React Native 0.77 Release Notes](https://reactnative.dev/blog/2025/01/14/release-0.77) ### ๐ด Chrome Debugger Removed (0.79+) **What Changed:** Old Chrome debugger (`chrome://inspect`) removed. Use React Native DevTools instead. **Old Method (Removed):** ```bash # โ This no longer works: # Open Dev Menu โ "Debug" โ Chrome DevTools opens ``` **New Method (0.76+):** ```bash # Press 'j' in CLI or Dev Menu โ "Open React Native DevTools" # โ Uses Chrome DevTools Protocol (CDP) # โ Reliable breakpoints, watch values, stack inspection # โ JS Console (replaces Metro logs) ``` **Limitations:** - Third-party extensions not yet supported (Redux DevTools, etc.) - Network inspector coming in 0.83 (late 2025) **Source:** [React Native 0.79 Release Notes](https://reactnative.dev/blog/2025/04/release-0.79) ### ๐ด JSC Engine Moved to Community (0.79+) **What Changed:** JavaScriptCore (JSC) moved out of React Native core, Hermes is default. **Before (0.78):** - Both Hermes and JSC bundled - JSC available in Expo Go **After (0.79+):** ```json // If you still need JSC (rare): { "dependencies": { "@react-native-community/javascriptcore": "^1.0.0" } } ``` **Expo Go:** - JSC completely removed from Expo Go (SDK 52+) - Hermes only **Note:** JSC will eventually be removed entirely from React Native. ### ๐ด Deep Imports Deprecated (0.80+) **What Changed:** Importing from internal paths will break. **Before (Old Code):** ```typescript // โ Deep imports deprecated import Button from 'react-native/Libraries/Components/Button'; import Platform from 'react-native/Libraries/Utilities/Platform'; ``` **After:** ```typescript // โ Import only from 'react-native' import { Button, Platform } from 'react-native'; ``` **Source:** [React Native 0.80 Release Notes](https://reactnative.dev/blog/2025/06/release-0.80) --- ## New Features (Post-Dec 2024) ### CSS Properties (0.77+ New Architecture Only) React Native now supports many CSS properties previously only available on web: #### 1. `display: contents` Makes an element "invisible" but keeps its children in the layout: ```typescript <View style={{ display: 'contents' }}> {/* This View disappears, but Text still renders */} <Text>I'm still here!</Text> </View> ``` **Use case:** Wrapper components that shouldn't affect layout. #### 2. `boxSizing` Control how width/height are calculated: ```typescript // Default: padding/border inside box <View style={{ boxSizing: 'border-box', // Default width: 100, padding: 10, borderWidth: 2 // Total width: 100 (padding/border inside) }} /> // Content-box: padding/border outside <View style={{ boxSizing: 'content-box', width: 100, padding: 10, borderWidth: 2 // Total width: 124 (100 + 20 padding + 4 border) }} /> ``` #### 3. `mixBlendMode` + `isolation` Blend layers like Photoshop: ```typescript <View style={{ backgroundColor: 'red' }}> <View style={{ mixBlendMode: 'multiply', // 16 modes available backgroundColor: 'blue' // Result: purple (red ร blue) }} /> <
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context โ no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes โ information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development โ guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.