Context module
Make your whole brand AI‑ready.
Your brand books and files become five machine‑readable parts: Brand System, Visual identity, Design system, Templates and Media.
Your brand lives in decks and people’s heads. AI can’t read it there.
Monobase turns your whole brand into machine‑readable rules.
1 in 4documents a company sends out doesn’t follow its own brand guidelines.
Source: empower and Kantar, Corporate Design Report 2025
-
HannahBrand manager Same brand questions. Every. Single. Week. 🙃
Can’t the brand just answer for itself?
-
JamesMarketing Which positioning is the latest? Asking for the fifth time 😅
One version everyone trusts. Is that too much?
-
OliverDesigner Two design systems. One for product, one for marketing 😵
Why can’t it just be one?
Illustrative voices, not customer quotes.
Your whole brand in one place,in five parts.
One brand management platform answers all three. Agents build it from the files you have, and your team approves.
-
Brand System
Your agents write in your brand’s voice.
-
Visual identity
Your brand manual, as rules AI follows.
-
Design system
A full design system, built from yours.
-
Templates
Agents fill your templates without breaking them.
-
Media
Agents reuse the images you already have.
How it fits together
Set a rule once. Every brand and team below follows it.
Groups, brands, sub-brands and products, as many levels as you need, each with its documents, speakers and channels. Mark a document binding and every level below reads it, so an agent writing for a product starts from its brand’s tone of voice.
Diagram of the structure Monobase holds, shown for a fictional company: a group, its brands and products with their documents, speakers, channels, templates and media, and binding documents passing down. Select a part to see what it is and where it applies. Select a dot to read what it is and where it applies; pinch or use the zoom buttons to zoom.
The structure as a list:
- Group (Group)
- Positioning (Document, binding below). Inherited by Sub-brand A, Sub-brand B
- Tone of voice (Document, binding below). Inherited by Sub-brand A, Sub-brand B
- Guardrails (Document, binding below)
- Personas (Document). Inherited by Personas, Personas
- Visual identity (Visual identity). Used by Templates, Templates
- Design system (Design system). Used by Templates, Templates, Templates, Templates
- Media library (Media). Shows Product A1, Product B1, Product B2
- CEO (Speaker). Publishes on LinkedIn, Website
- LinkedIn (Channel). Published by CEO
- Website (Channel). Published by CEO
- Sub-brand A (Sub-brand). Inherits Positioning, Tone of voice
- Positioning (Document, binding below). Inherited by Product A1, Product A2, Product A3
- Messaging house (Document, binding below)
- Personas (Document). Inherits Personas
- CMO (Speaker). Publishes on Instagram, Newsletter, Website, TikTok
- Instagram (Channel). Published by CMO
- Newsletter (Channel). Published by CMO
- Website (Channel). Published by CMO
- Templates (Templates). Follows Visual identity
- Product A1 (Product). Media from Media library. Inherits Positioning
- Product sheet (Document)
- Positioning (Document)
- Packshots (Media)
- Templates (Templates). Follows Design system
- Product A2 (Product). Inherits Positioning
- Product sheet (Document)
- Packshots (Media)
- TikTok (Channel). Published by CMO
- Product A3 (Product). Inherits Positioning
- Product sheet (Document)
- Packshots (Media)
- Templates (Templates). Follows Design system
- Sub-brand B (Sub-brand). Inherits Positioning, Tone of voice
- Positioning (Document, binding below)
- Tone of voice (Document, binding below). Inherited by Product B1, Product B2, Product B3
- Messaging house (Document, binding below)
- Personas (Document). Inherits Personas
- Brand lead (Speaker). Publishes on Instagram, TikTok, Newsletter
- Product lead (Speaker). Publishes on TikTok, Website
- Instagram (Channel). Published by Brand lead
- TikTok (Channel). Published by Brand lead, Product lead
- Newsletter (Channel). Published by Brand lead
- Templates (Templates). Follows Design system, Visual identity
- Product B1 (Product). Media from Media library. Inherits Tone of voice
- Product sheet (Document)
- Positioning (Document)
- Packshots (Media)
- Product B2 (Product). Media from Media library. Inherits Tone of voice
- Product sheet (Document)
- Packshots (Media)
- Website (Channel). Published by Product lead
- Product B3 (Product). Inherits Tone of voice
- Product sheet (Document)
- Packshots (Media)
- Templates (Templates). Follows Design system
MCP
Monobase is an MCP server for your brand.
Claude, ChatGPT, Cursor, Copilot and any other MCP client read your approved Brand System and design system as they are written. Read-only by default, signed in with OAuth, so nobody explains the brand to each chat again.
- Once a document is approved, AI tools read that version. New edits wait for the next approval.
- Visual identity, templates and media are used by agents inside Monobase.
ClaudeWhat's Lumo's tone of voice?
MonobaseDirect, warm, short.Brand System› Tone of voice v4
ChatGPTWhat's Lumo's tone of voice?
MonobaseDirect, warm, short.Brand System› Tone of voice v4
CursorWhat's Lumo's tone of voice?
MonobaseDirect, warm, short.Brand System› Tone of voice v4
GitHub CopilotWhat's Lumo's tone of voice?
MonobaseDirect, warm, short.Brand System› Tone of voice v4
ClaudeWhat's Lumo's tone of voice?
MonobaseDirect, warm, short.Brand System› Tone of voice v4
ChatGPTWhat's Lumo's tone of voice?
MonobaseDirect, warm, short.Brand System› Tone of voice v4
CursorWhat's Lumo's tone of voice?
MonobaseDirect, warm, short.Brand System› Tone of voice v4
GitHub CopilotWhat's Lumo's tone of voice?
MonobaseDirect, warm, short.Brand System› Tone of voice v4
Agents
The agents in Context. They propose. A person approves.
-
Brand agent
Reads your brand documents, researches competitors and drafts changes, with sources.
-
Design system agent
Answers from your design system and proposes token changes.
-
Template Author
Turns a Figma frame into a template with a contract for AI.
Questions about the brand management platform
What is a brand context platform?
A brand context platform is a brand management platform that AI agents can read: who the brand is and how it speaks, its logos, colours and type, its design tokens, its templates and its images, everything a person or an AI tool needs to make something on brand. Monobase keeps all five parts in one workspace, so your team and its agents work from the same approved version.
Do we need all five parts from day one?
No. Start with the one that costs your team the most work today, such as the brand book, the design system or templates, and add the rest once it works. The Symbio team sets it up with you.
What do AI tools see over MCP?
AI tools read your brand documents and design system over MCP, as they are written. Once a document is approved, they read that version, and new edits wait in Monobase until the next approval. Visual identity, templates and media are used by agents inside Monobase.
We already have a brand portal. What changes?
A portal keeps the rules for people to look up. In Monobase, agents read them while they draft a brief, fill a template or generate an image, and your AI tools read the brand documents directly.
Can we take our data with us?
Yes. The design system exports as DTCG JSON and CSS, logo and font files download as a ZIP, and images from Media download as ZIP files. Your Figma masters stay in your Figma.
Who can see and change what?
Monobase has four roles, from owner to viewer. Owners and admins build the Brand System and the design system. Creators work from them in Create and Campaigns, and everyone in the workspace can read the visual identity and download its files.
Where is our data stored?
Database, app and agents run in Frankfurt. Owners can switch on EU‑only mode for AI models. The security page lists which models process what.




