Automated summary
This skill scaffolds a full React Native (Expo) project by asking for the project name, description, target platforms, authentication, navigation, and internationalization, then reads architecture reference files and uses Context7 for up-to-date library docs.
Strengths
- Automates initial setup with guided choices
- Integrates mobile design best practices and architecture patterns
- Uses Context7 for latest API versions
- Includes mandatory mobile design checkpoints
Limitations
- Requires Context7 to be configured or user must manually provide docs
- Code generation depends on reading many reference files, which can be slow
- Does not cover deployment or CI/CD setup
Use this skill when starting a new React Native (Expo) project and want a robust foundation with proven architecture.
Do not use it for adding features to an existing project, as it is designed for full scaffolding.
Security analysis
SafeThe skill contains only standard project initialization commands (npx create-expo-app, npm install, etc.) and no destructive, exfiltrating, or obfuscated instructions. It prompts the user for input and suggests optional tools like Context7 MCP, but does not execute any risky operations automatically.
No concerns found
How this analysis is madeExamples
Scaffold a new React Native Expo project called 'FreshCart' for a grocery delivery app targeting both iOS and Android. Include authentication, tabs+stack navigation, internationalization, and use Context7 for fetching the latest library docs.Scaffold a React Native Expo project named 'MyApp' for learning purposes, targeting only iOS, no authentication, stack-only navigation, and no i18n. I don't have Context7 set up, so proceed with the architecture reference files.Create a new React Native Expo project 'TaskMaster' for a task management app targeting Android only. Use drawer+stack navigation, include authentication and internationalization. Use Context7 for latest docs.React Native Arc — Project Scaffolding Skill
You are scaffolding a new React Native (Expo) project using the arc-skill architecture.
Pre-Flight
-
Ask the user for:
- Project name (used in
app.json, package name, display name) - Brief description of the app (to inform screen/feature choices)
- Target platforms: iOS only, Android only, or both
- Whether they need i18n (internationalization) — default: yes
- Whether they need authentication flow — default: yes
- Which navigation pattern:
tabs + stack(default) orstack onlyordrawer + stack
- Project name (used in
-
Context7 (mandatory): Ask the user to connect Context7 MCP server if not already configured. Use it to fetch the latest docs for:
react-native— core APIs and New Architectureexpo— SDK setup and latest modules@react-navigation/native— navigation@tanstack/react-query— server statereact-native-mmkv— storagereact-native-reanimated— animations
Tell the user: "Do you have Context7 MCP connected? It fetches up-to-date library docs so the generated code uses the latest APIs. If not, add it: https://github.com/upstash/context7" If the user confirms they don't have it and don't want to add it, proceed with the architecture reference files.
-
Expo Skills (recommended): Check if the user has Expo community skills installed. If not, suggest they look into Expo's official documentation for AI-assisted development patterns covering native UI, deployment, and SDK upgrades.
-
Mobile Design Checkpoint (mandatory): Before writing any code, read
skills/arc-skill/mobile-design/GUIDE.mdand complete:Platform: [iOS / Android / Both] Framework: React Native (Expo) 3 Principles I Will Apply: 1. Touch-first (44pt+ targets, thumb zone aware) 2. Platform-respectful (iOS HIG / Material Design 3) 3. Performance-first (FlatList, Reanimated, memo) Anti-Patterns I Will Avoid: 1. ScrollView for lists 2. Hardcoded pixel values 3. Inline styles / anonymous functions in render
Architecture Reference Files
Read the following skill files from skills/arc-skill/ to understand the full architecture before generating code:
Core Architecture:
project-structure.md— Complete folder structurenavigation.md— React Navigation patternstheme.md— Theme system with color schemescomponents.md— Component file structure & patternsapi-services.md— Axios HTTP client & API layerstorage.md— MMKV storage wrapperstate-management.md— React Query setup & patternsperformance.md— React Native performance best practicesproviders.md— Provider stack architecturetypescript.md— TypeScript conventionslinting.md— ESLint, Prettier, Husky, lint-stagedi18n.md— Internationalization with Lingui
Mobile Design System (ALWAYS read — these are mandatory, not optional):
13. mobile-design/GUIDE.md — Master checklist & anti-patterns
14. mobile-design/touch-psychology.md — Touch targets, thumb zones, haptics
15. mobile-design/mobile-performance.md — Deep performance optimization
16. mobile-design/mobile-navigation.md — Navigation UX patterns
17. mobile-design/mobile-typography.md — Type scales, Dynamic Type
18. mobile-design/mobile-color-system.md — OLED, dark mode, contrast
19. mobile-design/platform-ios.md — iOS HIG specifics (read if targeting iOS)
20. mobile-design/platform-android.md — Material Design 3 specifics (read if targeting Android)
21. mobile-design/mobile-backend.md — Offline sync, push, auth patterns
22. mobile-design/decision-trees.md — Framework & architecture decisions
23. mobile-design/mobile-design-thinking.md — Anti-memorization, forces context-based thinking
Template Files
Read templates from skills/arc-skill/templates/ for code generation patterns:
component.md— Component file templatesscreen.md— Screen file templateshook.md— Custom hook templatesapi-service.md— API service module templates
Execution Steps
Step 1: Initialize Expo Project
npx create-expo-app@latest <project-name> --template blank-typescript
cd <project-name>
Step 2: Install Core Dependencies
Always use npx expo install for Expo-compatible packages (resolves correct versions). Use latest — do NOT pin versions. Install in this order (groups can be parallel):
Navigation:
npx expo install @react-navigation/native @react-navigation/native-stack @react-navigation/bottom-tabs react-native-screens react-native-safe-area-context
State & Storage:
npx expo install @tanstack/react-query @tanstack/react-query-persist-client react-native-mmkv
HTTP:
npx expo install axios
UI & Animations:
npx expo install react-native-reanimated react-native-gesture-handler react-native-size-matters expo-blur expo-haptics expo-status-bar expo-image expo-splash-screen expo-font @expo/vector-icons react-native-keyboard-controller
Forms (if auth flow):
npx expo install formik yup
i18n (if enabled):
npm install @lingui/react @lingui/core
npm install -D @lingui/cli @lingui/macro @lingui/babel-plugin-lingui-macro
npx expo install expo-localization
Dev tools:
npm install -D typescript @types/react eslint prettier eslint-config-expo husky lint-staged babel-plugin-module-resolver
Verify compatibility:
npx expo doctor
Fix any version mismatches before proceeding. Follow expo doctor recommendations.
Step 3: Generate Project Structure
Create the full src/ directory structure as defined in project-structure.md.
Step 4: Generate Core Files
Generate files in this order (respecting dependencies):
- Types (
src/types/) — Base type definitions - Constants (
src/constants/) — App constants, keys, platform utils - Theme (
src/theme/) — Theme definitions, interfaces, fonts - Storage (
src/store/storage/) — MMKV storage wrappers - API Client (
src/api/http/index.ts) — Axios instance with interceptors - API Modules (
src/api/http/) — Auth, profile, etc. - Store Services (
src/store/services/) — React Query client, hooks - Hooks (
src/hooks/) — useAppTheme, useAppNavigation, useStyles - Providers (
src/providers/) — AppInitialization, i18n - Components (
src/components/) — Shared UI components - Screens (
src/screens/) — App screens - Navigation (
src/navigation/) — Navigator setup - App Entry (
src/app.tsx) — Root component with provider stack - i18n (
src/locale/) — If i18n enabled
Step 5: Configure Build Tools
- Update
tsconfig.jsonwith path aliases (seetypescript.md) - Update
babel.config.jsfor reanimated + lingui + module-resolver plugins - Create ESLint config,
.prettierrc,.prettierignore(seelinting.md) - Set up Husky + lint-staged for pre-commit hooks (see
linting.md) - Add
lint,format,typecheck,checkscripts topackage.json - Create
.env.example - Update
app.jsonwith project metadata + enable React Compiler:{ "expo": { "experiments": { "reactCompiler": true } } }
Step 6: Verify
npx react-compiler-healthcheck@latest
npx expo doctor
npx expo start
Important Rules
Architecture:
- Always use the component file structure from
components.md— separate files for styles, types, constants - Always use
react-native-size-mattersmoderateScale— never hardcode pixel sizes - Always type navigation — use typed
useAppNavigation()hook - Always use the
useStyles()hook — never callStyleSheet.createdirectly in components - Follow the barrel export pattern — every folder has an
index.ts - API calls go through React Query — never call API functions directly from components
- Storage access through typed wrappers — never use MMKV directly in components
Mobile UX (from mobile-design system):
- Touch targets minimum 44pt (iOS) / 48dp (Android) — see
touch-psychology.md - Primary CTAs in thumb-friendly zone (bottom of screen)
- Never gesture-only interactions — always provide visible button alternative
- Haptic feedback for meaningful interactions
- Support Dynamic Type / font scaling — use
spon Android - Dark mode: use
#121212not pure#000000for surfaces (avoid OLED smearing) - Text contrast minimum 4.5:1 (WCAG AA)
- Platform-respectful: iOS follows HIG, Android follows Material Design 3
Performance (from performance.md + mobile-performance.md):
- FlatList for lists — never ScrollView for dynamic/long lists
- Reanimated for animations (UI thread) — never Animated API for complex animations
expo-imageinstead of React NativeImage— with caching and blurhashfreezeOnBluron tab screens- Clean up timers, listeners, subscriptions in useEffect cleanup
- Remove all
console.logbefore production - React Compiler handles memoization — do NOT manually add
React.memo,useCallback, oruseMemo
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/react-native-arc-project-scaffolding-mrx3y06w/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/react-native-arc-project-scaffolding-mrx3y06w' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/react-native-arc-project-scaffolding-mrx3y06w/download' --output '.skill-downloads/react-native-arc-project-scaffolding-mrx3y06w/SKILL.md.part' && mv '.skill-downloads/react-native-arc-project-scaffolding-mrx3y06w/SKILL.md.part' '.skill-downloads/react-native-arc-project-scaffolding-mrx3y06w/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.
Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/react-native-arc-project-scaffolding-mrx3y06w/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.