erne plan
- Repo stars 36
- License MIT
- Author repo everything-react-native-expo
- Domain
- Design
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 94 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @JubaKitiashvili · MIT
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No explicit requirements detected
- Detected file/system behavior
-
- Read-only
- Write / modify
- Shell exec
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
# Architecture Output
```
# /erne-plan — Feature Architecture Design
You are executing the `/erne-plan` command. Use the **architect** agent to design a feature architecture.
## Process
1. **Understand the requirement** — Ask clarifying questions if the feature description is vague
2. **Analyze existing codebase** — Read relevant files, understand current navigation structure, state management, and API patterns
3. **Design the architecture** — Using the architect agent's process:
- Decompose into components and screens
- Plan Expo Router file structure
- Select state management approach (Zustand / TanStack Query / local)
- Design data flow and API layer
- Consider platform-specific requirements
4. **Output the plan** — Use the architect agent's output format:
### Architecture Output
```
## Overview
[1-2 sentence description of the feature]
## File Structure
[New files to create with paths]
## Component Design
[Component hierarchy and responsibilities]
## Data Flow
[State management approach, API calls, caching strategy]
## Navigation
[New routes, layout changes, deep link support]
## Implementation Tasks
[Ordered list of implementation steps]
```
5. **Review with user** — Present the plan and ask for approval before implementation
## Notes
- Reference the active platform rules layer (`rules/expo/patterns.md` or `rules/bare-rn/patterns.md`) for conventions
- Consider whether this is Expo managed, bare RN, or has native modules
- Include test strategy in the plan
Sections and files
Listed in source order.
sections -> Process → Architecture Output → Notes
terms -> architect · Understand the requirement · Analyze existing codebase · Design the architecture · Output the plan · Review with user
files/cmd -> /erne-plan · rules/expo/patterns.md · rules/bare-rn/patterns.md
body sha256 -> f7ab31465f85
Process
Understand the requirement — Ask clarifying questions if the feature description is vague Analyze existing codebase — Read relevant files, understand current navigation structure, state management, and API patterns Design the architecture — Using the architect agent's process: Decompose into components and screens Plan Expo Router file structure
Architecture Output
Review with user — Present the plan and ask for approval before implementation
Notes
Reference the active platform rules layer (
rules/expo/patterns.mdorrules/bare-rn/patterns.md) for conventions Consider whether this is Expo managed, bare RN, or has native modules Include test strategy in the plan