Introduction
Roadmap
Where Marmo is headed — from open-source components to the free Core MCP to on-brand generation — plus a board you can vote on.
Status: beta
Roadmap
Marmo's goal is simple: the agent you already use should design like it knows your product. Everything below serves that — open components as the foundation, the MCP as the brain, your brand as the output.
The path
| Phase | What ships | Status |
|---|---|---|
| 1 | @marmoui/ui public on npm — every core component, MIT. | In progress |
| 2 | Public docs site — components, foundation, agent setup. | In progress |
| 3 | Free Core MCP — connect any agent, no account needed. | Next |
| 4 | Accounts + Pro — checkout, entitlements, personal MCP tokens. | Planned |
| 5 | On-brand generation — your DESIGN.md drives every generated screen. | Planned |
| 6 | Prototypes — shareable generated apps with inline review comments. | Planned |
Quality climbs with the phases: docs and MCP knowledge stay in lockstep (same source, re-indexed on deploy), and component docs keep gaining ## Patterns / ## Common Mistakes sections so agent output keeps getting better without you changing anything.
Vote on what ships next
Upvote cards to signal what hurts most — one input alongside team capacity. To add new work, use Open GitHub issue below; we can link or clone it onto this board when it's accepted.
Status labels
| Status | Meaning |
|---|---|
| Not started | No active effort; may still be prioritized. |
| In progress | Someone is actively working or it's partially landed. |
| Blocked | Waiting on dependency, decision, or capacity. |
| Done | Shipped for this roadmap slice. |
| Ongoing | Maintained as the system evolves. |
Iconography semantics
When to use which icon metaphor; avoid misleading decorative icons.
Internationalization and localization
Pluralization, truncation, RTL callouts, and locale-aware formatting in docs examples.
Prototypes
Shareable agent-generated apps reviewers can open, sign into, and comment on inline.
## Patterns / ## Common Mistakes sweep
Better MCP knowledge = better agent output. High-traffic component MDX first.
Component descriptions in props JSON
JSDoc on *Props or hand-edited JSON for MCP summaries on subcomponents.
"When to use" decision trees
Dialog vs Drawer vs Popover; Select variants — so agents (and humans) pick the right primitive first try.
On-brand generation (Pro)
DESIGN.md schema + /marmo-ui:init shipped; workspace ingestion next — your tokens drive every connected agent.
Per-component token overrides
Every component exposes its visual tokens so a DESIGN.md components: block can override them tenant-wide.
@marmoui/ui public on npm
MIT license, public registry, clean install in any React 19 app.
Free Core MCP
Public knowledge tier, no auth — connect Claude Code, Codex, Cursor, Gemini CLI and generate.
Priority component MDX
Text, DatePicker, Dialog, Select, Field, Badge — patterns + mistakes; knowledge audit trending up.
audit:knowledge in CI
Optional gate: warn/fail on regression vs agreed floors.
MCP server + Claude Code plugin
Streamable HTTP, get_pattern, review_generated_code, /marmoui:* commands.
Voice & tone + feedback patterns
Shipped — see Voice & Tone. Alert, Dialog, Toast, Field structures.
pnpm audit:knowledge
Continuous audit of docs → MCP knowledge quality.
This roadmap
Living doc — bump lastUpdated when cards or statuses change.
Principles that don't move
- Components stay free. Anything shipped free is never moved behind the paywall.
- The MCP is context, not a generator. Your agent does the generation with your own tokens; the MCP supplies the knowledge.
- Docs = MCP knowledge. One source; if the docs are wrong the agent is wrong, so docs accuracy is a release gate.
- No slop. Validation (
review_generated_code) ships with every knowledge tier, including free.
Related links
- Install the agent — connect and generate today.
- Voice & Tone — principles + feedback structures.
When this roadmap moves, update cards (status badges and copy) and bump lastUpdated in the frontmatter.