---
title: Build feature UI from a spec
description: Give the agent your spec and your components, and get a real screen on your system, in vectors you can take over. Step by step.
section: solutions
order: 6
featured: false
related: solutions/product-managers, solutions/ship-to-code, editor/components
---

# Build feature UI from a spec

How do I get the fifth variant of a settings panel without laying it out by hand? Give the agent the spec and the context. It builds with the components and tokens already in your project, and what lands is vectors, with full undo.

<DocFigure src="/docs/images/solutions/build-feature-ui-scene.webp" srcMobile="/docs/images/solutions/build-feature-ui-scene-390.webp" stage="panel" alt="A feature screen built from the project components" caption="Your components, your tokens, real vectors." />

## How do I build a feature with the agent?

Four steps, from spec to something you own.

<DocStep n="1" title="Give it the spec and the context.">

Press <KeybindingDisplay keyCode="/" size="small" /> and describe the surface. Click a frame first so "make this the empty state" is unambiguous, type @ to attach an element by name, and paste a screenshot when the spec is a picture.

</DocStep>

<DocStep n="2" title="Let it build on your system.">

With a design system active, every color, size and font slot resolves through it. Instances stay linked to their master, and a component set covers states: flip a dropdown and the instance re-renders as that variant.

</DocStep>

<DocStep n="3" title="Let it check its own work.">

Each line is validated, run, then linted on the real geometry. Each problem comes back with a stable code, a plain sentence and a fix, plus a render, and the agent usually corrects it in the same turn.

</DocStep>

<DocStep n="4" title="Take over.">

Everything is a native element. Each chat keeps its own undo, so you can hand-edit while it runs and roll back only its turn with Revert. If a change belongs to everyone, Push Overrides to Master sends it up.

</DocStep>

<DocFigure src="/docs/images/solutions/build-feature-ui-lint.webp" srcMobile="/docs/images/solutions/build-feature-ui-lint-390.webp" stage="panel" alt="The quality linter reporting a problem with a suggested fix" caption="Problems come back with a code and a fix." />

## Can it find things across my project?

Yes. It searches canvases by name, text, type, color or component, so "match the empty state on the Settings canvas" just works. Masters can live on another canvas from their instances, and that is the usual setup.

## Common questions

### Will it invent new styles?

Tell it not to: "use our CartRow and our tokens, no new styles." Agents work from the catalog they are given.

### What if I want to change which master an instance uses?

Detach it and make a fresh one, or flip its properties when both variants live in one component set. See [Components](/docs/editor/components).

## Where next?

- Follow a full build: [Design tutorials](/docs/ai/design-tutorials).
- Masters, instances and sets: [Components](/docs/editor/components).
- Bind it to your tokens: [Design system overview](/docs/design-system/overview).
- What the checks catch: [Quality linter](/docs/developers/quality-linter).
- Take it to production: [Ship to code](/docs/solutions/ship-to-code).
