White paper · Design · August 2026

The Prototype Is the Handoff

How a governed design canon, read by Claude, replaced the Figma prototype-and-handoff process.

Inside this paper

  • The problemFive roles, four forms, and a drift at every boundary.
  • The canon as source of truth21 governed documents Claude reads as a contract.
  • The revised processFive steps, none of them a rebuild.
  • What changedThree steps gone, and what still needs a person.
3

Three steps did not get faster. They stopped existing. The design QA alignment pass, the Dev Mode rebuild, and the annotation layer. What remains is the business review, the designer's judgment, and the development work: the steps that require people.Career Highways design practice, August 2026.

The problem

A request from the business became a Figma prototype, built from a mature component library. It went through several rounds of stakeholder review, then to a design QA reviewer who checked every screen against the system and annotated the file, then to a front-end developer who read the values through Figma Dev Mode and rebuilt the design in code. At every boundary the design was described again: as a drawing, as annotations, as copied style values, as code. Each description was a chance for it to drift.

The design process, before and after

Before
  1. Business request
  2. Alignment discussion
  3. Figma prototype, built from the Design Framework
  4. Stakeholder review rounds
  5. Design QA review and Figma annotationsRemoved
  6. Dev Mode handoffRemoved
  7. Front-end rebuild in codeRemoved
  8. Back-end questions on unclear data
  9. Full development and push release
After
  1. Business request
  2. Brief to Claude
  3. Canon-built prototype: the correct shell, canon tokens, computed contrast, and an accessibility gate run to zero violations
  4. Designer fine-tune with Claude
  5. Business review rounds
  6. Approval
  7. Design package
  8. Full development and push release
Our design decisions were not written anywhere they could be checked. The design system was amended by written commentary that nothing enforced.

The canon as the source of truth

The design system was capable. Its limit was structural: it lived in Figma, so its rules could be read by a designer but not enforced by anything downstream. We rewrote it as a design canon, a set of versioned documents, each with an owner and a review cycle, that a designer reads as documentation and Claude reads as a contract. Alongside it sits a Component Showcase, which Claude treats as the ground truth for how every element should look and behave.

What Claude reads: 21 governed documents in five families

DSF · 2

Foundations

Foundations and the accessibility floor.

DST · 4

Tokens

Color, typography, sizing, iconography.

DSC · 11

Components

Eleven component contracts.

DSP · 3

Patterns

Layouts, rich-text tiers, the build workflow.

DSM · 1

Marketing

The marketing extension.

Document families and counts as read on 2026-08-03.

A style guide describes what good looks like. A contract states what will be rejected, and only the second can be checked by something other than a person.

The revised process

Claude reads the canon in full and assembles the screen from a brief, starting from the correct shell and verifying the result before anything is presented: contrast ratios computed, an accessibility gate run to zero violations. The designer refines it with Claude, the business reviews it, and an approved design goes to development as a design package that is already markup, built from the same tokens the product uses.

01 Brief to Claude 02 Canon-built prototype 03 Designer fine-tune 04 Business review 05 Design package

What changed

01

The design QA alignment pass

Every prototype is built from the design system rather than checked against it afterward.

02

The Dev Mode rebuild

There is no drawing to transcribe. The design package is already markup.

03

The annotation layer

A canon correction is a versioned change to a governed document, not a comment on a frame.

Accessibility became evidence rather than assertion, and corrections compound: a rule written once applies to every screen built afterward. The full paper covers the limits too. The canon now sits on the critical path, and Claude follows what is written and nothing more.

Read the full paper

The complete paper: the full before-and-after process, why the Figma process had a ceiling, the canon and its working layer, the build workflow excerpt, what changed, the limits, and the sources.

Related

Explainer

Design

Tokens and component contracts govern the generated screen, so the design system stops being a suggestion.