← Back

Centri Design Ops Ecosystem

I built the workflow that carries a design change from Figma to code, for designers, engineers and AI agents.

  1. FigmaDesign sourceDesigners edit components and variables in the shared Figma library.
  2. NexusPluginThe Figma plugin. It publishes components (16 checks on each variant, then a version) and tokens (exported to GitHub).
  3. SupabaseRegistryThe registry. It keeps every version of each component: its changes, preview and the tokens it uses.
  4. SlackNotificationsEach release posts the component, its version and what changed.
  5. GitHubRepositoryNexus pushes the tokens here, where they build into CSS variables for the light and dark themes.
  6. VercelShowcaseDeploys the Showcase on each push. It reads the registry: live controls, tokens and version history.

*Click a box to read what it does.*Tap a box to read what it does.

01 · The challenge

No system between design and code

Centri’s design system began with version 2 of the platform. Until then there was none: Platform Core, Labs, Corporate and Academy were designed in separate files, and four problems kept showing up when those designs reached development.

02 · The approach

A design system, and the tools around it

I built the design system from scratch: one Figma library, with tokens for colour, type and spacing.

The key decision was what to publish. Each release records what a component is (its variants, properties and tokens), not how its layers are drawn. Every version stays on record, so anyone can see what changed and when.

03 · End to end

Follow one real change

  1. Step 1
    Fix it in Figma. In v1.0.0 the Checkbox’s check icon used control/indicator/content, the wrong colour. It now uses control/indicator/content-checked.
    Before and after, side by side. Before: the registry record of Checkbox v1.0.0, where the icon fill uses color/control/indicator/content. After: the Checkbox in Figma with the checked variant selected and its new control/indicator token among the selection colours. The changed parts are boxed in red.
    Before: v1.0.0. After: the fix in Figma.
  2. Step 2
    Nexus checks it. The component passes its checks, and Nexus suggests a patch: v1.0.1.
    The top of the Nexus panel for the Checkbox: the current version V1.0.0 and, under Version, patch v1.0.1 selected over minor and major; both are boxed in red.
    Nexus suggests v1.0.1.
  3. Step 3
    Publish. Supabase stores v1.0.1 with its changes and preview.
    The registry record of Checkbox v1.0.1, a patch: its change description, and for the checked variant the icon fill changed from color/control/indicator/content to color/control/indicator/content-checked, boxed in red.
    The v1.0.1 record.
  4. Step 4
    The team hears. Slack posts the component, its version and the release note.
    A Slack message from the design system app: Checkbox, version 1.0.1, a release note about the checked icon colour, a preview of every checkbox state, and buttons to view the changelog or open Figma.
    The Slack post.
  5. Step 5
    The Showcase updates. It reads the registry, so the Checkbox page shows v1.0.1 with its new token.
    The Checkbox page in the Showcase at v1.0.1, with every variant on the left and its anatomy on the right; the version and the icon fill token are boxed in red.
    The Showcase at v1.0.1.

04 · The linter

Checks before every release

The Nexus lint rule configuration: rules such as Broken Variables, Foreign Variables, Fill Color, Stroke Color, Effects, Text Style and Font Family, each with a one-line description and a switch, all turned on.
Each lint rule can be turned off for a team that doesn’t need it.

Nexus includes a linter. Before a component can publish, it runs 16 rules on each variant: every fill, stroke, effect, text style, spacing and radius must use a token, no variable can be broken or come from outside the system, and every component needs a description.

05 · Versioning

How Nexus picks a version

Nexus compares each release with the last one. It recognises 15 types of change, and the biggest one sets the version. The Checkbox fix changed one token, so it was a patch.

The database checks it too: it rejects a version whose number doesn’t match its changes.

06 · Variables

From Figma variables to JSON

Variables follow their own path to the code, and the registry keeps their history too.

  1. Step 1
    Pick what changed. In the Tokens tab, Nexus marks the collections that changed. It exports the Figma variables as JSON in the Design Tokens format, with a value for Dark and Light.
    The Tokens tab of Nexus: six variable collections, with responsive ticked and marked as changed (one change, boxed in red) and the others synced; below, 1 collection changed and 5 unchanged, and a Publish and Sync button.
    Nexus shows which collections changed.
  2. Step 2
    Push and record. Nexus pushes every collection in one commit to the Showcase repository, so aliases between collections still resolve. Supabase keeps a version of each release, with what it added, changed or removed.
    The changes per version table: each variable library release from 1.0.7 to 1.0.14 with the collections it touched and how many variables it added, changed and removed, and the total; the latest release, 1.0.14, is boxed in red.
    Every variable release, with what it changed.
  3. Step 3
    Export and build. A GitHub Action turns the JSON into CSS variables: light and dark, five brands, and a Tailwind theme.
    From Figma variable to JSON: the Figma variable action/primary/bg, with color/cosmos/200 for Dark and color/cosmos/900 for Light, becomes the JSON entry action.primary.bg whose $value points to tailwind.color.cosmos.200 for Dark and tailwind.color.cosmos.900 for Light. Both pairs of values are boxed in red.
    From Figma variable to JSON.

07 · AI agents

The same registry, read by agents

The Centri MCP server’s 37 tools in five groups: design system registry (17), token versions (5), tokens (4), Figma (4) and code repository (7).
The 37 tools agents use to read and update the system.

An MCP server gives AI agents 37 tools to read and update the system: components, versions, token usage and orphan tokens. They answer from the same registry the Showcase reads.

08 · Outcome

What changed for the team

Design changes used to take days to reach the code. Now tokens reach it almost immediately. Here’s what changed in the team’s daily work.

The design team spends less time checking which version shipped.

09 · What I would change

What I’d build differently