Overview
A project is a connected app, not a container of rules. Each project serves your brand ruleset untouched, plus a small set of overrides scoped to that app. The brand stays the source of truth, and every project inherits it by default.
How inheritance works
When an app reads from a project over MCP, it receives the brand styles, rules, and component vocabulary first. The project then layers its own sparse overrides on top of that inherited base.
Two rules govern the result:
- The project wins on conflict. Where a project override and the brand disagree, the project value applies for that app.
- The brand is never modified. Overrides live on the project. Changing a project never edits the brand, and other projects are unaffected.
This keeps one brand serving many apps consistently, while letting a single app diverge where it has to.
The effective view
Each project shows an effective (resolved) view. This is what an AI tool actually receives: the brand ruleset with the project overrides applied. Read the effective view to confirm what an app sees, rather than reading the brand and the overrides separately.
Where projects live
Projects sit under a brand. The sidebar footer lists the projects you touched most recently, with New project to add one and View all for the full list. Open a project and its overview shows the overrides it carries, with Connect your AI tools for wiring up a tool.
Every plan can add overrides. What differs by plan is how many projects a brand can hold. See Plans.
