monomind 2.5.2 → 2.5.4

package/README.md

@@ -365,7 +365,7 @@ Everything runs from inside Claude Code via slash commands. Here's the highlight
 graph TD
     CC["Claude Code"]
     MCP["MCP Server\nmonomind mcp start"]
-    D["Background Workers\n(@monomind/hooks, in-process)"]
+    D["Background Workers\n(@monoes/hooks, in-process)"]
     ORG["OrgDaemon\nmonomind org run\nreal SDK sessions"]
 
     CC <-->|"MCP tools: monograph, memory"| MCP

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "monomind",
-  "version": "2.5.2",
+  "version": "2.5.4",
   "description": "Open-source CLI extension for Claude Code. Adds an MCP server with a codebase knowledge graph, persistent memory, multi-agent coordination, and reusable slash commands. MIT licensed, runs locally, no data leaves your machine.",
   "main": "dist/index.js",
   "type": "module",

package/packages/@monomind/cli/.claude/agents/github/repo-architect.md

@@ -220,7 +220,7 @@ jobs:
     key: "architecture/analysis/results",
     value: {
       timestamp: Date.now(),
-      repositories_analyzed: ["@monomind/cli", "@monomind/hooks"],
+      repositories_analyzed: ["@monomind/cli", "@monoes/hooks"],
       optimization_areas: ["structure", "workflows", "templates", "documentation"],
       recommendations: ["standardize_structure", "improve_workflows", "enhance_templates"],
       implementation_status: "in_progress"
@@ -284,10 +284,10 @@ const integrationPattern = {
   packages: {
     "@monomind/cli": {
       role: "orchestration_layer",
-      dependencies: ["@monomind/hooks", "@monomind/memory"],
+      dependencies: ["@monoes/hooks", "@monomind/memory"],
       provides: ["CLI", "workflows", "commands"],
     },
-    "@monomind/hooks": {
+    "@monoes/hooks": {
       role: "intelligence_engine",
       dependencies: ["@monomind/memory"],
       provides: ["hooks", "workers", "learning"],

package/packages/@monomind/cli/.claude/agents/github/sync-coordinator.md

@@ -182,7 +182,7 @@ Bash(`gh pr create \
     key: "sync/complete/status",
     value: {
       timestamp: Date.now(),
-      packages_synced: ["@monomind/cli", "@monomind/hooks"],
+      packages_synced: ["@monomind/cli", "@monoes/hooks"],
       version_alignment: "completed",
       documentation_sync: "completed",
       github_integration: "completed",
@@ -225,7 +225,7 @@ const docSyncPattern = {
 ### 3. **Integration Testing Matrix**
 ```javascript
 const testMatrix = {
-  packages: ["@monomind/cli", "@monomind/hooks", "@monomind/memory"],
+  packages: ["@monomind/cli", "@monoes/hooks", "@monomind/memory"],
   tests: [
     "unit_tests",
     "integration_tests",

package/packages/@monomind/cli/.claude/agents/specialists/integration-architect.md

@@ -1,7 +1,7 @@
 ---
 name: v1-integration-architect
 description: |
-  v1 Integration Architect for cross-package integration work within the Monomind monorepo. Owns the wiring between @monomind/cli, @monomind/hooks, @monomind/memory, @monomind/security, and @monoes/monograph — ensuring MCP tool contracts, hook event flows, and inter-package APIs stay coherent as each package evolves.
+  v1 Integration Architect for cross-package integration work within the Monomind monorepo. Owns the wiring between @monomind/cli, @monoes/hooks, @monomind/memory, @monomind/security, and @monoes/monograph — ensuring MCP tool contracts, hook event flows, and inter-package APIs stay coherent as each package evolves.
 ---
 
 # Integration Architect
@@ -17,7 +17,7 @@ Keep the 5 Monomind packages working as a coherent system. When a package change
 | Package | Role | Integration Surface |
 |---------|------|-------------------|
 | `@monomind/cli` | Orchestration layer | MCP server, CLI commands, init generator |
-| `@monomind/hooks` | Intelligence engine | Hook events, background workers, pattern learning |
+| `@monoes/hooks` | Intelligence engine | Hook events, background workers, pattern learning |
 | `@monomind/memory` | Persistence layer | LanceDB, HNSW search, session state |
 | `@monomind/security` | Input validation | CVE remediation, safe executor, path validator |
 | `@monoes/monograph` | Knowledge graph | Dependency analysis, community detection, impact |
@@ -40,7 +40,7 @@ type HookEvent = {
 All MCP tools exposed via `@monomind/cli/src/mcp-tools/` must:
 1. Validate inputs through `@monomind/security` before execution
 2. Persist results to `@monomind/memory` when stateful
-3. Emit hook events via `@monomind/hooks` for learning
+3. Emit hook events via `@monoes/hooks` for learning
 
 ### Memory Access Pattern
 
@@ -58,7 +58,7 @@ const result = await db.search({ query, namespace: 'package-name' });
 When a new feature spans multiple packages:
 
 - [ ] API contract defined and typed in the consuming package
-- [ ] Hook events documented in `@monomind/hooks/src/types.ts`
+- [ ] Hook events documented in `@monoes/hooks/src/types.ts`
 - [ ] MCP tool registered in `@monomind/cli/src/mcp-tools/index.ts`
 - [ ] Security validation added at system boundary
 - [ ] Memory schema migration written if LanceDB schema changes

package/packages/@monomind/cli/.claude/commands/github/repo-architect.md

@@ -143,7 +143,7 @@ See CLAUDE.md for complete integration instructions.`
 
 ```javascript
 // Synchronize structure across related repositories
-const repositories = ["@monomind/cli", "@monomind/hooks", "@monomind/memory"];
+const repositories = ["@monomind/cli", "@monoes/hooks", "@monomind/memory"];
 
 // Update common files across repositories
 repositories.forEach((repo) => {
@@ -248,7 +248,7 @@ monomind/
 │   │   ├── src/
 │   │   ├── .claude/
 │   │   └── package.json
-│   ├── @monomind/hooks/
+│   ├── @monoes/hooks/
 │   │   ├── src/
 │   │   └── package.json
 │   └── shared/
@@ -296,10 +296,10 @@ const integrationPattern = {
   packages: {
     "@monomind/cli": {
       role: "orchestration_layer",
-      dependencies: ["@monomind/hooks", "@monomind/memory"],
+      dependencies: ["@monoes/hooks", "@monomind/memory"],
       provides: ["CLI", "workflows", "commands"],
     },
-    "@monomind/hooks": {
+    "@monoes/hooks": {
       role: "coordination_engine",
       dependencies: [],
       provides: ["MCP_tools", "neural_networks", "memory"],

package/packages/@monomind/cli/.claude/commands/github/sync-coordinator.md

@@ -225,7 +225,7 @@ const docSyncPattern = {
   ],
   customSections: {
     "@monomind/cli": "GitHub Commands Integration",
-    "@monomind/hooks": "MCP Tools Reference"
+    "@monoes/hooks": "MCP Tools Reference"
   }
 }
 ```
@@ -234,7 +234,7 @@ const docSyncPattern = {
 ```javascript
 // Comprehensive testing across synchronized packages
 const testMatrix = {
-  packages: ["@monomind/cli", "@monomind/hooks"],
+  packages: ["@monomind/cli", "@monoes/hooks"],
   tests: [
     "unit_tests",
     "integration_tests", 

package/packages/@monomind/cli/.claude/helpers/event-logger.cjs

@@ -194,7 +194,7 @@ async function main() {
 
   // Detect route changes and worker metric updates by mtime and forward them too.
   // These aren't Claude Code hook events — they're file writes from route-handler.cjs
-  // and the @monomind/hooks workers respectively — so we poll cheaply on every hook invocation.
+  // and the @monoes/hooks workers respectively — so we poll cheaply on every hook invocation.
   forwardFileChanges(monoDir, CWD);
 
   clearTimeout(safety);
@@ -221,7 +221,7 @@ function forwardFileChanges(monoDir, workDir) {
       }
     } catch {}
 
-    // Worker-complete: newest mtime among .monomind/metrics/*.json (written by @monomind/hooks workers)
+    // Worker-complete: newest mtime among .monomind/metrics/*.json (written by @monoes/hooks workers)
     const metricsDir = path.join(workDir, '.monomind', 'metrics');
     try {
       const files = fs.readdirSync(metricsDir).filter(f => f.endsWith('.json') && !f.startsWith('.'));

package/packages/@monomind/cli/.claude/helpers/extras-registry.json

@@ -3686,7 +3686,7 @@
     {
       "slug": "v1-integration-architect",
       "name": "v1-integration-architect",
-      "description": "v1 Integration Architect for cross-package integration work within the Monomind monorepo. Owns the wiring between @monomind/cli, @monomind/hooks, @monomind/memory, @monomind/security, and @monoes/monograph \u2014 ensuring MCP tool contracts, hook event flows, and inter-package APIs stay coherent as each package evolves.",
+      "description": "v1 Integration Architect for cross-package integration work within the Monomind monorepo. Owns the wiring between @monomind/cli, @monoes/hooks, @monomind/memory, @monomind/security, and @monoes/monograph \u2014 ensuring MCP tool contracts, hook event flows, and inter-package APIs stay coherent as each package evolves.",
       "category": "specialists",
       "filePath": "../agents/specialists/integration-architect.md",
       "keywords": [

package/packages/@monomind/cli/.claude/helpers/handlers/agent-start-handler.cjs

@@ -106,7 +106,7 @@ module.exports = {
       }
     } catch (e) { /* non-fatal */ }
 
-    // Bridge to @monomind/hooks registry — fires AgentSpawn hooks (was previously never
+    // Bridge to @monoes/hooks registry — fires AgentSpawn hooks (was previously never
     // wired: HookEvent.AgentSpawn existed but no CJS handler ever fired it).
     try {
       var _hooksModule = hCtx._ensureHooksModule ? await hCtx._ensureHooksModule() : null;
@@ -125,7 +125,7 @@ module.exports = {
               description: agentDescBridge.slice(0, 500),
             },
           }, { continueOnError: true, timeout: 1500 });
-        }, '@monomind/hooks.AgentSpawn');
+        }, '@monoes/hooks.AgentSpawn');
       }
     } catch (e) { /* non-fatal */ }
   },

package/packages/@monomind/cli/.claude/helpers/handlers/edit-handler.cjs

@@ -152,7 +152,7 @@ module.exports = {
       }
     } catch (e) { /* non-fatal */ }
 
-    // Bridge to @monomind/hooks registry — fires PostEdit hooks (observability bus, guidance provider).
+    // Bridge to @monoes/hooks registry — fires PostEdit hooks (observability bus, guidance provider).
     // Each hook event runs in a fresh process, so hCtx._hooksModule set by session-restore in an
     // earlier invocation is never visible here — must (re)load lazily via _ensureHooksModule().
     var _hooksModule = hCtx._hooksModule || (hCtx._ensureHooksModule ? await hCtx._ensureHooksModule() : null);
@@ -169,7 +169,7 @@ module.exports = {
             file: { path: editFileBridge, operation: 'modify' },
             duration: 0,
           }, { continueOnError: true, timeout: 1500 });
-        }, '@monomind/hooks.PostEdit');
+        }, '@monoes/hooks.PostEdit');
       } catch (e) { /* non-fatal */ }
     }
 

package/packages/@monomind/cli/.claude/helpers/handlers/gates-handler.cjs

@@ -23,7 +23,7 @@ const path = require('path');
 //
 // monofence-ai (packages/monofence-ai) has real prompt-injection / evasion
 // detection but is never wired into the live Claude Code PreToolUse path —
-// it only registers hooks on @monomind/hooks' internal HookRegistry, which
+// it only registers hooks on @monoes/hooks' internal HookRegistry, which
 // this CJS dispatch path does not use. This loads it lazily (so a missing
 // or unbuilt package never breaks the existing regex gates), bounds it with
 // a hard timeout, and fails open on any error.
@@ -107,8 +107,13 @@ function _withTimeout(promise, ms) {
 /**
  * Scan `input` with monofence-ai's threat detector, bounded by a timeout.
  * Returns null (never throws) when monofence is unavailable, times out, or errors.
+ * MONOMIND_MONOFENCE_GATE=off disables this scan entirely (mirrors
+ * MONOMIND_GRAPH_GATE=off) — e.g. when its heuristics misfire on ordinary
+ * markdown headings (observed a false-positive high-confidence block on
+ * plain release-note prose during v2.5.3).
  */
 async function monofenceScan(input) {
+  if (String(process.env.MONOMIND_MONOFENCE_GATE || '').toLowerCase() === 'off') return null;
   if (!input || typeof input !== 'string') return null;
   var mod = await _withTimeout(_loadMonofence(), MONOFENCE_TIMEOUT_MS);
   if (!mod || typeof mod.getMonoDefence !== 'function') return null;

package/packages/@monomind/cli/.claude/helpers/handlers/route-handler.cjs

@@ -111,7 +111,7 @@ module.exports = {
       var result = await Promise.resolve(routeFn(prompt));
 
       // ── Enrichment: when router.cjs falls to the broad "coder" catch-all,
-      //    try @monomind/routing's richer keyword pre-filter (30+ specialized
+      //    try @monoes/routing's richer keyword pre-filter (30+ specialized
       //    rules for Solidity, game engines, DevOps, embedded, etc.) for a
       //    more specific agent match. This bridges the hooks layer (router.cjs)
       //    with the CLI routing package without requiring ESM imports. ─────────

package/packages/@monomind/cli/.claude/helpers/handlers/session-handler.cjs

@@ -166,7 +166,7 @@ module.exports = {
       }
     } catch (e) { console.log('[WARN] Session end failed: ' + e.message); }
 
-    // Bridge to @monomind/hooks registry — fires SessionEnd hooks (episode-binner closeEpisode, observability bus).
+    // Bridge to @monoes/hooks registry — fires SessionEnd hooks (episode-binner closeEpisode, observability bus).
     // Each hook event runs in a fresh process, so hCtx._hooksModule set by session-restore in an
     // earlier invocation is never visible here — must (re)load lazily via _ensureHooksModule().
     var _hooksModule = hCtx._hooksModule || (hCtx._ensureHooksModule ? await hCtx._ensureHooksModule() : null);

package/packages/@monomind/cli/.claude/helpers/handlers/session-restore-handler.cjs

@@ -30,20 +30,20 @@ module.exports = {
       }
     } catch (e) { console.log('[WARN] Session restore failed: ' + e.message); }
 
-    // ── Non-blocking security scan via @monomind/hooks worker ─────────────
+    // ── Non-blocking security scan via @monoes/hooks worker ─────────────
     // The hooks package ships a security worker (worker-security.ts) that scans
     // for hardcoded secrets and vulnerability patterns. We run it at session
     // start as a fire-and-forget check — failures are silently ignored since
     // the package may not be installed or built.
     try {
-      var hooksWorkersMod = require('@monomind/hooks/dist/workers/worker-security.js');
+      var hooksWorkersMod = require('@monoes/hooks/dist/workers/worker-security.js');
       var _createSecurityWorker = hooksWorkersMod.createSecurityWorker;
       if (typeof _createSecurityWorker === 'function') {
         var _securityScan = _createSecurityWorker(CWD);
         // Fire-and-forget: do not await — must not delay session restore
         Promise.resolve(_securityScan()).catch(function() {});
       }
-    } catch (e) { /* @monomind/hooks not available or not built — skip */ }
+    } catch (e) { /* @monoes/hooks not available or not built — skip */ }
 
     // Stale helper self-heal — silently refresh project helpers that drift from
     // the bundled npm copy, so a `npm i -g monomind@latest` (or npx picking up a
@@ -226,16 +226,16 @@ module.exports = {
       }
     }
 
-    // Bridge to @monomind/hooks compiled workers (GAP-001).
+    // Bridge to @monoes/hooks compiled workers (GAP-001).
     // Uses the shared hCtx._ensureHooksModule() (defined in hook-handler.cjs) so worker
     // registration happens exactly once per process instead of being duplicated here —
     // every other bridging handler (agent-start, pre-task, post-task, post-edit,
     // session-end) calls the same lazy loader since each hook event is its own process.
     try {
-      var hooksModule = hCtx._ensureHooksModule ? await hCtx._ensureHooksModule() : await import('@monomind/hooks');
+      var hooksModule = hCtx._ensureHooksModule ? await hCtx._ensureHooksModule() : await import('@monoes/hooks');
       if (hooksModule) {
         hCtx._hooksModule = hooksModule;
-        console.log('[INFO] @monomind/hooks workers initialized');
+        console.log('[INFO] @monoes/hooks workers initialized');
 
         // Gate enforcement lives entirely in gates-handler.cjs (its own regex
         // table, run on every PreToolUse). The @monomind/guidance package that
@@ -251,16 +251,16 @@ module.exports = {
                   startedAt: new Date(),
                 },
               }, { continueOnError: true, timeout: 1500 });
-            }, '@monomind/hooks.SessionStart');
+            }, '@monoes/hooks.SessionStart');
           } catch (e2) { /* non-fatal */ }
         }
       }
