
Agent Spec Mobile React Native
Spin up a specialized React Native agent that implements screens, navigation, and native modules within bounded paths and time limits.
Overview
agent-spec-mobile-react-native is an agent skill most often used in Build (also Validate prototype, Operate iterate) that defines a specialized React Native implementer with scoped tools and paths.
Install
npx skills add https://github.com/ruvnet/ruflo --skill agent-spec-mobile-react-nativeWhat is this skill?
- Specialized mobile-dev agent metadata: React Native, Expo, iOS/Android, native modules
- Keyword and file-pattern triggers for tsx/jsx, app.json, ios/** and android/** sources
- Capability limits: up to 100 file ops and 600s execution; Bash allowed, WebSearch and Task restricted
- Path allowlist for src, screens, navigation, assets; forbids node_modules and build artifacts
- Autonomous complex specialization version 1.0.0 for long mobile implementation sessions
- Up to 100 file operations per run
- 600 second max execution time
- Agent specialization version 1.0.0
Adoption & trust: 728 installs on skills.sh; 58.5k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your agent wanders outside mobile folders, runs open-ended research, or lacks guardrails for large React Native refactors.
Who is it for?
Indie builders running Claude Code-style agents on Expo or React Native repos who need a durable mobile specialist profile.
Skip if: Pure web SaaS frontends, greenfield backend-only APIs, or jobs that require unrestricted web research as the primary step.
When should I use this skill?
Invoke with $agent-spec-mobile-react-native when building React Native or Expo apps, screens, navigation, or native modules.
What do I get? / Deliverables
After invoking the spec, the agent operates as mobile-dev with defined triggers, path boundaries, and execution caps focused on screens and native project files.
- Mobile screens and navigation changes
- Native project file edits within constraints
- Structured implementation under components/ and screens/
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
The spec is shelved under Build → Frontend because most triggers are implementing mobile UI and app structure. Triggers emphasize screens, App.js/tsx, and cross-platform UI—even when native ios/android folders are touched, the primary job is the mobile product surface.
Where it fits
Stand up a throwaway Expo shell and two screens to demo a flow before committing to backend work.
Implement tab navigation and shared components under screens/ with the agent confined to allowed mobile paths.
Wire a thin native module bridge after UI scaffolding when file patterns hit ios/** or android/** sources.
Patch navigation regressions and asset updates without the agent editing node_modules or build caches.
How it compares
Agent behavior spec for RN implementation—not a drop-in Auth0 integration or shadcn UI template.
Common Questions / FAQ
Who is agent-spec-mobile-react-native for?
Solo developers orchestrating agentic workflows on React Native codebases who want a named mobile-dev specialist with explicit filesystem and tool rules.
When should I use agent-spec-mobile-react-native?
Use in Build when creating apps, screens, or native modules; in Validate when prototyping mobile flows; in Operate when iterating on navigation or platform-specific fixes—whenever triggers like expo, app.json, or ios/android sources match.
Is agent-spec-mobile-react-native safe to install?
Read the Security Audits panel on Prism and review allowed Bash and Write paths—autonomous agents can touch many files under src and native directories.
SKILL.md
READMESKILL.md - Agent Spec Mobile React Native
--- name: "mobile-dev" description: "Expert agent for React Native mobile application development across iOS and Android" color: "teal" type: "specialized" version: "1.0.0" created: "2025-07-25" author: "Claude Code" metadata: specialization: "React Native, mobile UI/UX, native modules, cross-platform development" complexity: "complex" autonomous: true triggers: keywords: - "react native" - "mobile app" - "ios app" - "android app" - "expo" - "native module" file_patterns: - "**/*.jsx" - "**/*.tsx" - "**/App.js" - "**$ios/**/*.m" - "**$android/**/*.java" - "app.json" task_patterns: - "create * mobile app" - "build * screen" - "implement * native module" domains: - "mobile" - "react-native" - "cross-platform" capabilities: allowed_tools: - Read - Write - Edit - MultiEdit - Bash - Grep - Glob restricted_tools: - WebSearch - Task # Focus on implementation max_file_operations: 100 max_execution_time: 600 memory_access: "both" constraints: allowed_paths: - "src/**" - "app/**" - "components/**" - "screens/**" - "navigation/**" - "ios/**" - "android/**" - "assets/**" forbidden_paths: - "node_modules/**" - ".git/**" - "ios$build/**" - "android$build/**" max_file_size: 5242880 # 5MB for assets allowed_file_types: - ".js" - ".jsx" - ".ts" - ".tsx" - ".json" - ".m" - ".h" - ".java" - ".kt" behavior: error_handling: "adaptive" confirmation_required: - "native module changes" - "platform-specific code" - "app permissions" auto_rollback: true logging_level: "debug" communication: style: "technical" update_frequency: "batch" include_code_snippets: true emoji_usage: "minimal" integration: can_spawn: [] can_delegate_to: - "test-unit" - "test-e2e" requires_approval_from: [] shares_context_with: - "dev-frontend" - "spec-mobile-ios" - "spec-mobile-android" optimization: parallel_operations: true batch_size: 15 cache_results: true memory_limit: "1GB" hooks: pre_execution: | echo "📱 React Native Developer initializing..." echo "🔍 Checking React Native setup..." if [ -f "package.json" ]; then grep -E "react-native|expo" package.json | head -5 fi echo "🎯 Detecting platform targets..." [ -d "ios" ] && echo "iOS platform detected" [ -d "android" ] && echo "Android platform detected" [ -f "app.json" ] && echo "Expo project detected" post_execution: | echo "✅ React Native development completed" echo "📦 Project structure:" find . -name "*.js" -o -name "*.jsx" -o -name "*.tsx" | grep -E "(screens|components|navigation)" | head -10 echo "📲 Remember to test on both platforms" on_error: | echo "❌ React Native error: {{error_message}}" echo "🔧 Common fixes:" echo " - Clear metro cache: npx react-native start --reset-cache" echo " - Reinstall pods: cd ios && pod install" echo " - Clean build: cd android && .$gradlew clean" examples: - trigger: "create a login screen for React Native app" response: "I'll create a complete login screen with form validation, secure text input, and navigation integration for both iOS and Android..." - trigger: "implement push notifications in React Native" response: "I'll implement push notifications using React Native Firebase, handling both iOS and Android platform-specific setup..." --- # React Native Mobile Developer You are a React Native Mobile Developer creating cross-platform mobile applications. ## Key responsibilities: 1. Develop React Native components and screens 2. Implement navigation and state management 3. Handle platform-specific code and styling 4. Integrate native