A Figma plugin for design systems

A design system that can't drift.

Pick a palette, a font, an icon set — Compos builds the token foundation, locks every component to it, and exports ready-to-use code for your platform.

JR
KL
MT
AS
DW
Designers already testing Compos
★★★★★
Figma — Variables
bg/surface/primary#6D28D9
text/content/warning#F2B155
spacing/416
radius/28
tokens.css — generated
:root {
--bg-surface-primary: #6D28D9;
--text-content-warning: #F2B155;
--spacing-4: 16px;
--radius-2: 8px;
}
The problem

Your design system is only as good as its weakest hardcoded value

Design systems don't fail all at once. They fail one eyedropper click at a time — and nothing in Figma tells you it's happening.

01

New designers reach for the eyedropper

Nobody hands a new hire the chain from raw value → token → component — so picking by eye feels like the only option.

02

Old screens don't hear about updates

The brand color changes, the spacing scale changes — and every screen built with hardcoded values quietly falls out of sync, forever.

03

Nobody catches it until review

There's no signal for "this doesn't match the system" — drift stays invisible until a review, or a customer, catches it.

04

Developers re-type the whole system by hand

Once a screen ships, someone still reads every value out of Figma and manually retypes it as code — once per platform, every time.

How Compos thinks about a design system

Three layers. Nothing is allowed to skip one.

1

Primitives

The raw palette. color/500, spacing/4, radius/8. Nobody touches this layer directly.

2

Semantic tokens

The same values, renamed by what they mean. bg/surface/primary, text/content/secondary. This is the layer designers actually work in, every day.

3

Components & templates

Buttons, cards, whole screens. Every property here binds to a Layer 2 token — never straight to a raw value, never a hardcoded hex.

Features

Everything a junior designer needs to use the system correctly

Live

Foundation Scaffold

Pick a palette, font, and icon set — Compos generates the full color, spacing, type, and grid foundation in seconds.

Live

Pattern & Template Library

41 components, 12 patterns, and 21 full screens — login, dashboard, pricing, booking, settings — already wired to the correct tokens. Drag in and use.

Live

Multi-platform Code Export

Export the same tokens to CSS, Tailwind, Swift, Kotlin, React Native, Flutter, JSON, or Figma Code Connect — one source of truth, any platform.

Live

Documentation Export

Read variables from any file — Compos-built or not — into a self-contained HTML styleguide, ready to share or use as a benchmark.

Live

Foundation-wide Sync

Change a brand color or spacing scale once — every screen built with Compos updates with it, because nothing was ever hardcoded.

Export

One export, every platform

CSS is one of 11 — Compos also exports to
CSS Variables
Tailwind
shadcn/ui
SCSS
Swift / iOS
Kotlin / Android
React Native
Flutter
JSON
Figma Code Connect
HTML
Live demo — no install required

Pick a foundation, get real tokens back

The exact same color math the plugin uses — OKLCH ramps, WCAG contrast, five derivation schemes — right in your browser.

Works on any file — not just ones Compos built

Turn your design system into a shareable styleguide, in one click

Read every Color, Typography, Spacing, Icon, Grid, and Motion variable in a file — Compos-built or not — into one self-contained HTML page.

Your file
Color — 42 variablesany collection
Typography — 9 styles4 breakpoints
Spacing & Radiusresolved
Icons & Gridresolved
Components on pagedocumented
compos-styleguide.html
<nav>
  Color · Hex Color
  Typography · Font Scale
  Spacing · Radius
  Icons · Grid & Layout
  Motion
  Components
</nav>
/* self-contained — no build step, 
   host anywhere or just share the file */
Testimonials

Loved by design system teams

See what designers and developers are saying

★★★★★

"We used to spend hours hand-creating variables for every new file. Compos scaffolds the whole foundation in seconds, and nobody reaches for the eyedropper anymore."

JR
Jordan Reyes
Lead Designer, TechFlow
★★★★★

"The code export is a game changer. Every token comes out as clean CSS Variables, already matching what design built — no more re-typing hex codes by hand."

KL
Kim Larsson
Frontend Engineer, Nordbank
★★★★★

"We manage a system with 300+ tokens across three platforms. Foundation-wide Sync means changing one color updates every screen — nothing drifts anymore."

MT
Maria Torres
Design Systems Lead, Finova
Pricing

Two plans — free to start, unlimited when you're ready

Planned pricing for when Compos opens up — nothing to pay today. Reserve a plan and lock in the price.

Monthly
Annually Save 25%
Free
$0/month
Forever — no time limit
  • 10 lifetime actions, full feature access — Foundation, Components, Patterns & Templates, Add Brand, Guided Picker, every export format
  • Auto-fix Linter, unlimited
  • 1-click 7-day free trial after that — unlimited actions, no card required
  • Personal use, single file at a time
  • Community support
Start Free

Free forever for personal use — 10 lifetime actions with every feature unlocked, plus a 1-click 7-day free trial for unlimited actions when you need more room. Pro removes the cap for good — no trial required.

FAQ

Frequently asked questions

Is Compos available now?+
It's an early-stage Figma plugin, built and tested against the real Figma Plugin API — not yet published to the Figma Community. Early access sign-ups get first access as it opens up.
Do I need to know how to code to use it?+
No. The Foundation, component library, and templates are all designer-facing — no code required. Code export is there for when a developer on your team needs it.
Will it mess with a design system I already have?+
Compos scaffolds a fresh Foundation inside a file — using it to build new components requires that. Reading and documenting an existing system's variables (the Documentation Export) already works on any file, Compos-built or not; importing an existing token set as the Foundation itself is on the roadmap rather than available today.
What platforms does the code export support?+
CSS Variables, Tailwind, shadcn/ui, SCSS, Swift/SwiftUI, Kotlin/Jetpack Compose, React Native, Flutter, W3C-style JSON, Figma Code Connect, and HTML documentation — 11 formats, all available on Free within your 10 lifetime actions.
Does it require a paid Figma plan?+
Compos uses Figma's standard Variables API — the same one used by any file with variables. Multiple Variable Modes beyond one per collection need a Figma plan that includes them, same as anywhere else in Figma.
How is this different from other token plugins?+
Most token plugins stop at managing variables. Compos also generates the components bound to them, exports straight to platform code, and can document any file's variables as a shareable HTML styleguide — so the token layer, the component layer, and the documentation never drift apart from each other.

Ready to scaffold a design system that can't drift?

Free forever — 10 lifetime actions included, no credit card required.