erne-universal 0.10.12 → 0.10.14

package/.claude-plugin/plugin.json

@@ -43,27 +43,27 @@
       "visual-debugger"
     ],
     "commands": [
-      "plan",
-      "code-review",
-      "tdd",
-      "build-fix",
-      "perf",
-      "upgrade",
-      "native-module",
-      "navigate",
-      "animate",
-      "deploy",
-      "component",
-      "debug",
-      "debug-visual",
-      "quality-gate",
-      "code",
-      "feature",
-      "learn",
-      "retrospective",
-      "setup-device",
-      "orchestrate",
-      "worker"
+      "erne-plan",
+      "erne-code-review",
+      "erne-tdd",
+      "erne-build-fix",
+      "erne-perf",
+      "erne-upgrade",
+      "erne-native-module",
+      "erne-navigate",
+      "erne-animate",
+      "erne-deploy",
+      "erne-component",
+      "erne-debug",
+      "erne-debug-visual",
+      "erne-quality-gate",
+      "erne-code",
+      "erne-feature",
+      "erne-learn",
+      "erne-retrospective",
+      "erne-setup-device",
+      "erne-orchestrate",
+      "erne-worker"
     ],
     "skills": [
       "coding-standards",

package/CLAUDE.md

@@ -123,7 +123,7 @@ When a user's message matches these signals, automatically use the corresponding
 
 ## Available Commands
 
-Use `/plan`, `/code-review`, `/tdd`, `/build-fix`, `/perf`, `/upgrade`, `/native-module`, `/navigate`, `/animate`, `/deploy`, `/component`, `/debug`, `/debug-visual`, `/audit`, `/quality-gate`, `/code`, `/feature`, `/learn`, `/retrospective`, `/setup-device` for guided workflows.
+Use `/erne-plan`, `/erne-code-review`, `/erne-tdd`, `/erne-build-fix`, `/erne-perf`, `/erne-upgrade`, `/erne-native-module`, `/erne-navigate`, `/erne-animate`, `/erne-deploy`, `/erne-component`, `/erne-debug`, `/erne-debug-visual`, `/erne-audit`, `/erne-quality-gate`, `/erne-code`, `/erne-feature`, `/erne-learn`, `/erne-retrospective`, `/erne-setup-device` for guided workflows.
 
 ## Worker Mode (Autonomous Ticket Execution)
 

package/commands/{animate.md → erne-animate.md}

@@ -1,11 +1,11 @@
 ---
-name: animate
-description: Implement animations using the ui-designer agent with Reanimated and Gesture Handler
+name: erne-animate
+description: ERNE — Implement animations using the ui-designer agent with Reanimated and Gesture Handler
 ---
 
-# /animate — Implement Animations
+# /erne-animate — Implement Animations
 
-You are executing the `/animate` command. Use the **ui-designer** agent to implement animations.
+You are executing the `/erne-animate` command. Use the **ui-designer** agent to implement animations.
 
 ## Process
 

package/commands/{build-fix.md → erne-build-fix.md}

@@ -1,11 +1,11 @@
 ---
-name: build-fix
-description: Diagnose and fix build failures using the expo-config-resolver agent
+name: erne-build-fix
+description: ERNE — Diagnose and fix build failures using the expo-config-resolver agent
 ---
 
-# /build-fix — Fix Build Failures
+# /erne-build-fix — Fix Build Failures
 
-You are executing the `/build-fix` command. Use the **expo-config-resolver** agent to diagnose and fix build errors.
+You are executing the `/erne-build-fix` command. Use the **expo-config-resolver** agent to diagnose and fix build errors.
 
 ## Diagnostic Process
 

package/commands/{code-review.md → erne-code-review.md}

@@ -1,11 +1,11 @@
 ---
-name: code-review
-description: Comprehensive code review combining code quality and performance analysis
+name: erne-code-review
+description: ERNE — Comprehensive code review combining code quality and performance analysis
 ---
 
-# /code-review — Full Code Review
+# /erne-code-review — Full Code Review
 
-You are executing the `/code-review` command. Run **code-reviewer** and **performance-profiler** agents in parallel for comprehensive review.
+You are executing the `/erne-code-review` command. Run **code-reviewer** and **performance-profiler** agents in parallel for comprehensive review.
 
 ## Parallel Execution
 

package/commands/{code.md → erne-code.md}

@@ -1,11 +1,11 @@
 ---
-name: code
-description: Implement features using the senior-developer agent
+name: erne-code
+description: ERNE — Implement features using the senior-developer agent
 ---
 
-# /code — Feature Implementation
+# /erne-code — Feature Implementation
 
-You are executing the `/code` command. Use the **senior-developer** agent to implement production-grade feature code.
+You are executing the `/erne-code` command. Use the **senior-developer** agent to implement production-grade feature code.
 
 ## Process
 
@@ -30,4 +30,4 @@ You are executing the `/code` command. Use the **senior-developer** agent to imp
 
 - 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 `/feature` instead
+- If the task is a single isolated unit (one screen, one hook), consider `/erne-feature` instead

package/commands/{component.md → erne-component.md}

@@ -1,11 +1,11 @@
 ---
-name: component
-description: Design and test UI components using parallel ui-designer and tdd-guide agents
+name: erne-component
+description: ERNE — Design and test UI components using parallel ui-designer and tdd-guide agents
 ---
 
-# /component — Design + Test Component
+# /erne-component — Design + Test Component
 
-You are executing the `/component` command. Run **ui-designer** and **tdd-guide** in parallel. One designs the component, the other writes tests.
+You are executing the `/erne-component` command. Run **ui-designer** and **tdd-guide** in parallel. One designs the component, the other writes tests.
 
 ## Parallel Execution
 

package/commands/{debug-visual.md → erne-debug-visual.md}

@@ -1,11 +1,11 @@
 ---
-name: debug-visual
-description: Screenshot-based visual debugging using the visual-debugger agent
+name: erne-debug-visual
+description: ERNE — Screenshot-based visual debugging using the visual-debugger agent
 ---
 
-# /debug-visual — Visual Debugging
+# /erne-debug-visual — Visual Debugging
 
-You are executing the `/debug-visual` command. Use the **visual-debugger** agent for screenshot-based UI analysis and fixing.
+You are executing the `/erne-debug-visual` command. Use the **visual-debugger** agent for screenshot-based UI analysis and fixing.
 
 ## Arguments
 

package/commands/{debug.md → erne-debug.md}

@@ -1,11 +1,11 @@
 ---
-name: debug
-description: Systematic diagnosis of bugs using the performance-profiler agent
+name: erne-debug
+description: ERNE — Systematic diagnosis of bugs using the performance-profiler agent
 ---
 
-# /debug — Systematic Diagnosis
+# /erne-debug — Systematic Diagnosis
 
-You are executing the `/debug` command. Use the **performance-profiler** agent for systematic bug diagnosis.
+You are executing the `/erne-debug` command. Use the **performance-profiler** agent for systematic bug diagnosis.
 
 ## Process
 

package/commands/{deploy.md → erne-deploy.md}

@@ -1,11 +1,11 @@
 ---
-name: deploy
-description: Validate and submit app builds using parallel expo-config-resolver and code-reviewer agents
+name: erne-deploy
+description: ERNE — Validate and submit app builds using parallel expo-config-resolver and code-reviewer agents
 ---
 
-# /deploy — Validate & Submit
+# /erne-deploy — Validate & Submit
 
-You are executing the `/deploy` command. Run **expo-config-resolver** and **code-reviewer** in parallel. One validates build/deploy config, the other reviews code quality.
+You are executing the `/erne-deploy` command. Run **expo-config-resolver** and **code-reviewer** in parallel. One validates build/deploy config, the other reviews code quality.
 
 ## Parallel Execution
 

package/commands/{feature.md → erne-feature.md}

@@ -1,11 +1,11 @@
 ---
-name: feature
-description: Build a focused feature unit using the feature-builder agent
+name: erne-feature
+description: ERNE — Build a focused feature unit using the feature-builder agent
 ---
 
-# /feature — Focused Feature Unit
+# /erne-feature — Focused Feature Unit
 
-You are executing the `/feature` command. Use the **feature-builder** agent to implement a discrete, scoped feature unit.
+You are executing the `/erne-feature` command. Use the **feature-builder** agent to implement a discrete, scoped feature unit.
 
 ## Process
 
@@ -25,13 +25,13 @@ You are executing the `/feature` command. Use the **feature-builder** agent to i
 
 ## Parallel Work
 
-When used alongside `/code` (senior-developer):
-- `/code` handles: data layer, stores, navigation skeleton, complex multi-screen flows
-- `/feature` handles: individual screens, isolated components, utility hooks, API wrappers
+When used alongside `/erne-code` (senior-developer):
+- `/erne-code` handles: data layer, stores, navigation skeleton, complex multi-screen flows
+- `/erne-feature` handles: individual screens, isolated components, utility hooks, API wrappers
 - Coordinate via shared type definitions and agreed interfaces
 
 ## Notes
 
 - Reference the active platform rules layer for conventions
-- Keep scope tight — if the task touches more than 3 files, use `/code` instead
+- Keep scope tight — if the task touches more than 3 files, use `/erne-code` instead
 - Every delivered unit must include its integration point documentation

package/commands/{learn.md → erne-learn.md}

@@ -1,11 +1,11 @@
 ---
-name: learn
-description: Manual skill generation — runs continuous-learning-v2 scripts to extract patterns from session
+name: erne-learn
+description: ERNE — Manual skill generation — runs continuous-learning-v2 scripts to extract patterns from session
 ---
 
-# /learn — Generate Skills from Session
+# /erne-learn — Generate Skills from Session
 
-You are executing the `/learn` command. This is **script-driven** — it runs the continuous-learning-v2 pipeline directly.
+You are executing the `/erne-learn` command. This is **script-driven** — it runs the continuous-learning-v2 pipeline directly.
 
 ## What This Does
 
@@ -53,4 +53,4 @@ Ensures new rules/skills have valid frontmatter and don't conflict with existing
 - Periodically to capture accumulated project knowledge
 
 ## Note
-The automatic `PostToolUse` hook (`continuous-learning-v2.cjs`) does lightweight extraction after every tool call. This `/learn` command runs a comprehensive analysis that catches patterns the real-time hook might miss.
+The automatic `PostToolUse` hook (`continuous-learning-v2.cjs`) does lightweight extraction after every tool call. This `/erne-learn` command runs a comprehensive analysis that catches patterns the real-time hook might miss.

package/commands/{native-module.md → erne-native-module.md}

@@ -1,11 +1,11 @@
 ---
-name: native-module
-description: Create native modules with sequential native-bridge-builder then code-reviewer agents
+name: erne-native-module
+description: ERNE — Create native modules with sequential native-bridge-builder then code-reviewer agents
 ---
 
-# /native-module — Create Native Module
+# /erne-native-module — Create Native Module
 
-You are executing the `/native-module` command. Run **native-bridge-builder** first (create the module), then **code-reviewer** (review it). This is sequential, not parallel.
+You are executing the `/erne-native-module` command. Run **native-bridge-builder** first (create the module), then **code-reviewer** (review it). This is sequential, not parallel.
 
 ## Phase 1: native-bridge-builder — Scaffold & Implement
 

package/commands/{navigate.md → erne-navigate.md}

@@ -1,11 +1,11 @@
 ---
-name: navigate
-description: Design navigation architecture using the architect agent
+name: erne-navigate
+description: ERNE — Design navigation architecture using the architect agent
 ---
 
-# /navigate — Navigation Design
+# /erne-navigate — Navigation Design
 
-You are executing the `/navigate` command. Use the **architect** agent to design navigation structure.
+You are executing the `/erne-navigate` command. Use the **architect** agent to design navigation structure.
 
 ## Process
 

package/commands/{orchestrate.md → erne-orchestrate.md}

@@ -1,11 +1,11 @@
 ---
-name: orchestrate
-description: Run a full multi-agent pipeline from plan to validation using the pipeline-orchestrator agent
+name: erne-orchestrate
+description: ERNE — Run a full multi-agent pipeline from plan to validation using the pipeline-orchestrator agent
 ---
 
-# /orchestrate — Multi-Agent Pipeline Execution
+# /erne-orchestrate — Multi-Agent Pipeline Execution
 
-You are executing the `/orchestrate` command. Use the **pipeline-orchestrator** agent to coordinate a full pipeline across multiple ERNE agents.
+You are executing the `/erne-orchestrate` command. Use the **pipeline-orchestrator** agent to coordinate a full pipeline across multiple ERNE agents.
 
 ## Usage
 
@@ -112,4 +112,4 @@ The pipeline-orchestrator provides a live progress table and a final summary:
 - The pipeline-orchestrator does not write code — it coordinates agents
 - Handoffs between agents follow the templates in `docs/handoff-templates.md`
 - Full pipeline documentation is in `docs/pipeline.md`
-- If the task is too small for a full pipeline (e.g., a one-file fix), consider using `/code` or `/tdd` instead
+- If the task is too small for a full pipeline (e.g., a one-file fix), consider using `/erne-code` or `/erne-tdd` instead

package/commands/{perf.md → erne-perf.md}

@@ -1,11 +1,11 @@
 ---
-name: perf
-description: Performance profiling and optimization using the performance-profiler agent
+name: erne-perf
+description: ERNE — Performance profiling and optimization using the performance-profiler agent
 ---
 
-# /perf — Performance Profiling
+# /erne-perf — Performance Profiling
 
-You are executing the `/perf` command. Use the **performance-profiler** agent to diagnose and fix performance issues.
+You are executing the `/erne-perf` command. Use the **performance-profiler** agent to diagnose and fix performance issues.
 
 ## Diagnostic Areas
 

package/commands/{plan.md → erne-plan.md}

@@ -1,11 +1,11 @@
 ---
-name: plan
-description: Design feature architecture using the architect agent
+name: erne-plan
+description: ERNE — Design feature architecture using the architect agent
 ---
 
-# /plan — Feature Architecture Design
+# /erne-plan — Feature Architecture Design
 
-You are executing the `/plan` command. Use the **architect** agent to design a feature architecture.
+You are executing the `/erne-plan` command. Use the **architect** agent to design a feature architecture.
 
 ## Process
 

package/commands/{quality-gate.md → erne-quality-gate.md}

@@ -1,11 +1,11 @@
 ---
-name: quality-gate
-description: Pre-merge quality checks using parallel code-reviewer and performance-profiler agents
+name: erne-quality-gate
+description: ERNE — Pre-merge quality checks using parallel code-reviewer and performance-profiler agents
 ---
 
-# /quality-gate — Pre-Merge Checks
+# /erne-quality-gate — Pre-Merge Checks
 
-You are executing the `/quality-gate` command. Run **code-reviewer** and **performance-profiler** in parallel for comprehensive pre-merge validation.
+You are executing the `/erne-quality-gate` command. Run **code-reviewer** and **performance-profiler** in parallel for comprehensive pre-merge validation.
 
 ## Parallel Execution
 

package/commands/{retrospective.md → erne-retrospective.md}

@@ -1,11 +1,11 @@
 ---
-name: retrospective
-description: Session analysis — runs evaluate-session.js to review work quality and suggest improvements
+name: erne-retrospective
+description: ERNE — Session analysis — runs the session evaluator to review work quality and suggest improvements
 ---
 
-# /retrospective — Session Analysis
+# /erne-retrospective — Session Analysis
 
-You are executing the `/retrospective` command. This is **script-driven** — it runs the session evaluation pipeline.
+You are executing the `/erne-retrospective` command. This is **script-driven** — it runs the session evaluation pipeline.
 
 ## What This Does
 

package/commands/{setup-device.md → erne-setup-device.md}

@@ -1,15 +1,15 @@
 ---
-name: setup-device
-description: Install and configure agent-device MCP server for simulator/emulator control
+name: erne-setup-device
+description: ERNE — Install and configure agent-device MCP server for simulator/emulator control
 ---
 
-# /setup-device — Setup Device Control
+# /erne-setup-device — Setup Device Control
 
-You are executing the `/setup-device` command. This is **script-driven** — it sets up the agent-device MCP server.
+You are executing the `/erne-setup-device` command. This is **script-driven** — it sets up the agent-device MCP server.
 
 ## What This Does
 
-Installs and configures the agent-device MCP server so commands like `/debug`, `/perf`, `/component`, and `/deploy` gain visual device interaction capabilities.
+Installs and configures the agent-device MCP server so commands like `/erne-debug`, `/erne-perf`, `/erne-component`, and `/erne-deploy` gain visual device interaction capabilities.
 
 ## Process
 
@@ -62,11 +62,11 @@ After setup, these commands gain enhanced capabilities:
 
 | Command | Enhancement |
 |---------|-------------|
-| `/debug` | Screenshot reproduction steps, tap through UI |
-| `/perf` | Measure real FPS, capture actual jank frames |
-| `/component` | Render on device, visual verification screenshot |
-| `/deploy` | Launch preview build, verify UI before submit |
-| `/build-fix` | Build, install, and launch to verify fix |
+| `/erne-debug` | Screenshot reproduction steps, tap through UI |
+| `/erne-perf` | Measure real FPS, capture actual jank frames |
+| `/erne-component` | Render on device, visual verification screenshot |
+| `/erne-deploy` | Launch preview build, verify UI before submit |
+| `/erne-build-fix` | Build, install, and launch to verify fix |
 
 ### Output
 

package/commands/{tdd.md → erne-tdd.md}

@@ -1,11 +1,11 @@
 ---
-name: tdd
-description: Test-driven development workflow with Jest and React Native Testing Library
+name: erne-tdd
+description: ERNE — Test-driven development workflow with Jest and React Native Testing Library
 ---
 
-# /tdd — Test-Driven Development
+# /erne-tdd — Test-Driven Development
 
-You are executing the `/tdd` command. Use the **tdd-guide** agent to implement features test-first.
+You are executing the `/erne-tdd` command. Use the **tdd-guide** agent to implement features test-first.
 
 ## Red-Green-Refactor Cycle
 

package/commands/{upgrade.md → erne-upgrade.md}

@@ -1,11 +1,11 @@
 ---
-name: upgrade
-description: Version migration for Expo SDK and React Native using the upgrade-assistant agent
+name: erne-upgrade
+description: ERNE — Version migration for Expo SDK and React Native using the upgrade-assistant agent
 ---
 
-# /upgrade — Version Migration
+# /erne-upgrade — Version Migration
 
-You are executing the `/upgrade` command. Use the **upgrade-assistant** agent for guided version migration.
+You are executing the `/erne-upgrade` command. Use the **upgrade-assistant** agent for guided version migration.
 
 ## 5-Step Upgrade Process
 

package/commands/{worker.md → erne-worker.md}

@@ -1,9 +1,9 @@
 ---
-name: worker
-description: Autonomous ticket execution — polls a provider, picks up ready tickets, and runs the full ERNE pipeline (validate, plan, code, test, review, PR).
+name: erne-worker
+description: ERNE — Autonomous ticket execution — polls a provider, picks up ready tickets, and runs the full ERNE pipeline (validate, plan, code, test, review, PR).
 ---
 
-# /worker — Autonomous Ticket Execution
+# /erne-worker — Autonomous Ticket Execution
 
 ## Usage
 

package/lib/claude-md.js

@@ -69,7 +69,7 @@ const STORAGE_LABELS = {
   'async-storage': 'AsyncStorage',
 };
 
-const AVAILABLE_COMMANDS = '/plan, /code-review, /tdd, /build-fix, /perf, /upgrade, /native-module, /debug, /debug-visual, /deploy,\n/component, /navigate, /animate, /orchestrate, /quality-gate, /code, /feature, /worker, /audit, /learn, /retrospective, /setup-device';
+const AVAILABLE_COMMANDS = '/erne-plan, /erne-code-review, /erne-tdd, /erne-build-fix, /erne-perf, /erne-upgrade, /erne-native-module, /erne-debug, /erne-debug-visual, /erne-deploy,\n/erne-component, /erne-navigate, /erne-animate, /erne-orchestrate, /erne-quality-gate, /erne-code, /erne-feature, /erne-worker, /erne-audit, /erne-learn, /erne-retrospective, /erne-setup-device';
 
 /**
  * Read project name from package.json or fallback to directory basename.

package/lib/init.js

@@ -238,6 +238,9 @@ module.exports = async function init() {
     console.log(`    ✓ .claude/rules/ (layers: ${ruleLayers.join(', ')})`);
     console.log(`    ✓ .claude/hooks.json (${profile} profile)`);
     console.log(`    ✓ .claude/mcp/ (${mcpCount} servers)`);
+    if (mcpCount > 0) {
+      console.log('    ⚠ MCP servers configured in .mcp.json — restart Claude Code session to activate');
+    }
     console.log('    ✓ .claude/settings.json');
 
     // Handle CLAUDE.md
@@ -270,48 +273,49 @@ module.exports = async function init() {
       console.log(`    ⚠ Audit skipped: ${err.message}`);
     }
 
-    // ─── Step 6: Launch Dashboard ───
+    // ─── Step 6: Dashboard Info ───
     const skipDashboard = process.env.NODE_TEST || process.env.ERNE_SKIP_DASHBOARD;
-    if (!skipDashboard) console.log('  Step 6: Launching dashboard...\n');
-    try {
-      if (skipDashboard) throw new Error('skipped in test');
-      const { fork } = require('child_process');
-      const fs = require('fs');
-      const dashboardDir = path.resolve(__dirname, '..', 'dashboard');
-      const serverPath = path.resolve(dashboardDir, 'server.js');
-
-      // Install dashboard deps if needed
-      if (!fs.existsSync(path.join(dashboardDir, 'node_modules', 'better-sqlite3'))) {
-        console.log('    Installing dashboard dependencies...');
-        require('child_process').execSync('npm install --production', { cwd: dashboardDir, stdio: 'ignore' });
-      }
-
-      // Fork dashboard server in background
-      const child = fork(serverPath, ['--no-open'], {
-        cwd,
-        detached: true,
-        stdio: 'ignore',
-        env: { ...process.env, ERNE_PROJECT_DIR: cwd },
-      });
-      child.unref();
-
-      // Wait briefly for server to start, then open browser
-      setTimeout(() => {
-        try {
-          const { resolveDashboardPort } = require('../scripts/hooks/lib/port-registry');
-          const port = resolveDashboardPort(cwd) || 3333;
-          const open = process.platform === 'darwin' ? 'open' : process.platform === 'win32' ? 'start' : 'xdg-open';
-          require('child_process').exec(`${open} http://localhost:${port}`);
-          console.log(`    ✓ Dashboard running at http://localhost:${port}`);
-        } catch {
-          console.log('    ✓ Dashboard started in background');
+    if (!skipDashboard) {
+      try {
+        const fs2 = require('fs');
+        const dashboardDir = path.resolve(__dirname, '..', 'dashboard');
+        const depsInstalled = fs2.existsSync(path.join(dashboardDir, 'node_modules', 'better-sqlite3'));
+
+        if (depsInstalled) {
+          const serverPath = path.resolve(dashboardDir, 'server.js');
+          const { fork } = require('child_process');
+          const child = fork(serverPath, [], {
+            cwd,
+            detached: true,
+            stdio: 'ignore',
+            env: { ...process.env, ERNE_PROJECT_DIR: cwd },
+          });
+          child.unref();
+
+          let port = 3333;
+          try {
+            const { resolveDashboardPort } = require('../scripts/hooks/lib/port-registry');
+            port = resolveDashboardPort(cwd) || 3333;
+          } catch { /* fallback 3333 */ }
+
+          console.log(`    ✓ Dashboard: http://localhost:${port}`);
+        } else {
+          console.log('    ℹ Dashboard: run \x1b[36mnpx erne-universal dashboard\x1b[0m to start (first launch installs deps ~2min)');
         }
