Draft from rough notes
Start with specs, architecture notes, or a broken Mermaid block instead of a blank editor.
MermaidPen
Write once. Render everywhere.
MermaidPen is a workflow layer for Mermaid diagrams. This first build ships the sharpest wedge first: compatibility checks, repair guidance, and a deployable studio that helps technical teams harden Mermaid before it breaks in docs workflows.
Mermaid-native, not canvas-firstCompatibility-aware, not just AI-generatedUseful as a deployable first version on Vercel today
Compatibility wedge
flowchart LR notes[Paste notes] scan[Compatibility scan] fix[Safe repairs] publish[Ship to docs] notes --> scan --> fix --> publish
Why this first version
Do not compete as a prettier Mermaid editor.
The market already has editors, whiteboards, and AI diagram tools. The sharper opening is reliability: helping teams generate, inspect, and publish Mermaid that survives the environments where it actually gets consumed.
Run conservative checks
Choose a target preset and catch the syntax and portability hazards that make Mermaid fragile across platforms.
Repair before shipping
Apply safe rewrites, preview the result, and export clean SVG for docs, repos, and internal knowledge bases.
What this build already proves
A real, Vercel-ready product shell.
This is not a static mock. The studio page can render Mermaid, flag conservative compatibility risks, apply safe repairs, and export SVG in the browser.
Prompt-to-Mermaid generation for PRDs, incident notes, and service maps
Target-specific repair presets for GitHub, GitLab, and markdown-heavy docs
Share links, export history, and repository-facing publishing flows
Next step
Use the studio as the seed of the MVP.
After this deployable first pass, the next move is straightforward: add prompt-to-Mermaid generation, saved diagrams, and GitHub-linked publishing paths without bloating the product into a generic whiteboard.