Diagrams worth sharing.

Turn Mermaid into clear architecture, workflows, and sequences. Your coding agent brings the ideas. Beautiflow handles the rendering and checks.

Install BeautiflowExplore the examples

CLI + portable skill · Pi, Claude Code & Codex

Customers call an Orders API connected to a database and a queue, worker, and notification path within a platform boundary

Order platform. Services, dependencies, and one clear boundary. Native Mermaid architecture rendering; no automatic polish.

Mermaid sourceFull-size SVG
Mermaid stays your source of truthSVG & PNG outputRead-only live previewOpen source · MIT

Same meaning.
Clearer priorities.

Make the happy path obvious without hiding the exception. Semantic emphasis changes the presentation, not the relationships.

Before: Draft reaches a Ready decision, with equally weighted Yes to Ship and No to Revise branches
Before: every path has equal weight.A valid diagram, without an explicit visual priority.
After: Draft to Ready to Ship is emphasized in blue, while the No to Revise branch is red and still explicitly labelled
After: the main path stands out.Four nodes. Three relationships. Every label preserved.

Real outputs from one semantic action pass—not a simulated before/after or a layout-score claim. Read the Mermaid source, or open the visual test gallery for layout comparisons.

Install once.
Ask your agent.

A standalone runtime and a portable skill. No model keys in Beautiflow—your existing harness owns the conversation.

  1. Install Beautiflow

    Download the standalone CLI.

    curl -fsSL https://beautiflow.cc/install.sh | bash

  2. Add the agent skill

    Give your harness the diagram workflow.

    beautiflow install-skill

  3. Open your harness

    Ask for a diagram in Pi, Claude Code, or Codex.

    Use Beautiflow to draw an order platform with an API, database, and background worker.

Prefer to inspect the script first? Read the installer. For harness-specific skill paths and manual installation, read the setup guide.

Agents supply judgment.
Beautiflow supplies control.

The CLI is built for agents. Deterministic operations stay separate from model judgment—and a successful render is only part of the check.

Keep the meaning

Mermaid holds the relationships. Sidecars hold layout overrides. Polishing never changes topology to make a diagram look better.

How layout state works

Check, then change

A validated plan precedes each supported agent mutation. Receipts enforce verification, allow one named correction, and support rollback.

Read the agent protocol

Know the limits

Flowcharts and state diagrams support polish. Architecture supports rendering and audit. Specialized families use their own renderers.

See family support