-    } catch (e) { /* @monomind/hooks not compiled yet — skip */ }
+    } catch (e) { /* @monoes/hooks not compiled yet — skip */ }
 
     // Refresh worker metrics once per session start — the statusline
     // (.claude/helpers/statusline.cjs) reads .monomind/metrics/ddd-progress.json,
     // route-handler.cjs and doctor read codebase-map/security-audit/performance/
-    // consolidation.json; the @monomind/hooks workers are never otherwise
+    // consolidation.json; the @monoes/hooks workers are never otherwise
     // scheduled on the live hook path (the worker daemon that used to produce
     // these files was deleted).
     //
@@ -295,7 +295,7 @@ module.exports = {
           var _create = (hooksModule && typeof hooksModule[_w.factory] === 'function')
             ? hooksModule[_w.factory] : null;
           if (!_create) {
-            // Dev-repo fallback: bare '@monomind/hooks' does not resolve from .claude/helpers
+            // Dev-repo fallback: bare '@monoes/hooks' does not resolve from .claude/helpers
             // in the monorepo (pnpm workspace link lives under packages/@monomind/cli), so
             // import the compiled worker directly by path.
             var _wDist = path.join(_hooksDistDir, _w.file);
@@ -307,7 +307,7 @@ module.exports = {
           if (_create) {
             var _wRun = _create(CWD);
             // runWithTimeout caps each at 1.5s so a slow worker can never block session start.
-            await runWithTimeout(function() { return _wRun(); }, '@monomind/hooks.' + _w.factory);
+            await runWithTimeout(function() { return _wRun(); }, '@monoes/hooks.' + _w.factory);
           }
         } catch (e) { /* non-fatal — worker unavailable */ }
       }

package/packages/@monomind/cli/.claude/helpers/handlers/task-handler.cjs

@@ -26,7 +26,7 @@ module.exports = {
     // - PromptVersioning experiments (unused feature)
     // - Monograph blast radius (already shown by post-edit hook on actual changes)
 
-    // Bridge to @monomind/hooks registry — fires Tasks 26 (PromptAssembler) and any other PreTask hooks.
+    // Bridge to @monoes/hooks registry — fires Tasks 26 (PromptAssembler) and any other PreTask hooks.
     // Each hook event runs in a fresh process, so hCtx._hooksModule set by session-restore in an
     // earlier invocation is never visible here — must (re)load lazily via _ensureHooksModule().
     var _hooksModule = hCtx._hooksModule || (hCtx._ensureHooksModule ? await hCtx._ensureHooksModule() : null);
@@ -114,7 +114,7 @@ module.exports = {
       }
     } catch (e) { /* non-fatal */ }
 
-    // Bridge to @monomind/hooks registry — fires Tasks 39 (SpecializationScorer) and any other PostTask hooks.
+    // Bridge to @monoes/hooks registry — fires Tasks 39 (SpecializationScorer) and any other PostTask hooks.
     // Each hook event runs in a fresh process, so hCtx._hooksModule set by session-restore in an
     // earlier invocation is never visible here — must (re)load lazily via _ensureHooksModule().
     var _hooksModule = hCtx._hooksModule || (hCtx._ensureHooksModule ? await hCtx._ensureHooksModule() : null);

package/packages/@monomind/cli/.claude/helpers/hook-handler.cjs

@@ -12,7 +12,7 @@
  *    configuration. They are plain CommonJS scripts invoked directly
  *    by Claude Code's hook runtime. This is the "live" system.
  *
- * 2. @monomind/hooks TypeScript package (packages/@monomind/hooks/)
+ * 2. @monoes/hooks TypeScript package (packages/@monomind/hooks/)
  *    A full TypeScript package with workers, learning services, and
  *    a WorkerManager. It compiles to dist/ but is only loaded
  *    optionally, bridged at six lifecycle events: SessionStart (restore),
@@ -23,7 +23,7 @@
  *
  *    IMPORTANT: each hook event is dispatched as its OWN fresh `node`
  *    process (Claude Code spawns one invocation per event — this file
- *    does not stay resident across events). So the @monomind/hooks
+ *    does not stay resident across events). So the @monoes/hooks
  *    module, and anything it registers (trace collector spans, episode
  *    binner, etc.), cannot be set up once and reused across events —
  *    every bridging handler must call hCtx._ensureHooksModule() itself,
