AI design system

Ask for a screen, and it comes in your own design system

An AI design system is your tokens, components and rules written so an AI can apply them, not only so a person can read them. In Epic Context the design system is part of the brain: an agent reads the component specs and rules before it builds, and a developer skill generated from your system checks the result.

The ask

Ask for a screen, and it starts from yours.

An AI that has not read your design system draws the average screen: a generic gradient, fields with a placeholder and no label, someone else's spacing. One that has read it starts from your components and your rules.

  1. The ask

    Design the sign-up screen for the new app.

  2. It reads first

    • DesignComponent specs
    • DesignDesign tokens
    • DesignDesign rules
    • UsersPersona and first job
    • BuildTech stack
    • BuildDecisions
  3. It works as

    The Design expert

    • A label above every field, never a placeholder alone
    • The persona's first job comes first
  4. What comes back

    A sign-up screen in your own system

    • Built by Claude Code on your stack, with your components
    • Checked against the design rules before review
    • The page and its components recorded in the brain
An illustrationHow a design task runs. Not a client's screen.

The design system as a brandbook

Your design system, as a brandbook an AI can read.

In Epic Context the design system is part of the brain, in five chapters: Foundations, Brand assets, Components, Guidelines and Applications. Every component spec carries its anatomy and specs: its parts, the tokens each part uses, and the rules for using it.

People read it as a book. Agents read the same blocks before they build.

A skill from your own system

A developer skill generated from your design system.

  • Rules, and do's and don'ts, from your design guidelines.
  • Token sources, never values, so the code points at your tokens instead of copying them.
  • A lint for literal colours and sizes, so a one-off hex or px value is caught before review.

Judged like a designer would

Every design round measures before it judges.

Design tasks run through the Design expert. It measures before it judges (sizes, contrast and spacing at phone, tablet and desktop widths), checks the craft floor for usability and accessibility, and says no with a principle, never with taste.

Where it stops

Figma stays Figma. The system is yours to decide.

Epic Context is not a design tool. Your designers keep designing in Figma; context cards bring the brain's facts into Figma, FigJam and Miro beside the work. What goes into the system, and when it changes, is your team's decision.

Questions

What is an AI design system?

An AI design system is your tokens, components and rules written so an AI can apply them, not only so a person can read them: each component with its parts, the tokens it uses and when to use it. The AI reads it before it builds, and a check catches what it got wrong.

Can AI design in our design system?

Yes, when it reads the system first. In Epic Context a design task gets a briefing with your component specs, tokens and rules, and the Design expert checks the result against them before review.

Does it work with Figma?

Yes, beside it. Designers keep working in Figma; context cards bring the brain's facts into Figma, FigJam and Miro. Editing the design stays in Figma.

How do developers use it?

Through their coding agent. Claude Code or Cursor reads the component specs and rules over MCP before it builds, and the developer design skill generated from your system lints the result for literal colours and sizes.

Who maintains the system?

Your team. A change to the design system is a write with a reason and an owner, visible in the changes feed. Epic Stories helps you set it up.

Start with one real project

Epic Stories installs Epic Context with your team, on your own work, and then steps back. Tell us where you would start.