@infinitedusky/indusk-mcp 0.7.0 → 0.7.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.
Files changed (2) hide show
  1. package/package.json +1 -1
  2. package/skills/document.md +1 -2
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@infinitedusky/indusk-mcp",
3
- "version": "0.7.0",
3
+ "version": "0.7.1",
4
4
  "description": "InDusk development system — skills, MCP tools, and CLI for structured AI-assisted development",
5
5
  "type": "module",
6
6
  "files": [
package/skills/document.md CHANGED
@@ -70,8 +70,7 @@ The `decisions/` and `lessons/` directories are **not** populated during normal
70
70
 
71
71
  - **One concept per diagram.** Don't cram the entire system into one chart. Break complex systems into focused diagrams.
72
72
  - **Meaningful labels.** Use full words, not abbreviations. `Plan Skill` not `PS`.
73
- - **Use `classDef` for visual grouping.** Color-code related nodes to show categories at a glance.
74
- - **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.
73
+ - **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.
75
74
  - **Keep diagrams small enough to read inline** but detailed enough to be useful when expanded.
76
75
 
77
76
  ### Always Use FullscreenDiagram