mddd-cli 1.0.4 → 1.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.
- package/bin/cli.js +4 -3
- package/package.json +1 -1
package/bin/cli.js
CHANGED
|
@@ -81,13 +81,14 @@ If the file is the Feature Contract: Focus only on:
|
|
|
81
81
|
- Versioning: Keep SPEC_VERSION always at the top.
|
|
82
82
|
|
|
83
83
|
** RULES: **
|
|
84
|
-
1. When generating diagrams from code, always
|
|
85
|
-
2. ASCII Art or
|
|
84
|
+
1. When generating diagrams from code, always remove function name parentheses. Keep the diagram clean and avoid rendering errors.
|
|
85
|
+
2. ASCII Art or drawings are PROHIBITED. Use only Mermaid diagrams for visual representation.
|
|
86
86
|
2. Every diagram must be encapsulated in markdown code blocks with the language 'mermaid'.
|
|
87
87
|
3. For architecture flows or business logic, use exclusively 'graph TD' or 'graph LR'.
|
|
88
88
|
4. For (finite) state machines, use 'stateDiagram-v2'.
|
|
89
89
|
5. Name the nodes, use specific shapes ([...], ([...]), { ... }) to indicate intent (Action, Start/End, Decision).
|
|
90
|
-
|
|
90
|
+
6. ALWAYS WORK ON THE .SPEC.MD FILES. If they don't exist, create them. They are the single source of truth. Never make changes directly in the code without reflecting them in the diagrams.
|
|
91
|
+
`;
|
|
91
92
|
|
|
92
93
|
fs.writeFileSync('system_prompt.md', promptContent);
|
|
93
94
|
|