Flash DSM - The design genome your agents build from.

Compose your foundations. Every component and module follows. The Design Genome knows where each one lives, and what moves when it changes.

Skip the canvas, start with the system

Figma - and every canvas-first tool - was built to draw pictures of a design system, not build one. You paint first, then reverse-engineer a system underneath, and ship code that never quite matches. Flash flips it: build the system first, and go straight to code that's actually accurate. And because the system is machine-readable, it doubles as guardrails for anything your AI tools generate.

How it works

Give Flash a brief, a URL, or a Figma file and it cuts the pattern for you: full color scales in both themes, a type pair, spacing, radii, motion, and components that reference them. That is the starting point, not the product. The product is what you make of it in the editor.

Describe it

Type a prompt, paste a live URL, or connect a Figma file. Flash extracts the design DNA either way.

Flash builds it

Flash bootstraps full token scales - colors in light and dark, a type pair, spacing, radii, shadows, motion - and you edit them in place. Swap the font, retune a scale, kill the choices you disagree with.

Ship it

Export CSS variables, a Tailwind config, or Tokens Studio JSON. Push straight to GitHub.

What the pipeline produces

  • Extracting brand DNA
  • Building color scales
  • Pairing typography
  • Shaping spacing & radii
  • Tuning motion & effects
  • Mapping components

+ 8–14 domain-specific components, mapped to tokens

Structure and style are separate layers

A tailor's pattern holds the fit and the seams. It never holds the color of the cloth. That split is what lets one system dress a whole company.

Structure is the part that should not vary: what a card is built from, how a button spaces its label, which states exist. Flash keeps it in one place, so every product cuts from the same shape.

Color, type, radius, motion. A theme sits on top of the structure and swaps without touching it, so one team can look nothing like the next and still share every component.

Ship a component that is also one specific blue, and the next team says that is not our blue and writes its own. Two months later you maintain two systems. Keeping the cloth separate is what prevents it.

Does a design system flatten the work?

It settles the parts nobody should be re-deciding, which is what leaves room for the parts only you would have made.

Flash doesn't hand you a template. Foundations, components and modules - all built to fit your brand, not the other way around.

The first quotes are in.

Everything below was actually said, by a real person who agreed to see it published here.

"The Figma killer." - Name withheld "I wish I had this six months ago when I was building our design system. This is insane." - Name withheld "This is so useful. I’m going to fly with this. It saves me so much time working with developers." - Name withheld "Now I can finally work with Claude Code while keeping everything consistent, without it making things up." - Name withheld "After researching dozens of design systems, I realized we shouldn’t have to rebuild the same foundations every single time." - Itay Haephrati, Founder, Flash DSM "I spent days setting this stuff up manually. Flash DSM does the part nobody wants to do." - Name withheld "This is what design system tooling should look like in 2026." - Name withheld "I gave it our system and suddenly Claude stopped inventing random styles." - Name withheld "Designers get consistency. Developers get usable code. That’s the whole problem right there." - Name withheld "This would have saved me an unbelievable amount of time on my last project." - Name withheld "I can see our team using this every time we start a new product." - Name withheld "The gap between Figma and production just got much smaller." - Name withheld

No customer logos yet.

Flash is new, and quotes are easy to collect. Here are three things you can check yourself before you pay for anything.

Every system on this page is public. Open one, read the tokens it produced, fork it into your own account and take it apart. None of it is a screenshot.

Exports are tokens.css, a Tailwind config and Tokens Studio JSON: plain files you could have written by hand. They keep working whether or not we do.

Every fix and every feature is written down with the day it shipped. If the work slows down, you will see it here before anyone tells you.

Frequently asked questions

What is Flash?

Flash is a design-system builder. From a prompt, a live URL, or a Figma file, it bootstraps a complete token architecture - color scales in light and dark, typography pairs, spacing, radii, shadows, motion - plus domain-specific components mapped to those tokens. You edit, then export CSS, Tailwind, Tokens Studio JSON, or push to GitHub.

Why do AI builders need a design system?

Tools like Lovable, v0, and Bolt generate screens fast, but every new prompt invents its own colors and spacing unless something pins them down. A design system is that rules layer: hand these tools machine-readable tokens and the output stays on-brand, keeps accessible contrast, and matches the code you already shipped. Flash builds the layer and serves it in the formats they actually read - kit.md, token files, and MCP.

Who is Flash for?

Design engineers - solo or in teams - who own UI quality but don't have time to police a design system. Also built for fast-moving dev teams who need a system that keeps up with how fast they ship.

Is Flash free to use?

Yes, to start. Every account builds one Genome, meaning one design system and everything that reads from it, free and with no card required. Pro, Team and Studio add module pulls, update sync, a shared Genome and client handoff - see the Pricing page for what sits where.

Can I import my existing designs?

Connect a Figma file, paste any live website URL, or pull from GitHub and Storybook. Flash extracts the existing design DNA and turns it into structured, editable tokens.

Does Flash stay in sync with Figma and my code?

Here's what's real today: import from Figma, a URL, or a codebase; export CSS, Tailwind, and Tokens Studio JSON; push to GitHub; send variables to Figma through the Flash plugin. Deeper two-way sync - changes flowing back automatically from code and Figma - is rolling out, and we'd rather under-promise it than pretend it's done.

What can I export?

Production-ready formats: tokens.css with CSS custom properties, a tailwind.config.js extension, Tokens Studio JSON that round-trips with Figma, and component specs. You can also push directly to GitHub.

Does it generate real, usable code?

The exports are the same CSS variables and Tailwind tokens you'd write by hand, ready to drop into your codebase. No proprietary runtime, no lock-in.

How is Flash different from AI UI generators?

Screen generators give you mockups. Flash gives you the system underneath them: consistent scales, semantic tokens, both color modes and components that reference tokens instead of hard-coded values - so everything you build afterwards stays consistent.

Do I own what Flash generates?

Completely. Every token, component spec and export belongs to you - use it in client work, commercial products, or your own design tools.