Boardbox
Get access

Design

Screens drawn from your own design system.

Design Studio reads the tokens, assets and fonts in your code and draws pages, flows and boards that look like your product, in light and dark. You approve one exact version, and that version is the only one that gets built.

Watch one launchRequest early access

How it works

  1. 1

    Bring your system

    Extract tokens from your codebase or an import, and copy your real assets and fonts into the workspace.

  2. 2

    Brief it

    Describe the screen or flow, or let an Initiative send a design request. It may ask you one short form before it starts.

  3. 3

    Review the canvas

    Pages, flows and boards render on the canvas in light and dark, already checked for contrast, tap targets and overflow.

  4. 4

    Approve one version

    Approval freezes that exact version as the handoff a Build implements.

Your system

Your tokens and assets

Design Studio proposes a design system from your codebase or an import, with the official values beside what it found in code, so new screens use your colors, type and spacing.

  • Tokens extracted from your source, reviewed before they become official
  • Your real app assets and fonts, copied from your repo
  • Light and dark themes on the same canvas

Checked

Reviewed before it reaches you

The author renders every draft and reviews it itself, with deterministic checks for common layout mistakes.

  • Contrast, tap-target size, overflow and clipped text
  • Checked against the brief and your company’s rules
  • Each page is reviewed in light and dark

Handoff

One exact version, approved

Approval pins a specific version and its content. A Build in an Initiative will not start until the design it depends on has been approved, and a later edit needs a new approval.

  • Handoffs freeze their source, so later edits never rewrite them
  • Page history lets you make any saved version current
  • Export artboards as PNG at 1×, 2× or 3×

Where it stops for you

Runs on its own

  • Drafts pages, flows and boards from the brief
  • Renders and reviews every draft
  • Fixes failed checks before showing you
  • Asks one structured question when the brief is unclear

Waits for you

  • Adopting extracted tokens as your official system
  • Approving the exact version a Build implements
  • A new approval after any later edit

What it works with

Reads

  • Your codebase
  • Design tokens and themes
  • App assets and fonts
  • Reference images
  • Claude Design exports
  • Library

Produces

  • Pages and flows
  • Boards with notes and connections
  • Versioned handoffs
  • PNG exports

Where founders use it

A new feature

An Initiative requests the screens, you approve one version, and the Build implements exactly that.

A user flow

Lay out every step of onboarding on one board, with branches, captions and labeled connections.

Bringing old work in

Import Claude Design exports as editable pages so earlier work joins the same system.

How it compares with a general AI design tool

Starting pointAI design tool: A generic style you restyle afterward.Boardbox: The tokens, assets and fonts already in your code.
Quality checksAI design tool: You catch contrast and overflow problems yourself.Boardbox: Every draft is rendered and checked before you see it.
HandoffAI design tool: A link to a file that keeps changing.Boardbox: One frozen version a Build is required to implement.
ContextAI design tool: A prompt box.Boardbox: Your company, your product and the plan the design serves.

In the Tablebird launch

The screens come back into the conversation.

Design Studio draws the group dashboard from Tablebird’s own components, checked against the rule that managers only see their own locations. Ava approves one exact version, and that version is the one that gets built.

Follow the whole launch

What people ask

Do I need a design system first?
No. Design Studio extracts one from your codebase and shows it to you for review before it becomes official.
How do I change a design?
Ask for the change in the conversation. It becomes a new version in the page history, and any earlier version can be made current again.
Can it design mobile apps?
Yes. It can also inspect your iOS app in the Simulator to match what already ships.
Can I import my existing designs?
Yes. Claude Design exports import as editable pages.
What stops a Build from using the wrong version?
In an Initiative, a dependent Build refuses to start unless the latest handoff was explicitly approved.
Which model draws the screens?
Your Claude Code or Codex plan, the same subscription the rest of the workspace uses.

How it connects to the rest of the company

Every capability reads the same Library and reports into the same Initiatives.

InitiativesOne conversation that plans and runs work across the whole company.BuildCoding sessions in your own repo, on your Claude Code or Codex plan.VideoScripts, storyboards, generated takes and the exported cut.GrowthYour website, email, organic posts and ads, judged against the outcome.SalesProspect research, outreach, conversations and deals.SupportSupport cases investigated against your code, your data and your launches.AutomationsAgents on a schedule or a trigger that report back into the workspace.ObserveThe questions an Initiative keeps checking long after launch.LibraryWho you serve, how you sound and what you've decided, read first by every capability.

Early access · macOS

Run your next launch from one conversation.

We’re onboarding a few founders and small teams each week, one at a time, starting with the launch you’re planning next.

We email you once, when your seat is ready.