Maude, how it works mostly.
Vibe-design & vibe-code workflows for Claude Code. Two plugins, one CLI, some vibes.
design iterates on HTML mocks. flow runs the agentic loop until the feature actually ships. maude scaffolds the second-brain .ai/ workspace they both pretend they could live without.
Open-source. Catalog-graded. No telemetry, no signup, no book a demo button. If it crashes, git pulland try again. That's the entire support contract.
# 0. install the CLI (skills use it) npm i -g @1agh/maude # 1. add the marketplace /plugin marketplace add 1aGh/maude # 2. install plugins /plugin install design@maude /plugin install flow@maude # 3. init the workspace /flow:init /design:init
The canvas talks back now.
Cmd+Click an element and edit its CSS against your real design tokens — Figma-style scrub fields, a searchable Variables popover that shows where each token is defined, and one colour picker for fill and border alike. It writes straight back to the source .tsx. The AI sits this one out.
The catalog.
two plugins · one CLI · one hub · v0.30.0 · what shipped ->design Iterates canvases until they stop being embarrassing.
Canvas-first iteration on HTML/JSX mocks. Zero-dep Node dev-server. Cmd+Click element inspector. Snapshot stack per canvas.
flow The agentic loop that ships things eventually.
Plan, execute, done, validate. Second-brain .ai/ workspace. Project-agnostic via per-repo workflows.config.json. Same plugin runs in Next.js, Expo, Go, anything.
maude The plumbing the other two pretend not to need.
Scaffolds the .ai/ workspace. Reads and writes config. Boots the design dev server. Pure ESM, zero runtime deps beyond Node 20+.
hub Mirrors your canvases across the team. No SaaS tier.
Optional self-hosted Yjs sync hub — mirror .design/ across collaborators in real time. Docker or Fly, on your infra, no cloud middleman.