-      }, 2000);
-    } catch (err) {
-      console.log(`    ⚠ Dashboard skipped: ${err.message}`);
+      } catch {
+        console.log('    ℹ Dashboard: run \x1b[36mnpx erne-universal dashboard\x1b[0m to start');
+      }
     }
 
-    console.log('\n  Done! Run /plan to start your first feature.\n');
+    console.log('');
+    console.log('  \x1b[32mDone!\x1b[0m ERNE is ready.');
+    console.log('');
+    console.log('  Next steps:');
+    console.log('    • Type \x1b[36m/erne-plan\x1b[0m to plan a feature');
+    console.log('    • Type \x1b[36m/erne-perf\x1b[0m to profile performance');
+    console.log('    • Type \x1b[36m/erne-doctor\x1b[0m to check project health');
+    console.log('    • See all commands: type \x1b[36m/erne-\x1b[0m and press Tab');
+    console.log('');
   } finally {
     if (rl) rl.close();
   }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "erne-universal",
-  "version": "0.10.12",
+  "version": "0.10.14",
   "description": "Complete AI coding agent harness for React Native and Expo development",
   "keywords": [
     "react-native",

package/skills/continuous-learning-v2/SKILL.md

@@ -11,17 +11,17 @@ This skill manages the continuous learning pipeline — observing patterns durin
 
 ```
 PostToolUse hook (real-time)
-  → continuous-learning-observer.cjs (lightweight pattern capture)
+  → `continuous-learning-observer.cjs` (lightweight pattern capture)
   → patterns stored in .claude/memory/observations/
 
 /learn command (manual, comprehensive)
-  → extract-session-patterns.js (full session analysis)
-  → analyze-patterns.js (pattern clustering + dedup)
+  → `extract-session-patterns.js` (full session analysis)
+  → `analyze-patterns.js` (pattern clustering + dedup)
   → skill-generator prompt (create new content)
-  → validate-content.js (verify new content is valid)
+  → `validate-content.js` (verify new content is valid)
 
 /retrospective command (session end)
-  → evaluate-session.js (quality metrics + suggestions)
+  → `evaluate-session.js` (quality metrics + suggestions)
 ```
 
 ## How It Works