Spektral
The handoff is where design systems break
I've spent a decade inside enterprise design systems, leading Pfizer's Helix system and working on the design systems of some of America's largest companies with Big Medium. Every one of them hit the same wall.
A designer draws a component. An engineer rebuilds it by hand. The two versions drift apart, accessibility problems turn up in QA, and new components queue behind one or two busy engineers. Eventually product teams stop waiting and build their own, and the system stops being the source of truth it was meant to be.
AI tools promised to help, but most of them generate code nobody can trust: plausible-looking, off-brand and untested. That just moves the rebuild somewhere else.
What changes with Spektral
Designers ship, not just spec
What a designer makes in Spektral is the component itself, not a picture of it. Engineers pick up working code in React, Vue, Lit or Svelte, so nothing is lost in translation.
Components in days, not sprints
A new component goes from idea to reviewed, working code in an afternoon. The system keeps up with product teams, so they use it instead of working around it.
Accessibility is built in, not audited later
Every state of every component is checked for accessibility, including colour contrast, before anyone is asked to review it. Problems are fixed while the component is being made, not months later in an audit.
One system that people and AI both build from
Every change is reviewed and every release is versioned. Product teams install what's published, and AI coding tools like Claude Code and Cursor read the same system, so AI-written product code uses the real components instead of inventing new ones.
Start with the system you already have
Spektral opens an existing component library where it already lives and connects to Figma on any plan. There's no migration project; teams improve their system one component at a time.
How I made AI output trustworthy
The value only holds if teams trust what the AI produces, so that's where most of the engineering went.
- The AI checks its own work. Spektral's agent writes code, edits tokens, validates CSS and runs accessibility tests, and keeps going until every check passes. It works inside the system's design tokens rather than inventing values.
- Nothing ships without review. Changes go through branches and approvals, just like code, and releases are packaged per framework so product teams can pin a version.
- Teams can work at the same time. When two people change the same component, Spektral re-applies one person's change on top of the other's, instead of handing a designer a merge conflict.
- It passes an enterprise security review. It's a desktop app with API keys kept away from the interface, hosted AI runs through Azure, and it supports single sign-on and on-premises deployment.
Where it is now
Spektral is in public beta, with around 90 beta sign-ups, mostly from organisations, and active use at Pfizer. The current version has shipped over 40 releases since February 2026.
What this means for your project
If your design system can't keep up with your product teams, or you're working out how AI should fit into the way your designers and engineers work, I've already solved those problems in production. I can help you adopt Spektral, or bring the same thinking to your own tools and workflows.
Visit spektral.design or get in touch to talk about your project.