For product teams
Six engineers, four repos, one agent each. Same product?
When everyone prompts their own way, the app, the marketing site and the admin tool stop looking related. moodspec gives the team one canvas — reviewed, versioned, and read by every agent in every repo.
What goes wrong
The design system exists. It just isn't where the agents are.
Six private versions of the truth
Everyone keeps a personal prompt preamble in a notes app. None of them match, and none of them get updated when the brand does.
Review catches it too late
Design sees the drift in a PR screenshot, after the agent generated forty components. Now it's rework, not a comment.
Onboarding is oral history
A new hire learns the rules by getting them wrong in review, or by asking in Slack and getting three different answers.
How teams use it
Who does what, and what stops happening.
| Surface | Repo token | Whose agent | Last read |
|---|---|---|---|
| Product app | tok_applive | 4 engineers | 2 min ago |
| Marketing site | tok_wwwlive | 1 designer | this morning |
| Internal admin | tok_adminlive | 2 engineers | yesterday |
| Docs | tok_docsrevoked | former vendor | Mar 4 |
One canvas, four scoped tokens. Revoking one repo doesn’t touch the others.
- 01
New engineer · week one
Onboarding stops being oral history
The MCP config ships in the repo, so their agent is pointed at the team canvas before they've had their first standup. They don't have to know that we dropped the violet in March, or that error copy never starts with "Oops".
Instead of"quick q — which blue do we use?" in three channels, answered three different ways.
- 02
Design lead · after a decision
A change lands once, everywhere
Tighten the spacing scale on the canvas, leave a comment saying why, get an owner's approval. Every agent on every surface reads the new value on its next prompt — no announcement to write, none to miss.
Instead ofa Figma comment, a Notion update and two repos that never got the memo.
- 03
Reviewer · pull request
Review is about the product again
When the agent already had the type scale, the palette rules and the voice, review comments move off "wrong font, wrong tone" and onto whether the flow is right.
Instead ofcatching drift in a PR screenshot after forty components were generated.
Business is $24 per editor, three minimum.
Shared workspace with roles, a locked brand canvas only owners can change, comments and approvals on every card, and scoped tokens per repo.
What teams ask before rolling this out
- Is this a replacement for our design system?
- No. Your component library stays where it is. The canvas is the layer above it — the decisions and intent an agent needs before it picks components, plus the things a library never encodes: who you're writing for, tone, what you'd never ship.
- Who is allowed to change it?
- Whoever you make an owner. On Business the brand canvas can be locked so editors propose changes with comments and an owner approves — and every version is restorable.
- How does it get into our repos?
- One MCP entry per repo, committed with the project, using a token scoped to that repo. New teammates inherit it by cloning.
- What about the three-editor minimum?
- Editors are people who change the canvas. Everyone else reads it for free — including every agent and every repo you connect.