Maude, how it works mostly

Vibe-design & vibe-code workflows for Claude Code. Two plugins, one CLI, some vibes. No telemetry, no signup.

Two plugins, one CLI, and the .ai/ workspace they both pretend not to need. You're probably here for design or flow. maude is the plumbing. Cmd-K skips ahead.

design. Canvas-first iteration on HTML / JSX mocks under .design/. Zero-dep dev server. Cmd+Click inspector overlay so Claude knows which element the feedback is about.
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.

Open-source. MIT. No telemetry, no signup, no book a demo button. If it crashes, git pull and try again. That's the entire support contract.

Pick a direction

Getting Started

Four steps and you're in. (Maybe five. Depends on your shell.)

`maude` CLI

Subcommands: init, config, design serve, design init.

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.

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.

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.