Handdraw Flowchart

Workflow

1. Convert the user's natural-language process into one supported Mermaid diagram:

   • flowchart TD or flowchart LR for business processes, decision trees, and state transitions.
   • sequenceDiagram for actor/system interactions over time.
   • classDiagram for domain objects, DTOs, entities, interfaces, and relationships.

2. Generate raw Mermaid only. Do not wrap it in Markdown fences when writing .mmd files.

3. Read references/mermaid-generation-rules.md before producing non-trivial Mermaid, especially for sequence or class diagrams.

4. Save the Mermaid source as \x3Cname>.mmd.

5. Run the renderer script. It performs strict Mermaid parsing before conversion:

   cd \x3Cskill-directory>
   npm install
   node scripts/render-mermaid-handdraw.mjs --input /path/to/\x3Cname>.mmd --out-dir /path/to/output --name \x3Cname>
   

The script writes:

• \x3Cname>.mmd: normalized Mermaid source
• \x3Cname>.excalidraw: editable Excalidraw scene
• \x3Cname>.png: rendered PNG

Conversion Contract

• Treat flowchart as the primary hand-drawn path. It converts to native Excalidraw elements and gives the best editable sketch-style result.
• Treat sequenceDiagram as supported but still verify output visually when the diagram is complex.
• Treat classDiagram as supported with possible image fallback inside the Excalidraw scene. If the script reports image-fallback, the PNG is valid, but editability is limited.
• Reject unsupported Mermaid diagram types instead of silently producing a lower-quality result.
• Do not claim success until the renderer has completed without validation or export errors.

Strict Validation Rules

• Run node scripts/render-mermaid-handdraw.mjs --input \x3Cfile> --validate-only after generating Mermaid if you need a fast syntax gate.
• If validation fails, edit the Mermaid source and rerun. Do not bypass validation.
• Prefer simple Mermaid syntax over clever syntax. Avoid custom CSS, HTML labels, Markdown tables inside labels, YAML frontmatter, and experimental Mermaid shape declarations.
• Keep node IDs stable and ASCII where practical. Put user-facing Chinese text in labels, not IDs.

Rendering Notes

• The script uses browser execution because Excalidraw export utilities require DOM/canvas APIs.
• If Playwright has no bundled browser, the script tries common local Chrome/Chromium executable paths and honors CHROME_PATH.
• For reproducible results, keep the versions pinned in package.json unless there is a specific reason to upgrade and retest the renderer.