---
title: Ship it into the codebase
description: Let your coding agent read the canvas directly, or export the selection as HTML, React, SVG or CSS. Two routes, one design.
section: solutions
order: 10
featured: false
related: solutions/design-engineers, workspace/import-and-export, solutions/framer
---

# Ship it into the codebase

How do I get a design into my codebase without a handoff document? Two routes. Your coding agent reads the canvas directly over a local MCP server, or you export the selection as HTML, React JSX, SVG, PDF or CSS. Most people use both.

<DocFigure src="/docs/images/solutions/ship-to-code-scene.webp" srcMobile="/docs/images/solutions/ship-to-code-scene-390.webp" stage="panel" alt="An agent turning a design into code" caption="Hand the design to your agent, in your stack." />

## How does my agent read the design?

Connect it once, then the prompt is the handoff. Claude Code, Cursor, Codex, Copilot, Windsurf and Antigravity connect with one toggle, and canvas work is unlimited on every plan. See [Connect your agent](/docs/agents/overview).

> Build the settings panel from the Dashboard canvas in our React components. Match the spacing and type.

This route adapts to your stack: the agent knows your repo, so it writes your components. It runs the other way too: a component you changed in code can land back on the canvas.

## Which export should I use?

Pick by what you want to hold. The Export panel, and the right-click Export as and Copy as menus, cover all of these.

| You want | Take |
|---|---|
| Markup to adapt | HTML: snippet, full document or flex |
| A component for a .tsx file | React (JSX) |
| Icons and illustrations | SVG |
| Just the values | CSS properties |
| The design itself | Blueprint, pasteable back into Brilliant or into an AI tool |

Cmd+E exports a PNG for a ticket or a thread, and the + in the Export panel header adds another row, so several formats ship in one click.

<DocFigure src="/docs/images/solutions/ship-to-code-code.webp" srcMobile="/docs/images/solutions/ship-to-code-code-390.webp" stage="panel" alt="A design exported as code" caption="From the canvas to code you can keep." />

## How do tokens reach my code?

Brilliant writes Styles/.gen/default.gen.yaml on every save, expanded to concrete values. Style Dictionary, Tokens Studio plugins and build scripts read that file. See [Design system overview](/docs/design-system/overview).

## Can design changes go through code review?

Yes. A .bl file is plain, deterministic text: branch it, diff it, comment in a pull request, and git blame the line where a color drifted. A published project is also a git repository you can clone.

<DocFigure src="/docs/images/solutions/ship-to-code-blueprint.webp" srcMobile="/docs/images/solutions/ship-to-code-blueprint-390.webp" stage="panel" alt="A design beside the Blueprint text that describes it" caption="The canvas and the Blueprint text are the same design." />

## Common questions

### Is exported code production ready?

It is a starting point to adapt: it carries the look, and your app keeps its state, routing and data. For code in your own components, use your agent.

### Can my agent build a real prototype?

Yes. It reads the canvas and builds the flow in your stack.

## Where next?

- Every format: [Import and export](/docs/workspace/import-and-export).
- Connect your editor: [Connect your agent](/docs/agents/overview).
- The language your agent writes: [Blueprint language](/docs/developers/blueprint).
- One vocabulary across design and code: [Design system overview](/docs/design-system/overview).
- Check quality on the way: [Quality linter](/docs/developers/quality-linter).
