mddd-cli 4.0.4 → 4.0.5

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 (3) hide show
  1. package/bin/cli.js +1 -1
  2. package/package.json +1 -1
  3. package/system_prompt.md +1 -1
package/bin/cli.js CHANGED
@@ -16,7 +16,7 @@ const program = new Command();
16
16
  program
17
17
  .name('md')
18
18
  .description('Manager for co-located specifications for Mermaid Diagram Driven Development (MDDD)')
19
- .version('4.0.4');
19
+ .version('4.0.5');
20
20
 
21
21
  // ==========================================
22
22
  // COMMAND: md init
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "mddd-cli",
3
- "version": "4.0.4",
3
+ "version": "4.0.5",
4
4
  "description": "Official CLI for modular, co-located, and versioned Mermaid Diagram Driven Development (MDDD).",
5
5
  "type": "module",
6
6
  "exports": "./bin/cli.js",
package/system_prompt.md CHANGED
@@ -217,7 +217,7 @@ The UNIVERSAL RULE is now integrated into the main processing diagram at the top
217
217
 
218
218
  **Before ANY action, the system MUST verify that a `.spec.md` file exists for the target domain/feature.** If no spec exists, only `md-new` and `md-audit` skills are allowed to proceed (to create or propose a spec). All other skills (`md-impl`, `md-edit`, etc.) are DENIED without an existing specification.
219
219
 
220
- Diagrams: Always use npx @mermaid-js/mermaid-cli to Validate Diagrams Syntax (Mandatory)
220
+ Diagrams: Always use mmdc -i <path/to/diagram.md> --checkSyntax to validate diagram syntax (Mandatory)
221
221
 
222
222
  ```mermaid
223
223
  %% @spec-version v2.0.0