@infinitedusky/indusk-mcp 0.7.0 → 0.7.2

package/dist/bin/commands/init.js

@@ -295,7 +295,7 @@ export async function init(projectRoot, options = {}) {
     console.info("\n[Hooks]");
     const hooksSource = join(packageRoot, "hooks");
     const hooksTarget = join(projectRoot, ".claude/hooks");
-    const hookFiles = ["check-gates.js", "gate-reminder.js"];
+    const hookFiles = ["check-gates.js", "gate-reminder.js", "validate-impl-structure.js"];
     if (existsSync(hooksSource)) {
         mkdirSync(hooksTarget, { recursive: true });
         for (const file of hookFiles) {
@@ -318,7 +318,10 @@ export async function init(projectRoot, options = {}) {
         PreToolUse: [
             {
                 matcher: "Edit|Write",
-                hooks: [{ type: "command", command: "node .claude/hooks/check-gates.js" }],
+                hooks: [
+                    { type: "command", command: "node .claude/hooks/check-gates.js" },
+                    { type: "command", command: "node .claude/hooks/validate-impl-structure.js" },
+                ],
             },
         ],
         PostToolUse: [
@@ -335,11 +338,15 @@ export async function init(projectRoot, options = {}) {
         for (const [event, entries] of Object.entries(hookConfig)) {
             const existingEntries = existing.hooks[event] || [];
             // Check if our hook is already present
-            const hasOurHook = existingEntries.some((e) => e.hooks?.some((h) => h.command?.includes("check-gates") || h.command?.includes("gate-reminder")));
+            const hasOurHook = existingEntries.some((e) => e.hooks?.some((h) => h.command?.includes("check-gates") ||
+                h.command?.includes("gate-reminder") ||
+                h.command?.includes("validate-impl")));
             if (!hasOurHook || force) {
                 // Remove old entries if force, then add
                 if (force) {
-                    existing.hooks[event] = existingEntries.filter((e) => !e.hooks?.some((h) => h.command?.includes("check-gates") || h.command?.includes("gate-reminder")));
+                    existing.hooks[event] = existingEntries.filter((e) => !e.hooks?.some((h) => h.command?.includes("check-gates") ||
+                        h.command?.includes("gate-reminder") ||
+                        h.command?.includes("validate-impl")));
                 }
                 existing.hooks[event] = [...(existing.hooks[event] || []), ...entries];
                 hooksUpdated = true;

package/dist/bin/commands/update.js

@@ -114,7 +114,7 @@ export async function update(projectRoot) {
     let hooksUpdated = 0;
     let hooksCurrent = 0;
     if (existsSync(hooksSource) && existsSync(hooksTarget)) {
-        const hookFiles = ["check-gates.js", "gate-reminder.js"];
+        const hookFiles = ["check-gates.js", "gate-reminder.js", "validate-impl-structure.js"];
         for (const file of hookFiles) {
             const sourceFile = join(hooksSource, file);
             const targetFile = join(hooksTarget, file);

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@infinitedusky/indusk-mcp",
-	"version": "0.7.0",
+	"version": "0.7.2",
 	"description": "InDusk development system — skills, MCP tools, and CLI for structured AI-assisted development",
 	"type": "module",
 	"files": [

package/skills/document.md

@@ -70,9 +70,9 @@ The `decisions/` and `lessons/` directories are **not** populated during normal
 
 - **One concept per diagram.** Don't cram the entire system into one chart. Break complex systems into focused diagrams.
 - **Meaningful labels.** Use full words, not abbreviations. `Plan Skill` not `PS`.
-- **Use `classDef` for visual grouping.** Color-code related nodes to show categories at a glance.
-- **Dark-mode friendly.** Avoid hardcoded light colors (white, light gray). Use the mermaid `dark` theme (already configured in VitePress). If you must customize colors, use high-contrast pairs.
+- **Do not use custom `style`, `classDef`, or `themeVariables` in diagrams.** The docs site supports both light and dark mode. The vitepress-plugin-mermaid auto-switches between Mermaid's `default` (light) and `dark` themes. Hardcoded colors (fills, text colors, borders) that work in one mode will be unreadable in the other. Let the built-in theme handle all colors. If you need visual grouping, use `subgraph` blocks instead of color-coding.
 - **Keep diagrams small enough to read inline** but detailed enough to be useful when expanded.
+- **Mermaid `securityLevel` must be `"strict"`.** Using `"loose"` causes Mermaid to scan the entire page DOM for diagram content, which produces "Syntax error in text" errors in the footer of every page. Always use `"strict"` in the VitePress mermaid config.
 
 ### Always Use FullscreenDiagram
 

package/skills/domain/vitepress.md

@@ -16,6 +16,9 @@ You are working with a VitePress documentation site. Follow these patterns.
 - Keep diagrams focused — one concept per diagram
 - Use `flowchart TD` for top-down flows, `flowchart LR` for left-right
 - Use `classDiagram` for type relationships, `sequenceDiagram` for interactions
+- **Set `securityLevel: "strict"` in the mermaid config.** Using `"loose"` causes Mermaid v10+ to scan the entire page DOM, producing "Syntax error in text" errors on every page.
+- **Do not use `style`, `classDef`, or `themeVariables` with hardcoded colors.** The `vitepress-plugin-mermaid` auto-switches between `default` (light) and `dark` themes. Hardcoded colors break in the opposite mode. Use `subgraph` for visual grouping instead.
+- **Set `theme: "default"` in the mermaid config.** The plugin overrides to `"dark"` automatically when VitePress dark mode is active. Do not set `theme: "dark"` or `theme: "base"` — they interfere with the auto-switching.
 
 ## Sidebar & Navigation