Pick a color, a type ratio and a spacing unit. RatioDS builds the whole design system around them and ships it to Figma as native Variables, or straight to code.
Brand palette
187 tokens, aliased end to end.
Type scale
This is the real generator. Change the color, the ratio or the base size.
The problem
0.00 : 1
White text on your step 500 reaches 3.92:1. WCAG AA asks for 4.5:1, and nobody checked.
Flipping a light theme is not a dark mode. Every surface, border and text needs its own decision.
One name in the file, another in the code. Nobody knows which one is true.
Rebuilding scales, roles and components by hand is where the time goes.
A design system is a language. Raw values are its vocabulary, semantic roles its grammar, and components the sentences you write with them. RatioDS keeps the three connected, so changing a word changes every sentence that uses it.
A vocabulary
raw values
A grammar
semantic roles
Sentences
components
Three choices
One color
Eleven OKLCH steps with matched lightness and chroma, so step 500 reads the same whether the base is violet or gold.
One type scale
A real ratio: every size from caption to display follows it, down to the exact rem. (1.333)
One unit
Spacing, padding and gaps on the same grid. Change the unit and every component breathes with it. (4px)
Components
From Button to Command palette, in seven categories. Every fill, stroke, radius and padding comes from a semantic token, never from a raw value.
Headers, heroes, pricing, testimonials and footers, composed into whole pages in your system. Thirteen sections and three templates to start from.
A design system that stays connected to its source
Generate primitives, choose your semantic roles, and push all three tiers to Figma as real aliased variables.
Three tiers, one direction
A component token never reaches past semantic into a raw value. That indirection is the whole product.
Primitives
OKLCH ramps generated from one seed colour, perceptually even at every step.
Semantic
UI roles that alias primitives, so repointing one token re-skins everything downstream.
Components
Fifty specimens painting themselves live from whatever your semantic layer says today.
“We repointed one brand token and every button, badge and focus ring in the file moved with it. That used to be a week.”
Push your system to Figma
Three collections, aliased end to end, with Light and Dark modes from the first run.
The RatioDS Token Importer writes your whole system into the file. Free on Figma Community.
CSS custom properties, a Tailwind config or a JS object, written from the same source as the Figma file. This one is generated from your choices above.
:root {
--color-primary-50: #f6f5fe;
--color-primary-100: #e9e5fd;
--color-primary-300: #c3b4ff;
--color-primary-500: #9063fa;
--color-primary-600: #7c3aed;
--color-primary-700: #6d24d9;
--color-primary-900: #482a87;
--font-size-sm: 0.875rem;
--font-size-base: 1rem;
--font-size-lg: 1.333rem;
--font-size-xl: 1.777rem;
--font-size-2xl: 2.369rem;
--font-size-3xl: 3.157rem;
--space-0.5: 2px;
--space-1: 4px;
--space-1.5: 6px;
--space-2: 8px;
--space-2.5: 10px;
--space-3: 12px;
}Sign up and pick a color
A free account keeps every system you make, on any device.
Refine it in one workbench
Foundation, semantic roles, components, sections and templates, side by side.
Ship it
Native Variables for design, CSS, Tailwind or JS for code, from the same source.
RatioDS is a design system generator. You choose a brand color, a type ratio and a base size, and it builds the whole system around them: OKLCH color scales, semantic tokens with Light and Dark modes, a type scale, spacing, radius, 50 components, sections and templates. Then it ships it to Figma as native Variables and component sets, or to code.
Stop drawing the foundations by hand. RatioDS derives every token from three choices, keeps primitives, semantic roles and components connected, and the free Figma plugin imports everything in one run. Change a value, import again, and every component that uses it updates.
Yes. Five collections aliased end to end (Primitive, Brand, Semantic, Typography, Component) with Light and Dark modes, text and effect styles, documentation artboards and all 50 components as component sets bound to those Variables.
A design system treated as a language: raw values are the vocabulary, semantic roles are the grammar and components are the sentences. Keeping the three layers connected is what lets one change travel through the whole product, and it is how RatioDS is built.
Every step of every scale carries its contrast ratio with white and black text, and semantic roles pick pairs that pass WCAG AA in both Light and Dark.
Yes: CSS custom properties, a Tailwind config, DTCG JSON, JS or TypeScript, and a Markdown design-system document your AI coding tools can read, all from the same source as the Figma file.
A UI kit is a fixed file you adapt by hand. RatioDS generates the system from your own choices, checks contrast on every pair and regenerates it whenever you change your mind.
Yes, with a free account (email or Google): the generator, the 50 components, the Figma plugin and the code export. Pro, with multi-brand theming and the Pro sections and templates, is coming soon.
Start from colors, typography and spacing. RatioDS builds the foundations of your design system, ready to use in Figma or in code.