@@ -102,7 +102,7 @@ const session = safeRequire(path.join(helpersDir, 'session.cjs'));
 const memory = safeRequire(path.join(helpersDir, 'memory.cjs'));
 const intelligence = safeRequire(path.join(helpersDir, 'intelligence.cjs'));
 
-// Module-level reference to @monomind/hooks — populated lazily via
+// Module-level reference to @monoes/hooks — populated lazily via
 // _ensureHooksModule(). NOTE: hook-handler.cjs runs as a fresh `node` process
 // per hook event (Claude Code spawns one invocation per event, it does not
 // keep the process alive across events), so a value set during one event
@@ -116,10 +116,10 @@ async function _ensureHooksModule() {
   if (_hooksModule) return _hooksModule;
   if (_hooksModuleLoadAttempted) return null; // already tried+failed this process
   _hooksModuleLoadAttempted = true;
-  // 1) Bare specifier — works when @monomind/hooks is installed/linked in a
+  // 1) Bare specifier — works when @monoes/hooks is installed/linked in a
   //    node_modules reachable from this file (e.g. an end-user install).
   try {
-    _hooksModule = await import('@monomind/hooks');
+    _hooksModule = await import('@monoes/hooks');
   } catch (e) {
     _hooksModule = null;
   }
@@ -141,11 +141,11 @@ async function _ensureHooksModule() {
   return _hooksModule;
 }
 
-// ── Visible one-time warning when the @monomind/hooks bridge fully fails ───
+// ── Visible one-time warning when the @monoes/hooks bridge fully fails ───
 // Both load paths above (bare specifier + dev-repo file:// fallback) failed:
 // the 15 background workers (metrics, security scan, DDD tracking, etc.) are
 // unavailable for the rest of this session. This is almost always because
-// @monomind/hooks was never resolvable from npm (it ships with
+// @monoes/hooks was never resolvable from npm (it ships with
 // optionalDependencies:"*", which npm silently skips) — NOT a problem with
 // the user's own project setup. Historically this failed completely
 // silently (see docs/AUDIT-BACKLOG.md P1-1), burning debugging time on the
@@ -166,7 +166,7 @@ function _warnHooksBridgeUnavailable() {
     }
     if (alreadyWarned) return;
     process.stderr.write(
-      '[WARN] @monomind/hooks could not be loaded (bare specifier and dev-repo fallback both failed) — ' +
+      '[WARN] @monoes/hooks could not be loaded (bare specifier and dev-repo fallback both failed) — ' +
       'background workers (metrics, security scan, DDD tracking, etc.) are unavailable this session. ' +
       'This is not a problem with your project configuration — the package is not resolvable via npm ' +
       'from this install. See docs/AUDIT-BACKLOG.md P1-1 or https://github.com/monoes/monomind/issues.\n'

package/packages/@monomind/cli/.claude/skills/mastermind-techport/SKILL.md

@@ -590,7 +590,7 @@ For each approved item, in recommended order.
 | Exported functions | camelCase, no prefix | `buildGraph()`, `resolveAgent()` |
 | Config keys | camelCase | `projectRoot`, `maxAgents` |
 | Env vars | `MONOMIND_*` uppercase | `MONOMIND_PORT`, `MONOMIND_LOG_LEVEL` |
-| npm packages | `@monomind/<name>` | `@monomind/hooks` |
+| npm packages | `@monomind/<name>` | `@monoes/hooks` |
 | CLI commands | `monomind <command>` | `monomind agent spawn` |
 | Error classes | extend monomind hierarchy | `class PortedError extends CLIError {}` |
 | Event names | `domain:action` kebab | `'hook:fired'`, `'agent:spawned'` |

package/packages/@monomind/cli/.claude/skills/monodesign/SKILL.md

@@ -56,7 +56,7 @@ allowed-tools:
   - Bash
   - WebSearch
   - WebFetch
-license: "Apache 2.0 — Pattern adapted from impeccable (Apache-2.0) and Anthropic's frontend-design skill; see NOTICE.md"
+license: Apache-2.0
 ---
 
 Designs and iterates production-grade frontend interfaces. Real working code, committed design choices, exceptional craft.
@@ -151,7 +151,7 @@ If someone could look at this interface and say "AI made that" without doubt, it
 
 ## Antipattern detection
 
-Before finalizing any design, run the bundled detector. It checks 46 known design antipatterns across two categories (**slop** — AI tells; **quality** — design principle violations):
+Before finalizing any design, run the bundled detector. It checks 51 known design antipatterns across two categories (**slop** — AI tells; **quality** — design principle violations):
 
 ```bash
 monomind design detect <file-or-dir>          # human-readable report

package/packages/@monomind/cli/.claude/skills/monodesign/reference/antipatterns-catalog.md

@@ -1,14 +1,14 @@
 <!-- Synced from the monodesign v3.2.1 registry. Source of truth: cli/engine/registry/antipatterns.mjs -->
 # Antipatterns Catalog
 
-All 46 known design antipatterns with detection rules and remediation. These are what `monomind design detect` checks. Run this on any HTML/CSS target before presenting work.
+All 51 known design antipatterns with detection rules and remediation. These are what `monomind design detect` checks. Run this on any HTML/CSS target before presenting work.
 
 ## Categories
 
 These are the two categories the `monomind design detect` engine uses:
 
 - **slop** — AI tells that signal lack of intentional design (27 patterns)
-- **quality** — Design principle violations including contrast, motion, readability, and semantic structure (19 patterns)
+- **quality** — Design principle violations including contrast, motion, readability, and semantic structure (24 patterns)
 
 ---
 
@@ -226,6 +226,14 @@ These are the two categories the `monomind design detect` engine uses:
 **Why it's wrong:** Cramped elements are hard to read, harder to click, and communicate low quality. 8px is the absolute minimum; 16px is the default.  
 **Fix:** Minimum 12px padding inside cards. Minimum 10px vertical + 16px horizontal on buttons. Minimum 44×44px touch targets.
 
+### `dark-scheme-contrast-blindspot` — Dark-scheme contrast blindspot
+
+**Detect** (advisory): The page ships dark styling (a `@media (prefers-color-scheme: dark)` block or a `.dark` / `[data-theme=dark]` scope), but for some selector the dark override changes the background without changing the paired text color — or the reverse — while the light scheme defined both.
+
+**Why it's wrong**: A half-updated color pair often collapses to unreadable contrast in dark mode (dark text left on a newly-dark background). It's the most common dark-mode regression and easy to miss because the light scheme looks fine.
+
+**Fix**: Override text and background together for the same selector, or verify the inherited half still contrasts against the changed half. Prefer semantic tokens (`--fg` / `--bg`) that flip as a pair.
+
 ### `design-system-color` — Color outside DESIGN.md
 
 **Detect**: A literal color value used in CSS that is not declared in the project's `DESIGN.md` palette or its tonal ramps.
@@ -263,6 +271,22 @@ These are the two categories the `monomind design detect` engine uses:
 **Why it's wrong:** Gray text on colored backgrounds almost always fails WCAG contrast requirements and looks muddy.  
 **Fix:** Use white or the appropriate neutral from the color ramp. Never use a generic gray on a tinted background.
 
+### `hover-only-affordance` — Functionality gated behind hover only
+
+**Detect**: An element is hidden by default (`display: none`, `visibility: hidden`, or `opacity: 0`) and revealed only via a `:hover` rule on an ancestor, with no matching `:focus`, `:focus-within`, or `:active` rule.
+
+**Why it's wrong**: Hover doesn't exist on touch devices and can't be reached by keyboard. Anything gated behind hover alone is invisible and unusable for a large share of users.
+
+**Fix**: Mirror every hover reveal with a `:focus-within` (or `:active`) rule targeting the same element, so the affordance is reachable without a pointer.
+
+### `image-missing-dimensions` — Image without reserved dimensions
+
+**Detect**: An `<img>` ships without both `width` and `height` attributes and without a CSS `aspect-ratio` or explicit height.
+
+**Why it's wrong**: The browser can't reserve space before the image loads, so surrounding content jumps when it arrives — cumulative layout shift (CLS), a Core Web Vitals failure and a jarring experience.
+
+**Fix**: Set `width` and `height` attributes (the browser derives the aspect ratio), or give the image a CSS `aspect-ratio`. Either reserves the box before load.
+
 ### `justified-text` — Justified text
 **Detect:** `text-align: justify` on paragraph elements.  
 **Why it's wrong:** CSS text justification creates uneven word spacing (rivers of white) because browsers don't hyphenate automatically. It reads as broken on web.  
@@ -283,11 +307,27 @@ These are the two categories the `monomind design detect` engine uses:
 **Why it's wrong:** Low contrast text fails WCAG AA requirements and creates genuine barriers for users with low vision, in bright ambient light, or on low-quality displays.  
 **Fix:** Increase the contrast between text and background. Use white or a high-lightness neutral on dark backgrounds; use Deep Graphite (`oklch(10% 0 0)`) or Soft Charcoal (`oklch(25% 0 0)`) on light ones. Tool: check with `monomind design detect` or the WebAIM contrast checker.
 
+### `missing-focus-visible` — Suppressed focus outline with no replacement
+
+**Detect**: An interactive element (link, button, input, `[role=button]`) removes its focus outline (`outline: none` / `0`), but the stylesheet never provides a `:focus-visible` or `:focus` replacement.
+
+**Why it's wrong**: Removing the outline with no substitute strands keyboard users — there's no visible indication of where focus is. It's one of the most common and most damaging accessibility regressions.
+
+**Fix**: Remove the suppression, or pair it with a visible `:focus-visible` ring — an `outline`, `box-shadow`, or `border` that clearly marks the focused control.
+
 ### `skipped-heading` — Skipped heading level
 **Detect:** An `h3` or deeper element that is not preceded by an `h2` in the same section, or an `h2` not preceded by an `h1`.  
 **Why it's wrong:** Skipped headings break screen reader navigation and document outline semantics.  
 **Fix:** Maintain sequential heading hierarchy. If you need the visual size of `h3` without the `h2` parent, use a `h2` with class-based styling.
 
+### `small-touch-target` — Touch target below 44px
+
+**Detect**: A clickable control (`button`, link, clickable `input`, `[role=button]`) renders smaller than 44×44px on one or both axes. Inline text links inside prose are exempt.
+
+**Why it's wrong**: Fingers are imprecise. Targets below ~44×44px (the WCAG 2.5.5 / platform HIG minimum) are missed and mis-tapped, especially on mobile and for users with motor impairments.
+
+**Fix**: Give standalone controls at least 44×44px of hit area via `padding` or `min-width` / `min-height`. Spacing between adjacent targets helps too.
+
 ### `text-overflow` — Content overflowing its container
 
 **Detect**: Content renders wider than its container — `scrollWidth > clientWidth` on any non-scroll element, or a horizontal scrollbar appears on the page.
@@ -349,16 +389,21 @@ These are the two categories the `monomind design detect` engine uses:
 | `broken-image` | quality | Real image or remove tag |
 | `clipped-overflow-container` | quality | Portal or visible overflow |
 | `cramped-padding` | quality | 16px minimum |
+| `dark-scheme-contrast-blindspot` | quality | Flip text + background as a pair |
 | `design-system-color` | quality | Use palette token or update DESIGN.md |
 | `design-system-font` | quality | Use type system or update DESIGN.md |
 | `design-system-font-size` | quality | Use type-ramp step or update DESIGN.md |
 | `design-system-radius` | quality | Use radius token or update DESIGN.md |
 | `gray-on-color` | quality | White or appropriate ramp tone |
+| `hover-only-affordance` | quality | Mirror hover with :focus-within |
+| `image-missing-dimensions` | quality | width/height attrs or aspect-ratio |
 | `justified-text` | quality | text-align: left |
 | `layout-transition` | quality | transform + opacity only |
 | `line-length` | quality | max-width: 65ch |
 | `low-contrast` | quality | 4.5:1 normal, 3:1 large text |
+| `missing-focus-visible` | quality | Add a :focus-visible ring |
 | `skipped-heading` | quality | Sequential h1→h2→h3 |
+| `small-touch-target` | quality | 44×44px minimum hit area |
 | `text-overflow` | quality | overflow-wrap + constrained widths |
 | `tight-leading` | quality | line-height: 1.6 |
 | `tiny-text` | quality | 16px minimum body |

package/packages/@monomind/cli/.claude/skills/monodesign/reference/critique.md

@@ -181,7 +181,7 @@ Skip this step if the Setup slug was null (vague or root-level target).
    MONODESIGN_CRITIQUE_META='{"target":"<user phrasing>","total_score":<n>,"p0_count":<n>,"p1_count":<n>}' \
      node .claude/skills/monodesign/scripts/critique-storage.mjs write <slug> <body-file>
    ```
-   The helper prints the absolute path it wrote.
+   The helper prints the absolute path it wrote. As part of the write it also best-effort mirrors a compact record (score, P0/P1 counts, date, slug, path) into monomind's persistent memory under the `design-critique` namespace, so design health carries across sessions. This mirror is silent and never fails the critique: if the monomind CLI is unavailable it is skipped, and setting `MONODESIGN_NO_MEMORY=1` disables it entirely. Do not report mirror status unless the user asks.
 
 3. **Delete the temp body file** after the write attempt completes, whether the write succeeded or failed. If deletion fails, mention `temp-file cleanup failed: <reason>` briefly in the final output, but do not block the critique.
 

package/packages/@monomind/cli/.claude/skills/monodesign/reference/live.md

@@ -681,10 +681,6 @@ const __monodesignLiveDev =
 - **SvelteKit**: edit `svelte.config.js`, appending to `kit.csp.directives['script-src']` and `kit.csp.directives['connect-src']`.
 - **Nuxt + nuxt-security**: edit `nuxt.config.*`, appending to `security.headers.contentSecurityPolicy['script-src']` and `['connect-src']`.
 
-Reference outputs:
-- `tests/framework-fixtures/nextjs-turborepo/expected-after-patch.ts` (Next.js)
-- `tests/framework-fixtures/sveltekit-csp/expected-after-patch.js` (SvelteKit)
-
 Idempotency: if `__monodesignLiveDev` already exists in the file, the patch is already applied; skip asking and just mark `cspChecked: true`.
 
 #### append-string
@@ -707,10 +703,6 @@ Per-framework specifics:
 - **Next.js inline `headers()`**: edit `next.config.*`, splicing the variable into the CSP value.
 - **Nuxt `routeRules`**: edit `nuxt.config.*`, splicing into the CSP in `routeRules['/**'].headers['Content-Security-Policy']`.
 
-Reference outputs:
-- `tests/framework-fixtures/nextjs-inline-csp/expected-after-patch.js` (Next.js)
-- `tests/framework-fixtures/nuxt-csp/expected-after-patch.ts` (Nuxt)
-
 ### Troubleshooting
 
 If a user says "no" to the CSP patch at setup time and later complains that live doesn't work: their dev CSP blocks `http://localhost:8400`. Fix: delete `cspChecked` from `.monodesign/live/config.json` and re-run `live.mjs`: setup will ask again.

package/packages/@monomind/cli/.claude/skills/monodesign/reference/polish.md

@@ -38,9 +38,9 @@ Understand the current state and goals before touching anything:
 4. **Pull in any prior critique** (optional signal): If `/monodesign critique` has been run on the same target, its priority issues are a useful prior for what to address first. Resolve the target to a file path or URL, then:
    ```bash
    slug=$(node .claude/skills/monodesign/scripts/critique-storage.mjs slug "<resolved>")
-   node .claude/skills/monodesign/scripts/critique-storage.mjs latest "$slug"
+   node .claude/skills/monodesign/scripts/critique-storage.mjs recall "$slug"
    ```
-   Exit 0 with body = found; fold the P0/P1 items into your polish list and mention the snapshot path so the user sees what you read. Exit 2 = no snapshot, continue without it. The critique is one input among many. Do your own pass either way.
+   Exit 0 prints a compact markdown block: latest score, score trend with direction, the open P0/P1 item titles, and the snapshot path. Fold the P0/P1 items into your polish list and mention the snapshot path so the user sees what you read. If you need the full snapshot body behind an item, read the printed snapshot path directly (or run the `latest` subcommand). Exit 2 = no snapshot, continue without it. The critique is one input among many. Do your own pass either way.
 
 5. **Triage cosmetic vs functional**: Classify each issue as **cosmetic** (looks off, doesn't impede the user) or **functional** (breaks, blocks, or confuses the experience). When polish time is tight, functional issues ship first; cosmetic ones can land in a follow-up. Quality should be consistent; never perfect one corner while leaving another rough.