react-native-architecture
$
npx mdskill add HoangNguyen0403/agent-skills-standard/react-native-architecture- **Feature-First**: Organize by feature/module, not by type. - **Colocation**: Keep related files together (screens, components, hooks within feature). - **Separation**: UI (screens/components) separate from logic (hooks/services).
SKILL.md
.github/skills/react-native-architectureView on GitHub ↗
---
name: react-native-architecture
description: Structure React Native projects with feature-first organization and separation of concerns. Use when structuring a React Native project or applying clean architecture patterns.
metadata:
triggers:
files:
- 'src/**/*.tsx'
- 'src/**/*.ts'
- 'app.json'
- 'StyleSheet.create'
keywords:
- feature
- module
- directory structure
- separation of concerns
- Expo
- React Navigation
- react-native
- mobile architecture
---
# React Native Architecture
## **Priority: P0 (CRITICAL)**
## Organize by Feature
- **Feature-First**: Organize by feature/module, not by type.
- **Colocation**: Keep related files together (screens, components, hooks within feature).
- **Separation**: UI (screens/components) separate from logic (hooks/services).
See [folder structure reference](references/folder-structure.md) for full directory tree and path alias configuration.
- **Atomic Components**: Reusable components in `/components`. Feature-specific in feature folder.
- **Absolute Imports**: Configure tsconfig.json paths for clean imports.
- **Single Responsibility**: Each file one clear purpose.
- **Expo vs CLI**: Structure works for both. Expo uses `app.json`, CLI uses `index.js`.
## Anti-Patterns
- **No Type-Based Folders**: Avoid `/containers`, `/screens` at root. Use features.
- **No Logic in Screens**: Extract to hooks or services.
- **No Circular Deps**: Features should not import from each other directly.
- **No Deep Nesting**: Max 3 levels deep.
## Navigation Strategy
- **Expo Router**: Use for new projects, web-parity, and file-based routing.
- **React Navigation**: Use for complex deep-linking, legacy apps, or high-customization needs.
## Verification Checklist (Mandatory)
- [ ] **Feature-First**: file inside feature directory?
- [ ] **Colocation**: hooks/services colocated with screens?
- [ ] **Logic-Free Screens**: there any business logic in screen component?
- [ ] **Navigation Choice**: project use navigation strategy defined above?
## References
See [references/folder-structure.md](references/folder-structure.md) for full directory tree, path alias config, and service layer patterns.More from HoangNguyen0403/agent-skills-standard
- android-agp-upgradeUpgrade an Android project to Android Gradle Plugin (AGP) 9. Use when migrating to AGP 9, updating Gradle build files, migrating to built-in Kotlin, or adopting the new AGP DSL.
- android-architectureApply Clean Architecture layering, modularization, and Unidirectional Data Flow in Android projects. Use when setting up project structure, placing code in layers, configuring feature/core modules, or implementing UDF patterns.
- android-background-workImplement WorkManager and background processing correctly on Android. Use when creating Worker classes, scheduling tasks, choosing between WorkManager and Foreground Services, or setting up Hilt in workers.
- android-composeBuild high-performance declarative UI with Jetpack Compose. Use when writing Composable functions, optimizing recomposition, hoisting state, or working with LazyColumn and side effects.
- android-compose-migrationMigrate an Android XML View to Jetpack Compose following a structured 10-step workflow. Use when converting XML layouts to Compose, setting up Compose in an existing View-based project, or incrementally adopting Compose.
- android-concurrencyWrite correct coroutine scopes, Flow collection, and dispatcher injection in Android. Use when writing suspend functions, choosing between StateFlow and SharedFlow, or injecting Dispatchers for testability.
- android-deploymentConfigure release signing, R8 obfuscation, and App Bundle publishing for Android. Use when setting up signing configs, enabling minification, adding ProGuard keep rules, or preparing for Play Store submission.
- android-design-systemEnforce Material Design 3 theming and design token usage in Jetpack Compose. Use when implementing M3 components, color schemes, typography, or design tokens.
- android-diConfigure Hilt dependency injection with proper scoping, modules, and constructor injection in Android. Use when setting up Hilt DI, defining modules, or configuring component scoping.
- android-edge-to-edgeMigrate a Jetpack Compose app to edge-to-edge display and fix system bar inset issues. Use when UI components are obscured by navigation/status bars, fixing IME insets, or enabling edge-to-edge for SDK 35+.