erne-universal 0.5.1 → 0.6.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CLAUDE.md +52 -1
- package/README.md +177 -105
- package/agents/architect.md +60 -0
- package/agents/code-reviewer.md +73 -0
- package/agents/expo-config-resolver.md +59 -0
- package/agents/feature-builder.md +58 -0
- package/agents/native-bridge-builder.md +63 -0
- package/agents/performance-profiler.md +61 -1
- package/agents/pipeline-orchestrator.md +160 -0
- package/agents/senior-developer.md +60 -0
- package/agents/tdd-guide.md +58 -0
- package/agents/ui-designer.md +60 -0
- package/agents/upgrade-assistant.md +58 -0
- package/agents/variants/architect/monorepo.md +42 -1
- package/agents/variants/architect/redux.md +42 -1
- package/agents/variants/architect/zustand.md +42 -1
- package/agents/variants/feature-builder/legacy-bare.md +43 -2
- package/agents/variants/feature-builder/modern-expo.md +42 -1
- package/agents/variants/senior-developer/legacy-bare.md +43 -2
- package/agents/variants/senior-developer/modern-expo.md +42 -1
- package/agents/variants/ui-designer/nativewind.md +47 -1
- package/agents/variants/ui-designer/stylesheet.md +42 -1
- package/bin/cli.js +33 -10
- package/commands/code.md +33 -0
- package/commands/feature.md +37 -0
- package/commands/orchestrate.md +115 -0
- package/commands/plan.md +1 -1
- package/dashboard/public/agents.js +14 -0
- package/dashboard/public/canvas.js +4 -1
- package/dashboard/public/panel.js +4 -1
- package/dashboard/public/toasts.js +1 -1
- package/dashboard/public/ws-client.js +0 -3
- package/dashboard/server.js +26 -5
- package/docs/agents.md +4 -3
- package/docs/commands.md +3 -0
- package/docs/getting-started.md +33 -7
- package/docs/hooks-profiles.md +18 -8
- package/examples/runbook-bug-fix.md +412 -0
- package/examples/workflow-new-feature.md +338 -0
- package/examples/workflow-new-screen.md +450 -0
- package/examples/workflow-upgrade.md +355 -0
- package/hooks/hooks.json +0 -7
- package/hooks/profiles/minimal.json +2 -1
- package/hooks/profiles/standard.json +2 -1
- package/hooks/profiles/strict.json +2 -2
- package/lib/add-agent.js +142 -0
- package/lib/claude-md.js +22 -13
- package/lib/dashboard.js +56 -19
- package/lib/detect.js +136 -23
- package/lib/doctor.js +254 -0
- package/lib/generate.js +2 -9
- package/lib/start.js +40 -1
- package/lib/status.js +174 -0
- package/lib/sync-configs.js +408 -0
- package/lib/update.js +9 -2
- package/package.json +16 -5
- package/scripts/hooks/accessibility-check.js +1 -1
- package/scripts/hooks/bundle-size-check.js +45 -15
- package/scripts/hooks/check-reanimated-worklet.js +48 -19
- package/scripts/lint-agents.js +138 -0
- package/scripts/validate-all.js +2 -2
- package/scripts/hooks/performance-budget.js +0 -57
package/CLAUDE.md
CHANGED
|
@@ -46,9 +46,60 @@ You are working in an ERNE-powered React Native/Expo project.
|
|
|
46
46
|
- Branch naming: `feat/`, `fix/`, `refactor/` prefix
|
|
47
47
|
- Atomic commits — one logical change per commit
|
|
48
48
|
|
|
49
|
+
## Workflow Orchestration
|
|
50
|
+
|
|
51
|
+
### 1. Plan Mode Default
|
|
52
|
+
- Enter plan mode for ANY non-trivial task (3+ steps or architectural decisions)
|
|
53
|
+
- If something goes sideways, STOP and re-plan immediately — don't keep pushing
|
|
54
|
+
- Use plan mode for verification steps, not just building
|
|
55
|
+
- Write detailed specs upfront to reduce ambiguity
|
|
56
|
+
|
|
57
|
+
### 2. Subagent Strategy
|
|
58
|
+
- Use subagents liberally to keep main context window clean
|
|
59
|
+
- Offload research, exploration, and parallel analysis to subagents
|
|
60
|
+
- For complex problems, throw more compute at it via subagents
|
|
61
|
+
- One task per subagent for focused execution
|
|
62
|
+
|
|
63
|
+
### 3. Self-Improvement Loop
|
|
64
|
+
- After ANY correction from the user: save a `feedback` memory via the memory system
|
|
65
|
+
- Write rules for yourself that prevent the same mistake
|
|
66
|
+
- Memory is auto-loaded each session — no manual review needed
|
|
67
|
+
|
|
68
|
+
### 4. Verification Before Done
|
|
69
|
+
- Never mark a task complete without proving it works
|
|
70
|
+
- Diff behavior between main and your changes when relevant
|
|
71
|
+
- Ask yourself: "Would a staff engineer approve this?"
|
|
72
|
+
- Run tests, check logs, demonstrate correctness
|
|
73
|
+
|
|
74
|
+
### 5. Demand Elegance (Balanced)
|
|
75
|
+
- For non-trivial changes: pause and ask "is there a more elegant way?"
|
|
76
|
+
- If a fix feels hacky: "Knowing everything I know now, implement the elegant solution"
|
|
77
|
+
- Skip this for simple, obvious fixes — don't over-engineer
|
|
78
|
+
- Challenge your own work before presenting it
|
|
79
|
+
|
|
80
|
+
### 6. Autonomous Bug Fixing
|
|
81
|
+
- When given a bug report: just fix it. Don't ask for hand-holding
|
|
82
|
+
- Point at logs, errors, failing tests — then resolve them
|
|
83
|
+
- Zero context switching required from the user
|
|
84
|
+
- Go fix failing CI tests without being told how
|
|
85
|
+
|
|
86
|
+
## Task Management
|
|
87
|
+
|
|
88
|
+
1. **Plan First**: Use plan mode or TodoWrite for non-trivial tasks
|
|
89
|
+
2. **Verify Plan**: Check in before starting implementation
|
|
90
|
+
3. **Track Progress**: Use built-in task system (TodoWrite/TaskCreate) to mark progress
|
|
91
|
+
4. **Explain Changes**: High-level summary at each step
|
|
92
|
+
5. **Capture Lessons**: Save corrections as `feedback` memories
|
|
93
|
+
|
|
94
|
+
## Core Principles
|
|
95
|
+
|
|
96
|
+
- **Simplicity First**: Make every change as simple as possible. Impact minimal code.
|
|
97
|
+
- **No Laziness**: Find root causes. No temporary fixes. Senior developer standards.
|
|
98
|
+
- **Minimal Impact**: Changes should only touch what's necessary. Avoid introducing bugs.
|
|
99
|
+
|
|
49
100
|
## Available Commands
|
|
50
101
|
|
|
51
|
-
Use `/plan`, `/code-review`, `/tdd`, `/build-fix`, `/perf`, `/upgrade`, `/native-module`, `/navigate`, `/animate`, `/deploy`, `/component`, `/debug`, `/quality-gate` for guided workflows.
|
|
102
|
+
Use `/plan`, `/code-review`, `/tdd`, `/build-fix`, `/perf`, `/upgrade`, `/native-module`, `/navigate`, `/animate`, `/deploy`, `/component`, `/debug`, `/quality-gate`, `/code`, `/feature`, `/learn`, `/retrospective`, `/setup-device` for guided workflows.
|
|
52
103
|
|
|
53
104
|
## Available Skills
|
|
54
105
|
|
package/README.md
CHANGED
|
@@ -1,55 +1,53 @@
|
|
|
1
|
-
#
|
|
1
|
+
# 🏗️ ERNE — Everything React Native & Expo
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
> **The complete AI coding agent harness for React Native and Expo** — 11 specialized agents, adaptive stack detection, multi-agent orchestration, and a pixel-art dashboard. Every config is generated to match *your* exact project setup.
|
|
4
|
+
|
|
5
|
+
[](https://www.npmjs.com/package/erne-universal)
|
|
6
|
+
[](https://github.com/JubaKitiashvili/everything-react-native-expo)
|
|
7
|
+
[](https://opensource.org/licenses/MIT)
|
|
8
|
+
[](https://makeapullrequest.com)
|
|
4
9
|
|
|
5
10
|
<p align="center">
|
|
6
|
-
<video src="demo-dashboard.mp4" autoplay loop muted playsinline width="800"></video>
|
|
11
|
+
<video src="https://github.com/JubaKitiashvili/everything-react-native-expo/raw/main/demo-dashboard.mp4" autoplay loop muted playsinline width="800"></video>
|
|
7
12
|
</p>
|
|
8
13
|
|
|
9
|
-
|
|
14
|
+
---
|
|
15
|
+
|
|
16
|
+
## ⚡ Quick Start
|
|
10
17
|
|
|
11
18
|
```bash
|
|
12
19
|
npx erne-universal init
|
|
13
20
|
```
|
|
14
21
|
|
|
15
22
|
This will:
|
|
16
|
-
1. **Deep-scan your project** — detects 15 stack dimensions (state management, navigation, styling, lists, images, forms, storage, testing, build system, component style, monorepo, New Architecture, and more)
|
|
17
|
-
2. Let you choose a hook profile (minimal / standard / strict)
|
|
18
|
-
3. Select MCP integrations (simulator control, GitHub, etc.)
|
|
19
|
-
4. **Generate adaptive configuration** — selects from 24 variant templates matched to your exact stack (Zustand vs Redux, Expo Router vs React Navigation, NativeWind vs StyleSheet, etc.)
|
|
23
|
+
1. 🔍 **Deep-scan your project** — detects 15 stack dimensions (state management, navigation, styling, lists, images, forms, storage, testing, build system, component style, monorepo, New Architecture, and more)
|
|
24
|
+
2. 🎚️ Let you choose a hook profile (minimal / standard / strict)
|
|
25
|
+
3. 🔌 Select MCP integrations (simulator control, GitHub, etc.)
|
|
26
|
+
4. ⚙️ **Generate adaptive configuration** — selects from 24 variant templates matched to your exact stack (Zustand vs Redux, Expo Router vs React Navigation, NativeWind vs StyleSheet, etc.)
|
|
27
|
+
|
|
28
|
+
---
|
|
20
29
|
|
|
21
|
-
## What's Included
|
|
30
|
+
## 📦 What's Included
|
|
22
31
|
|
|
23
32
|
| Component | Count | Description |
|
|
24
33
|
|-----------|-------|-------------|
|
|
25
|
-
| Agents |
|
|
26
|
-
| Agent variants | 9 | Stack-adaptive agent configurations (StyleSheet vs NativeWind, Zustand vs Redux, etc.) |
|
|
27
|
-
| Commands |
|
|
28
|
-
| Rule layers | 5 | Conditional rules: common, expo, bare-rn, native-ios, native-android |
|
|
29
|
-
| Rule variants | 15 | Stack-specific rules selected by deep detection (state, navigation, styling, security, etc.) |
|
|
30
|
-
| Hook profiles | 3 | Minimal, standard, strict — quality enforcement your way |
|
|
31
|
-
| Skills |
|
|
32
|
-
| Contexts | 3 | Behavior modes: dev, review, vibe |
|
|
33
|
-
| MCP configs | 10 | Pre-configured server integrations |
|
|
34
|
-
|
|
35
|
-
|
|
34
|
+
| 🤖 Agents | 11 | Specialized AI agents for architecture, development, review, testing, UI, native, orchestration |
|
|
35
|
+
| 🔀 Agent variants | 9 | Stack-adaptive agent configurations (StyleSheet vs NativeWind, Zustand vs Redux, etc.) |
|
|
36
|
+
| ⚡ Commands | 19 | Slash commands for every React Native workflow |
|
|
37
|
+
| 📏 Rule layers | 5 | Conditional rules: common, expo, bare-rn, native-ios, native-android |
|
|
38
|
+
| 🎯 Rule variants | 15 | Stack-specific rules selected by deep detection (state, navigation, styling, security, etc.) |
|
|
39
|
+
| 🛡️ Hook profiles | 3 | Minimal, standard, strict — quality enforcement your way |
|
|
40
|
+
| 📚 Skills | 7 | Reusable knowledge modules loaded on-demand |
|
|
41
|
+
| 🎭 Contexts | 3 | Behavior modes: dev, review, vibe |
|
|
42
|
+
| 🔌 MCP configs | 10 | Pre-configured server integrations |
|
|
43
|
+
| 📋 Workflow examples | 4 | End-to-end multi-agent workflow guides |
|
|
44
|
+
| 🤝 Handoff templates | 4 | Structured agent-to-agent context passing |
|
|
36
45
|
|
|
37
|
-
|
|
46
|
+
---
|
|
38
47
|
|
|
39
|
-
|
|
40
|
-
|-----------|-------------|---------|
|
|
41
|
-
| **Profile-gated hooks** | Minimal profile runs 3 hooks instead of 17 | ~31% |
|
|
42
|
-
| **Conditional rules** | Only loads rules matching your project type (Expo, bare RN, native) | ~26% |
|
|
43
|
-
| **On-demand skills** | Skills load only when their command is invoked, not always in context | ~12% |
|
|
44
|
-
| **Subagent isolation** | Fresh agent per task with only its own definition + relevant rules | ~12% |
|
|
45
|
-
| **Task-specific commands** | 16 focused prompts instead of one monolithic instruction set | ~13% |
|
|
46
|
-
| **Context-based behavior** | Modes change behavior dynamically without loading new rulesets | ~3% |
|
|
47
|
-
|
|
48
|
-
**Result:** Typical workflows use **60–67% fewer tokens** compared to a naive all-in-context approach. Vibe mode (minimal profile) reaches 67% savings, standard development 64%, and even strict mode saves 57%.
|
|
48
|
+
## 🎮 Agent Dashboard
|
|
49
49
|
|
|
50
|
-
|
|
51
|
-
|
|
52
|
-
ERNE includes a real-time pixel-art dashboard that visualizes all 10 agents working in an animated office environment.
|
|
50
|
+
ERNE includes a real-time pixel-art dashboard that visualizes all 11 agents working in an animated office environment.
|
|
53
51
|
|
|
54
52
|
```bash
|
|
55
53
|
erne dashboard # Start on port 3333, open browser
|
|
@@ -59,69 +57,122 @@ erne start # Init project + dashboard in background
|
|
|
59
57
|
```
|
|
60
58
|
|
|
61
59
|
**Features:**
|
|
62
|
-
- 4 office rooms — Development, Code Review, Testing, and Conference
|
|
63
|
-
-
|
|
64
|
-
-
|
|
65
|
-
-
|
|
66
|
-
-
|
|
67
|
-
-
|
|
68
|
-
-
|
|
69
|
-
-
|
|
70
|
-
-
|
|
71
|
-
- Real-time status updates via WebSocket (connected to Claude Code hooks)
|
|
72
|
-
- Auto-reconnect with exponential backoff
|
|
73
|
-
|
|
74
|
-
The dashboard hooks into Claude Code's `PreToolUse` and `PostToolUse` events (pattern: `Agent`) to track which agents are actively working and what they're doing.
|
|
75
|
-
|
|
76
|
-
## IDE & Editor Support
|
|
60
|
+
- 🏢 4 office rooms — Development, Code Review, Testing, and Conference
|
|
61
|
+
- 🎨 11 animated agent sprites with walking, typing, and done animations
|
|
62
|
+
- 💬 Thought bubbles showing the current task above working agents
|
|
63
|
+
- 🖥️ Animated monitor screens (green code when working, screensaver when idle)
|
|
64
|
+
- 🔔 Toast notifications for agent start/complete events
|
|
65
|
+
- 📊 Bottom stats bar with session duration, tasks completed, working/planning counts
|
|
66
|
+
- 👤 Agent detail overlay with full activity history (click any agent)
|
|
67
|
+
- 🎯 Pipeline orchestrator coordination view in conference room
|
|
68
|
+
- 🔄 Real-time WebSocket updates with auto-reconnect
|
|
77
69
|
|
|
78
|
-
|
|
70
|
+
---
|
|
79
71
|
|
|
80
|
-
|
|
81
|
-
|
|
82
|
-
|
|
83
|
-
|
|
84
|
-
|
|
85
|
-
|
|
86
|
-
|
|
87
|
-
|
|
72
|
+
## 🎯 Multi-Agent Orchestration
|
|
73
|
+
|
|
74
|
+
ERNE supports coordinated multi-agent workflows through the pipeline orchestrator:
|
|
75
|
+
|
|
76
|
+
```bash
|
|
77
|
+
/orchestrate "build user profile screen"
|
|
78
|
+
```
|
|
79
|
+
|
|
80
|
+
**Pipeline phases:**
|
|
81
|
+
|
|
82
|
+
```
|
|
83
|
+
🏗️ Plan architect decomposes the task
|
|
84
|
+
↓
|
|
85
|
+
⚡ Implement senior-developer + feature-builder (parallel)
|
|
86
|
+
↓
|
|
87
|
+
🧪 Test tdd-guide writes and runs tests
|
|
88
|
+
↓
|
|
89
|
+
🔍 Review code-reviewer validates with evidence
|
|
90
|
+
↓
|
|
91
|
+
📊 Validate performance-profiler checks performance
|
|
92
|
+
```
|
|
93
|
+
|
|
94
|
+
Features retry logic (max 3 attempts), escalation to user on persistent failures, and structured [handoff templates](docs/handoff-templates.md) for context passing between agents. See [Pipeline Documentation](docs/pipeline.md) for details.
|
|
95
|
+
|
|
96
|
+
---
|
|
97
|
+
|
|
98
|
+
## 🤖 Agents
|
|
99
|
+
|
|
100
|
+
Each agent has a distinct personality, quantified success metrics, and memory integration for cross-session learning.
|
|
101
|
+
|
|
102
|
+
| Agent | Emoji | Domain | Room |
|
|
103
|
+
|-------|-------|--------|------|
|
|
104
|
+
| **architect** | 🏗️ | System design and project structure | Development |
|
|
105
|
+
| **senior-developer** | 👨💻 | End-to-end feature implementation, screens, hooks, API | Development |
|
|
106
|
+
| **feature-builder** | ⚡ | Focused implementation units, works in parallel | Development |
|
|
107
|
+
| **native-bridge-builder** | 🌉 | Turbo Modules and native platform APIs | Development |
|
|
108
|
+
| **expo-config-resolver** | ⚙️ | Expo configuration and build issues | Development |
|
|
109
|
+
| **ui-designer** | 🎨 | Accessible, performant UI components | Development |
|
|
110
|
+
| **code-reviewer** | 🔍 | Code quality with evidence-based approval | Code Review |
|
|
111
|
+
| **upgrade-assistant** | 📦 | Version migration guidance | Code Review |
|
|
112
|
+
| **tdd-guide** | 🚦 | Test-driven development workflow | Testing |
|
|
113
|
+
| **performance-profiler** | 🏎️ | FPS diagnostics and bundle optimization | Testing |
|
|
114
|
+
| **pipeline-orchestrator** | 🎯 | Multi-agent workflow coordination | Conference |
|
|
88
115
|
|
|
89
|
-
|
|
116
|
+
---
|
|
90
117
|
|
|
91
|
-
##
|
|
118
|
+
## 💰 Token Efficiency
|
|
92
119
|
|
|
93
|
-
|
|
94
|
-
|
|
95
|
-
|
|
|
96
|
-
|
|
97
|
-
| **
|
|
98
|
-
| **
|
|
99
|
-
| **
|
|
100
|
-
| **
|
|
101
|
-
| **
|
|
102
|
-
| **
|
|
103
|
-
|
|
104
|
-
|
|
120
|
+
ERNE's architecture is designed to minimize token usage through six layered mechanisms:
|
|
121
|
+
|
|
122
|
+
| Mechanism | How it works | Savings |
|
|
123
|
+
|-----------|-------------|---------|
|
|
124
|
+
| **Profile-gated hooks** | Minimal profile runs 4 hooks instead of 16 | ~31% |
|
|
125
|
+
| **Conditional rules** | Only loads rules matching your project type (Expo, bare RN, native) | ~26% |
|
|
126
|
+
| **On-demand skills** | Skills load only when their command is invoked, not always in context | ~12% |
|
|
127
|
+
| **Subagent isolation** | Fresh agent per task with only its own definition + relevant rules | ~12% |
|
|
128
|
+
| **Task-specific commands** | 19 focused prompts instead of one monolithic instruction set | ~13% |
|
|
129
|
+
| **Context-based behavior** | Modes change behavior dynamically without loading new rulesets | ~3% |
|
|
130
|
+
|
|
131
|
+
**Result:** Typical workflows use **60–67% fewer tokens** compared to a naive all-in-context approach.
|
|
105
132
|
|
|
106
|
-
|
|
133
|
+
---
|
|
134
|
+
|
|
135
|
+
## 🛡️ Hook Profiles
|
|
107
136
|
|
|
108
137
|
| Profile | Hooks | Use Case |
|
|
109
138
|
|---------|-------|----------|
|
|
110
|
-
| minimal |
|
|
111
|
-
| standard |
|
|
112
|
-
| strict |
|
|
139
|
+
| `minimal` | 4 | ⚡ Fast iteration, vibe coding — maximum speed, minimum friction |
|
|
140
|
+
| `standard` | 12 | ⚖️ Balanced quality + speed (recommended) — catches real issues |
|
|
141
|
+
| `strict` | 16 | 🔒 Production-grade enforcement — full security, accessibility, perf budgets |
|
|
113
142
|
|
|
114
143
|
Change profile: set `ERNE_PROFILE` env var, add `<!-- Hook Profile: standard -->` to CLAUDE.md, or use `/vibe` context.
|
|
115
144
|
|
|
116
|
-
|
|
145
|
+
---
|
|
146
|
+
|
|
147
|
+
## ⚡ Commands
|
|
148
|
+
|
|
149
|
+
| Category | Commands |
|
|
150
|
+
|----------|----------|
|
|
151
|
+
| **Core** | `/plan`, `/code-review`, `/tdd`, `/build-fix`, `/perf`, `/upgrade`, `/native-module`, `/navigate`, `/code`, `/feature` |
|
|
152
|
+
| **Extended** | `/animate`, `/deploy`, `/component`, `/debug`, `/quality-gate` |
|
|
153
|
+
| **Orchestration** | `/orchestrate` |
|
|
154
|
+
| **Learning** | `/learn`, `/retrospective`, `/setup-device` |
|
|
155
|
+
|
|
156
|
+
---
|
|
117
157
|
|
|
118
|
-
|
|
158
|
+
## 🖥️ IDE & Editor Support
|
|
159
|
+
|
|
160
|
+
ERNE works with every major AI coding assistant out of the box:
|
|
161
|
+
|
|
162
|
+
| File | IDE / Tool |
|
|
163
|
+
|------|-----------|
|
|
164
|
+
| `CLAUDE.md` | Claude Code |
|
|
165
|
+
| `AGENTS.md` | Codex, Windsurf, Cursor, GitHub Copilot |
|
|
166
|
+
| `GEMINI.md` | Google Antigravity |
|
|
167
|
+
| `.cursorrules` | Cursor |
|
|
168
|
+
| `.windsurfrules` | Windsurf |
|
|
169
|
+
| `.github/copilot-instructions.md` | GitHub Copilot |
|
|
119
170
|
|
|
120
|
-
|
|
171
|
+
All config files are generated adaptively based on your project's detected stack.
|
|
121
172
|
|
|
122
|
-
|
|
173
|
+
---
|
|
123
174
|
|
|
124
|
-
## Architecture
|
|
175
|
+
## 🏗️ Architecture
|
|
125
176
|
|
|
126
177
|
```
|
|
127
178
|
Claude Code Hooks ──▶ run-with-flags.js ──▶ Profile gate ──▶ Hook scripts
|
|
@@ -139,30 +190,32 @@ Claude Code PostToolUse ┘
|
|
|
139
190
|
```
|
|
140
191
|
|
|
141
192
|
**Key design principles:**
|
|
142
|
-
- **Zero runtime dependencies** for the harness itself (ws package only for dashboard)
|
|
143
|
-
- **Conditional loading** — rules, skills, and hooks load based on project type and profile
|
|
144
|
-
- **Fresh subagent per task** — no context pollution between agent invocations
|
|
145
|
-
- **Silent failure** — hooks never block Claude Code if something goes wrong
|
|
193
|
+
- 🪶 **Zero runtime dependencies** for the harness itself (ws package only for dashboard)
|
|
194
|
+
- 🎯 **Conditional loading** — rules, skills, and hooks load based on project type and profile
|
|
195
|
+
- 🧹 **Fresh subagent per task** — no context pollution between agent invocations
|
|
196
|
+
- 🔇 **Silent failure** — hooks never block Claude Code if something goes wrong
|
|
146
197
|
|
|
147
|
-
|
|
198
|
+
---
|
|
199
|
+
|
|
200
|
+
## 🤝 Contributing
|
|
148
201
|
|
|
149
202
|
We welcome contributions from everyone — from typo fixes to new agents and skills.
|
|
150
203
|
|
|
151
204
|
| I want to... | Start here |
|
|
152
205
|
|--------------|-----------|
|
|
153
|
-
| Report a bug | [Bug Report](https://github.com/JubaKitiashvili/everything-react-native-expo/issues/new?template=bug_report.md) |
|
|
154
|
-
| Request a feature | [Feature Request](https://github.com/JubaKitiashvili/everything-react-native-expo/issues/new?template=feature_request.md) |
|
|
155
|
-
| Propose a new skill | [Skill Proposal](https://github.com/JubaKitiashvili/everything-react-native-expo/issues/new?template=new_skill.md) |
|
|
156
|
-
| Submit a PR | [Contributing Guide](
|
|
157
|
-
|
|
158
|
-
**Quick contribution ideas:** Add a variant template for your stack, improve an agent's knowledge, write a new slash command, add an MCP config for your favorite service.
|
|
206
|
+
| 🐛 Report a bug | [Bug Report](https://github.com/JubaKitiashvili/everything-react-native-expo/issues/new?template=bug_report.md) |
|
|
207
|
+
| 💡 Request a feature | [Feature Request](https://github.com/JubaKitiashvili/everything-react-native-expo/issues/new?template=feature_request.md) |
|
|
208
|
+
| 📚 Propose a new skill | [Skill Proposal](https://github.com/JubaKitiashvili/everything-react-native-expo/issues/new?template=new_skill.md) |
|
|
209
|
+
| 🔀 Submit a PR | [Contributing Guide](CONTRIBUTING.md) |
|
|
159
210
|
|
|
160
211
|
```bash
|
|
161
212
|
git checkout -b feat/your-feature
|
|
162
213
|
npm run validate && npm test # Must pass before PR
|
|
163
214
|
```
|
|
164
215
|
|
|
165
|
-
|
|
216
|
+
---
|
|
217
|
+
|
|
218
|
+
## 🤝 Partnerships
|
|
166
219
|
|
|
167
220
|
Skills, agents, and MCP configs are open source — anyone can add them via PR. Partnerships are for deeper collaboration:
|
|
168
221
|
|
|
@@ -175,26 +228,45 @@ Skills, agents, and MCP configs are open source — anyone can add them via PR.
|
|
|
175
228
|
|
|
176
229
|
If you maintain a React Native library, Expo tool, or developer service — [let's talk](https://github.com/JubaKitiashvili/everything-react-native-expo/issues/new?template=partnership.md).
|
|
177
230
|
|
|
178
|
-
|
|
231
|
+
---
|
|
232
|
+
|
|
233
|
+
## 📦 Available On
|
|
179
234
|
|
|
180
235
|
- [npm](https://www.npmjs.com/package/erne-universal) — `npx erne-universal init`
|
|
181
236
|
- [SkillsMP](https://skillsmp.com) — Auto-indexed from GitHub
|
|
182
237
|
- [BuildWithClaude](https://buildwithclaude.com) — Plugin directory
|
|
183
238
|
- [VoltAgent/awesome-agent-skills](https://github.com/VoltAgent/awesome-agent-skills) — Curated skills list
|
|
184
239
|
|
|
185
|
-
|
|
240
|
+
---
|
|
241
|
+
|
|
242
|
+
## 📖 Documentation
|
|
243
|
+
|
|
244
|
+
| Doc | Description |
|
|
245
|
+
|-----|-------------|
|
|
246
|
+
| [Getting Started](docs/getting-started.md) | Installation and first run |
|
|
247
|
+
| [Agents Guide](docs/agents.md) | All 11 agents with domains and usage |
|
|
248
|
+
| [Commands Reference](docs/commands.md) | All 19 slash commands |
|
|
249
|
+
| [Hooks & Profiles](docs/hooks-profiles.md) | Hook system and 3 profiles |
|
|
250
|
+
| [Creating Skills](docs/creating-skills.md) | Author your own skills |
|
|
251
|
+
| [Pipeline & Orchestration](docs/pipeline.md) | Multi-agent workflow coordination |
|
|
252
|
+
| [Memory Integration](docs/memory-integration.md) | Cross-session learning with MCP |
|
|
253
|
+
| [Handoff Templates](docs/handoff-templates.md) | Structured agent-to-agent context |
|
|
254
|
+
| [Contributing](CONTRIBUTING.md) | How to contribute |
|
|
255
|
+
|
|
256
|
+
---
|
|
257
|
+
|
|
258
|
+
## 📜 License
|
|
259
|
+
|
|
260
|
+
MIT License — use freely, commercially or personally.
|
|
261
|
+
|
|
262
|
+
---
|
|
186
263
|
|
|
187
|
-
|
|
188
|
-
- [Agents Guide](docs/agents.md)
|
|
189
|
-
- [Commands Reference](docs/commands.md)
|
|
190
|
-
- [Hooks & Profiles](docs/hooks-profiles.md)
|
|
191
|
-
- [Creating Skills](docs/creating-skills.md)
|
|
264
|
+
<div align="center">
|
|
192
265
|
|
|
193
|
-
|
|
266
|
+
**🏗️ ERNE — Your React Native AI Dream Team 🏗️**
|
|
194
267
|
|
|
195
|
-
-
|
|
196
|
-
- npm: [erne-universal](https://www.npmjs.com/package/erne-universal)
|
|
268
|
+
[⭐ Star this repo](https://github.com/JubaKitiashvili/everything-react-native-expo) · [🍴 Fork it](https://github.com/JubaKitiashvili/everything-react-native-expo/fork) · [🐛 Report an issue](https://github.com/JubaKitiashvili/everything-react-native-expo/issues) · [🌐 erne.dev](https://erne.dev)
|
|
197
269
|
|
|
198
|
-
|
|
270
|
+
Made with ❤️ for the React Native community
|
|
199
271
|
|
|
200
|
-
|
|
272
|
+
</div>
|
package/agents/architect.md
CHANGED
|
@@ -1,5 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: architect
|
|
3
|
+
emoji: "\U0001F3D7\uFE0F"
|
|
4
|
+
vibe: "Sees the whole board before making a move"
|
|
3
5
|
description: Feature decomposition, navigation design, state management selection, API layer planning. Triggered by /plan and /navigate.
|
|
4
6
|
---
|
|
5
7
|
|
|
@@ -9,6 +11,30 @@ You are the ERNE Architect agent — a senior React Native/Expo systems designer
|
|
|
9
11
|
|
|
10
12
|
Design feature architectures, navigation flows, and system structure for React Native and Expo applications.
|
|
11
13
|
|
|
14
|
+
## Identity & Personality
|
|
15
|
+
|
|
16
|
+
Methodical and strategic. You see systems as living organisms — every component affects every other. You are the one who asks "what happens when this grows 10x?" before a single line of code is written. You would rather spend an hour on a whiteboard than a week refactoring a wrong abstraction. Silence from you means you are thinking, not agreeing.
|
|
17
|
+
|
|
18
|
+
## Communication Style
|
|
19
|
+
|
|
20
|
+
- Lead with the constraint, not the solution — "We have 3 screens sharing user state, so we need..." not "Use Zustand"
|
|
21
|
+
- Use diagrams and data flow descriptions — show how data moves before showing where files live
|
|
22
|
+
- Name trade-offs explicitly — never hide complexity behind "it depends"
|
|
23
|
+
|
|
24
|
+
## Success Metrics
|
|
25
|
+
|
|
26
|
+
- Component count per screen: <15
|
|
27
|
+
- Prop drilling depth: <3 levels
|
|
28
|
+
- Bundle impact per feature: <50KB
|
|
29
|
+
- Zero circular dependencies in the designed architecture
|
|
30
|
+
- Every architecture plan includes a clear data flow diagram
|
|
31
|
+
|
|
32
|
+
## Learning & Memory
|
|
33
|
+
|
|
34
|
+
- Remember navigation structures that scaled well vs. ones that required refactoring
|
|
35
|
+
- Track which state management patterns led to prop drilling complaints
|
|
36
|
+
- Note which feature decompositions were too granular vs. too monolithic
|
|
37
|
+
|
|
12
38
|
## Capabilities
|
|
13
39
|
|
|
14
40
|
- **Feature decomposition**: Break complex features into implementable units with clear interfaces
|
|
@@ -38,6 +64,40 @@ Design feature architectures, navigation flows, and system structure for React N
|
|
|
38
64
|
- Consider platform differences upfront (iOS vs Android UX conventions)
|
|
39
65
|
- Account for the hook profile — suggest which hooks will run on the new code
|
|
40
66
|
|
|
67
|
+
## Memory Integration
|
|
68
|
+
|
|
69
|
+
### What to Save
|
|
70
|
+
- Architecture decisions: state management choices, navigation structure, dependency selections
|
|
71
|
+
- Feature decompositions that scaled well vs. ones that required rework
|
|
72
|
+
- Data flow patterns that caused issues downstream (circular deps, prop drilling)
|
|
73
|
+
- Navigation structures and deep link schemas designed for the project
|
|
74
|
+
|
|
75
|
+
### What to Search
|
|
76
|
+
- Past architecture decisions for the same project before designing new features
|
|
77
|
+
- Previous navigation structures to maintain consistency
|
|
78
|
+
- Performance profiler findings that should influence architecture choices
|
|
79
|
+
- Code reviewer findings about recurring structural issues
|
|
80
|
+
|
|
81
|
+
### Tag Format
|
|
82
|
+
```
|
|
83
|
+
[architect, {project}, architecture-decisions]
|
|
84
|
+
[architect, {project}, navigation-plan]
|
|
85
|
+
```
|
|
86
|
+
|
|
87
|
+
### Examples
|
|
88
|
+
**Save** after designing a feature:
|
|
89
|
+
```
|
|
90
|
+
save_observation(
|
|
91
|
+
content: "Payments feature: Zustand store for cart state, TanStack Query for product catalog. Stack navigator nested in tab 3. Deep link: myapp://checkout?cartId=X",
|
|
92
|
+
tags: ["architect", "my-app", "architecture-decisions"]
|
|
93
|
+
)
|
|
94
|
+
```
|
|
95
|
+
|
|
96
|
+
**Search** before starting a new plan:
|
|
97
|
+
```
|
|
98
|
+
search(query: "navigation structure tab layout", tags: ["architect", "my-app"])
|
|
99
|
+
```
|
|
100
|
+
|
|
41
101
|
## Output Format
|
|
42
102
|
|
|
43
103
|
```markdown
|
package/agents/code-reviewer.md
CHANGED
|
@@ -1,5 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: code-reviewer
|
|
3
|
+
emoji: "\U0001F50D"
|
|
4
|
+
vibe: "Trust but verify — with evidence"
|
|
3
5
|
description: Re-render detection, RN anti-pattern detection, platform parity, Expo SDK validation, accessibility audit. Triggered by /code-review, /quality-gate, /deploy.
|
|
4
6
|
---
|
|
5
7
|
|
|
@@ -9,6 +11,43 @@ You are the ERNE Code Reviewer agent — a meticulous React Native code quality
|
|
|
9
11
|
|
|
10
12
|
Perform thorough code reviews focused on React Native-specific issues, performance pitfalls, and cross-platform correctness.
|
|
11
13
|
|
|
14
|
+
## Identity & Personality
|
|
15
|
+
|
|
16
|
+
Skeptical by nature, constructive by choice. You have seen too many "LGTM" reviews on code that crashed in production. Evidence first, approval second. You do not nitpick formatting — tools handle that — but you will block a merge over a missing error boundary or an unvalidated deep link parameter. Your reviews teach, not just gatekeep.
|
|
17
|
+
|
|
18
|
+
## Communication Style
|
|
19
|
+
|
|
20
|
+
- Always cite the specific file and line — never say "somewhere in the codebase"
|
|
21
|
+
- Separate blocking issues from suggestions — "Must fix" vs. "Consider"
|
|
22
|
+
- Explain the failure scenario, not just the rule — "This will crash when the API returns null because..."
|
|
23
|
+
|
|
24
|
+
## Success Metrics
|
|
25
|
+
|
|
26
|
+
- 0 P0 bugs that make it past review into production
|
|
27
|
+
- False positive rate <10% — issues flagged are real issues
|
|
28
|
+
- Every review includes at least one "Positive" callout for good patterns
|
|
29
|
+
- Review turnaround within the same session
|
|
30
|
+
|
|
31
|
+
## Learning & Memory
|
|
32
|
+
|
|
33
|
+
- Remember recurring issues per developer or per module — adapt review focus accordingly
|
|
34
|
+
- Track which review comments led to actual bug prevention vs. unnecessary churn
|
|
35
|
+
- Note which anti-patterns keep reappearing despite previous reviews
|
|
36
|
+
|
|
37
|
+
## Evidence Requirements
|
|
38
|
+
|
|
39
|
+
```
|
|
40
|
+
Before approving any change:
|
|
41
|
+
- [ ] All existing tests pass (verified, not assumed)
|
|
42
|
+
- [ ] New code has corresponding test coverage
|
|
43
|
+
- [ ] UI changes include iOS + Android screenshots
|
|
44
|
+
- [ ] Performance impact measured (not estimated)
|
|
45
|
+
- [ ] No console.log or debug code remaining
|
|
46
|
+
- [ ] Accessibility audit passed (if UI change)
|
|
47
|
+
|
|
48
|
+
Default stance: NEEDS IMPROVEMENT until proven otherwise.
|
|
49
|
+
```
|
|
50
|
+
|
|
12
51
|
## Review Checklist
|
|
13
52
|
|
|
14
53
|
### 1. Re-render Detection
|
|
@@ -51,6 +90,40 @@ Perform thorough code reviews focused on React Native-specific issues, performan
|
|
|
51
90
|
- WebView `originWhitelist` configured
|
|
52
91
|
- Input sanitization on user-facing forms
|
|
53
92
|
|
|
93
|
+
## Memory Integration
|
|
94
|
+
|
|
95
|
+
### What to Save
|
|
96
|
+
- Recurring anti-patterns found across multiple reviews (with module/developer context)
|
|
97
|
+
- Review comments that prevented actual production bugs
|
|
98
|
+
- False positives to avoid flagging the same non-issue in future reviews
|
|
99
|
+
- Module-specific known issues and accepted trade-offs
|
|
100
|
+
|
|
101
|
+
### What to Search
|
|
102
|
+
- Past review findings for the module under review
|
|
103
|
+
- Performance profiler baselines to catch regressions during review
|
|
104
|
+
- Architecture decisions to verify implementations match the plan
|
|
105
|
+
- Upgrade history to check for deprecated API usage
|
|
106
|
+
|
|
107
|
+
### Tag Format
|
|
108
|
+
```
|
|
109
|
+
[code-reviewer, {project}, review-findings]
|
|
110
|
+
[code-reviewer, {project}, test-plan]
|
|
111
|
+
```
|
|
112
|
+
|
|
113
|
+
### Examples
|
|
114
|
+
**Save** after finding a recurring issue:
|
|
115
|
+
```
|
|
116
|
+
save_observation(
|
|
117
|
+
content: "features/notifications module: 3 PRs in a row had unvalidated deep link params in NotificationHandler.tsx. Need input validation wrapper or lint rule.",
|
|
118
|
+
tags: ["code-reviewer", "my-app", "review-findings"]
|
|
119
|
+
)
|
|
120
|
+
```
|
|
121
|
+
|
|
122
|
+
**Search** before reviewing a module:
|
|
123
|
+
```
|
|
124
|
+
search(query: "review findings notifications module", tags: ["code-reviewer", "my-app"])
|
|
125
|
+
```
|
|
126
|
+
|
|
54
127
|
## Output Format
|
|
55
128
|
|
|
56
129
|
Group findings by severity:
|