Context · Design system

One design system
for every touchpoint.

The Monobase Design System, complete for product and marketing. Import your Figma design system, and your team and agents share the same design tokens.

One token set

From your Figma design systemto released tokens.

  • Change one token at a time. Edit a cell in the library or ask the agent. You see the token before and after, with the lint result, and the change waits as a draft.

  • Review before you merge. The audit ranks what breaks the methodology. An owner or admin reviews each draft, sees what the audit finds new, and merges it.

  • Release versions you can compare. Seal a release with its files and compare it with the one before. Developers export DTCG, CSS or the whole document as JSON.

  • Ask the agent, not the file. Ask the design system agent what your button radius is on Web. It answers from the tokens and names the one it read.

Agents

The agent that knows your tokens. It proposes. A person merges.

All agents

Questions about the design system

Is it a full design system or a light version?

A full one. The Monobase Design System holds tokens for Global and each touchpoint (Web, App, Social, Email, Display, Print), components with their documentation, patterns, an audit against the methodology, reviewed drafts and sealed releases. Bring yours in from your product’s Figma, a website’s CSS variables or a DTCG file, and marketing and product work from one system.

How do we bring in our Figma design system?

Through the Monobase Bridge plugin, which reads your Figma variables and styles. Tokens can also come from a public website’s CSS variables or a DTCG token file. Each import shows a preview of what maps and what does not, and saves nothing until you confirm. You can also build the design system from your visual identity.

Does it write back to Figma?

No. Monobase reads from your Figma file; changes made in Monobase are not pushed back to it.

Can we export our design tokens?

Yes. Pick the touchpoints and download DTCG as a ZIP with a resolver per touchpoint, CSS variables, or the whole document as JSON, components and profiles included.

How do touchpoints differ from Global?

Global holds the brand’s colours, gradients, type and motion. Each touchpoint, Web, App, Social, Email, Display or Print, takes those values and adds its own sizes, spacing, shapes, text styles and formats. It never overrides Global.

Can we add a touchpoint later?

Yes. Add Email, Display or Print when you need them. The methodology builds each one on Global and hands it to you as one proposal.

Who approves changes?

Owners and admins. An edit in a library table or an agent’s proposal is saved as a draft; a person reviews it and merges it, optionally after one or two other owners or admins approve. Creators and viewers read everything.

What does the audit check?

Your design system against the methodology: naming, the grid, contrast, roles and touchpoint conventions. It ranks findings by severity and library, shows coverage, and can prepare a repair as a draft for review.