erne code
- Repo stars 36
- License MIT
- Author repo everything-react-native-expo
- Domain
- Engineering
- 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.
# /erne-code — Feature Implementation
You are executing the `/erne-code` command. Use the **senior-developer** agent to implement production-grade feature code.
## Process
1. **Understand the task** — Read any existing architecture plan or feature description. If none exists, ask for scope and requirements.
2. **Analyze existing codebase** — Read relevant files, understand current patterns, state management, and navigation structure
3. **Implement end-to-end** — Using the senior-developer agent's process:
- Set up the file skeleton and type definitions
- Implement data layer first (API client, queries/mutations, stores)
- Build screens with all states handled (loading, error, empty, success)
- Wire navigation (route params, transitions, deep links)
- Handle edge cases (offline, token expiry, race conditions)
4. **Self-review** — Check for re-renders, missing error handling, accessibility, type safety
5. **Deliver** — Complete implementation with file paths, type definitions, and integration notes
## When to Use
- Implementing a feature from an architect plan
- Building screens, hooks, API integration, and state management
- End-to-end feature work that touches multiple files
## Notes
- Reference the active platform rules layer for conventions
- Follow the project's import ordering: react -> react-native -> expo -> external -> internal -> types
- If the task is a single isolated unit (one screen, one hook), consider `/erne-feature` instead
Sections and files
Listed in source order.
sections -> Process → When to Use → Notes
terms -> senior-developer · Understand the task · Analyze existing codebase · Implement end-to-end · Self-review · Deliver
files/cmd -> /erne-code · /erne-feature · queries/mutations
body sha256 -> c6ddd2df59ca
Process
Understand the task — Read any existing architecture plan or feature description. If none exists, ask for scope and requirements. Analyze existing codebase — Read relevant files, understand current patterns, state management, and navigation structure Implement end-to-end — Using the senior-developer agent's process: Set up the file skeleton and type definitions Implement data layer first (API client, queries/mutations, stores)
When to Use
Implementing a feature from an architect plan Building screens, hooks, API integration, and state management End-to-end feature work that touches multiple files
Notes
Reference the active platform rules layer for conventions Follow the project's import ordering: react -> react-native -> expo -> external -> internal -> types If the task is a single isolated unit (one screen, one hook), consider
/erne-featureinstead