The design tool built around Claude, not bolted onto one. Download the desktop app and make a canvas; plugins, the CLI and a self-hosted hub are there when you want more. No telemetry.

Using Maude

For designers and teams. No terminal needed.

Tutorials and how-to guides

Getting started5 min The Mac app Share links and inviting Maude Cloud Moving from Maude 1

Advanced

For Claude Code, the command line and self-hosting.

Reference, explanations and recipes · every page kept

ExploreThe design plugin The flow plugin The maude CLI Self-hosted hub Flow migrationMore: Orchestration, Codex, Config, Security

Look upDesign commands Flow commands Config schema Design system schema

RecipesNext.js Expo pnpm monorepo

People start here

Make your first canvasAsk AI for a draft, or draw it.Invite your teamOne Share button, three roles.Bring your design systemColours, type, components.Export anythingPNG, PDF, video, or code.

NewMaude 2 · Sign in to a team server in your browserRead the changelog

Most design tools bolt AI onto a human workflow. Claude's own canvas is a chat box that forgets everything by morning. Maude is built around Claude from day one, so canvases are real files, and the same repo-native model runs flow's plan-to-ship loop too. That's the whole pitch.

Start with the desktop app. Download it, open a project, say what to make. No terminal, no signup to try it, no telemetry. ⌘K searches everything.

Download for Mac.dmg · Apple Silicon & Intel · free, no signup

Windows LinuxAbout the desktop app

Open-source. MIT. If it crashes, git pull and try again. That's the entire support contract.

Pick a direction

Getting Started

Download the app, open a project, make your first canvas. Three steps, no terminal.

Around the window

The project pill and its one menu, Search, the Share cluster, panels, toolbars, Settings.

Share and collaborate

Invite people, copy a link, work together live on Maude Cloud or your own hub.

Coming from Maude 1

Where Maude 1's controls went, and the keys that moved.

Advanced / Explore Maude

Everything the desktop app does is also available from a terminal, a plugin or a server you run yourself. None of it is needed to get started.

design. Canvas-first iteration on .tsx canvases under .design/, driven by /design:* slash commands in Claude Code or Codex. Select an element and the next /design:edit knows which one you mean.
flow. The agentic loop that ships things eventually. Second-brain .ai/ workspace, project-agnostic via per-repo workflows.config.json. Same plugin runs in Next.js, Expo, Go, anything.
maude (legacy alias: mdcc). Small CLI. Scaffolds the .ai/ workspace, reads and writes config, boots the design dev server, runs health diagnostics (doctor), manages the sidecar cache, and hosts the optional sync hub.

MDCC-DGM/MAPArchitectureMap

Claude Codehost shell · plugin marketplace

/plugin design

MAUDE/PLG·DSN

canvas-first TSX mocks

/plugin flow

MAUDE/PLG·FLW

agentic .ai/ workspace loop

maudeCLI · @1agh/maude

.ai/owned by flow

├─state/STATE.md
├─plans/
├─decisions/
└─workflows.config.json

.design/owned by design

├─config.json
├─ui/
├─system/
└─_history/

maude at a glance — Claude Code, the two plugins, the CLI, and the .ai/ + .design/ workspaces

`maude` CLI

Subcommands: init, config, doctor, cache, design, hub.

Design canvas loop

`/design:new`, `/design:edit`, `/design:critic`, and the rest of the canvas loop.

Flow lifecycle

The 30 slash commands behind plan, execute, done, validate, release.

Config reference

Every key in `.ai/workflows.config.json` with examples.

Recipes

Drop-in setups for Next.js, Expo, and pnpm monorepos.

Self-host the hub

Optional Yjs sync hub — mirror `.design/` across collaborators. You run it; there's no SaaS tier.

Why both plugins together?

The two plugins share a worldview. Claude Code is the IDE. The repo is the source of truth. Decisions get written to .ai/decisions/. Plans get archived to .ai/plans/archive/. Design mocks live in .design/ next to the production code they precede. Nothing lives only in a chat scroll.

Install one, install both. They're independent.

MDCC-DGM/STTStatPanel

41commandsdesign + flow

12criticspanel agents

2pluginsdesign · flow

1CLI@1agh/maude

0telemetryby design

The catalog at a glance

License and source

MIT. Source at github.com/1aGh/maude. Open issues if it breaks. Send PRs if you have a better idea. I read both.

Maude, how it works mostly