Do enterprise layers replace the standard AI Package?

No. Enterprise extensions sit on top of the standard AI Package. The core — tokens, components, guidelines, themes, and context — stays exactly the same; larger organisations simply add layers for governance, traceability, and AI orchestration.

Which enterprise layers exist?

Metadata, governance, indexes, rich component contracts, interconnections, agent instructions, decision logs, and quality checks. Each is optional and becomes valuable as organisational complexity increases.

When should a team add enterprise extensions?

Most teams only need the standard AI Package. Add layers when ownership spans many teams, when AI agents generate at scale, or when you need an audit trail for design decisions and quality.

Enterprise

Enterprise AI design systems.

The core package stays the same. Larger organisations simply add additional layers for governance, collaboration, traceability, and AI orchestration.

Explore the layers → What's in the standard package

Scroll to explore

The relationship

Start simple. Add complexity only when you need it.

Enterprise structures never replace the standard AI Package. They extend it — so the system you already trust keeps working while it gains the scaffolding a large organisation needs.

Standard

AI Package

Add when needed

Enterprise Extensions

Outcome

Enterprise AI Design System

Explore

The enterprise layers

Eight optional layers, each solving a specific problem that appears at scale. Select one to see why it exists, the files it adds, and a real example — then download a starter template.

Rich component contracts

From a sketch to a contract

A basic component spec tells an AI what something is. An enterprise contract tells it exactly how, when, and when not to use it — expand any row to see a real example.

Basic

card.md

Enough to render. Open to interpretation.

Purpose

A surface that groups related content
and actions into a single block.

Variants

default · elevated · outlined

Examples

<Card>
  <CardTitle>Plan</CardTitle>
  <CardBody>…</CardBody>
</Card>

Enterprise

card.md

A complete contract an agent can follow without guessing.

Purpose

A surface that groups related content and
actions. Not a layout primitive.

Use when

• Summarising one entity (a plan, a person)
• Offering 1–2 primary actions
• Items belong on a browsable grid

Avoid when

• Rendering dense, scannable data → use Table
• Nesting cards more than one level deep
• A single value would do → use a Stat

Variants

default · elevated · outlined · interactive

Accessibility

• Interactive cards expose a single focusable
  control; whole card is the hit target
• Title uses a heading level, not bold text
• Contrast: text on surface ≥ 4.5:1

Dependencies

tokens: spacing-md, radius-lg, shadow-sm
components: Button, Badge

Related components

Stat · Tile · Panel · ListItem

Examples

<Card variant="interactive">
  <CardTitle>Plan</CardTitle>
  <CardBody>…</CardBody>
  <Button>Choose</Button>
</Card>

AI instructions

# for the assistant
Prefer the existing Card over a new surface.
Never place a data table inside a Card.
Use spacing-md for internal padding.

Interconnections

Everything relates to everything

The real system isn't a folder of files — it's a graph. Select a node to see what flows into it and what depends on it.

Architecture

Enterprise AI Package architecture

The standard package on top; the enterprise layers below. Same root, more scaffolding.

ai-package/

Resource library

Starter templates

Real, editable markdown to drop into your package and adapt. Nothing to sign up for — just download and make it yours.

Most teams only need the standard AI Package.

Enterprise layers become valuable as organisational complexity increases. Reach for them when you feel the pain — not before.

Start with the AI Package → See how it works