You're in the Studio

Settings

Your team, its people, and how changes reach your code.

General

How your team shows up for everyone in Bridge.

How changes reach your code

What happens once your team keeps a change.

Kept changes

Bridge writes each change for your developers

When your team keeps a change, Bridge writes it into the code for you, and your developers check it before it ships.

For developers
What developers get
Bridge commits each kept change on a new branch and opens a pull request against the default branch.
For developers

Open on GitHub (opens in a new tab)

Repository
the-bridge-company/ai-design-system-demo
Default branch
main
Tokens
packages/tokens/src
Mode
"changes": "direct"
Set in
bridge.config.json

Review rules

Who checks a change before it reaches the library your products use, and what each kind of change needs. How review works

Who checks a change

Design reviewers

People or GitHub teams who answer for how it looks.

peterbono

Code reviewers

People or GitHub teams who answer for the code.

peterbono

Checks the look

Says a change looks right.

peterbono

Checks the code

Says the code behind it is sound.

peterbono

Adds it to the library

Puts an approved change in the library your products use.

peterbono

Only owner

A design system run by one person.

As the only owner, peterbono checks the look and the code in one review.

Leads can publish small changes without review

Guidance, docs and fixes with no visual change.

On: team admins and the reviewers of that part publish them. They go live once the automatic checks pass.

Exception

Adds a change before every check is in. Owners only.

peterbono, with a written reason of at least 20 characters.

Token values

Colors, sizes and other values your designers change in Studio or send from Figma.

Ship once the look is approved and the automatic checks pass.

Nobody checks the code. From Figma, sending counts as the approval. A renamed or removed token waits for a code check.

This change needs a review because it changes the rules.
Kind of changeNeeds
Token changesDesign owner + tech owner. A token value change (values changed or tokens added only): design owner only
New component or variantDesign owner + tech owner
Docs fixesOne owner, or none when a lead publishes it
For developers

Bridge counts approvals on GitHub reviews. A ruleset or branch protection on main keeps unreviewed pull requests out.

Design owners
@peterbono
Tech owners
@peterbono
governance.rights.approveDesign
design
governance.rights.approveTech
tech
governance.rights.ship
tech
Owner override
@peterbono, reason of 20+ characters, posted on the pull request
Token values
A pull request that only changes token values (values changed or tokens added, nothing renamed or removed, no code) needs the design approval only: the tech approval counts as given, and it merges once the required checks pass. From Figma, Bridge approves it and turns on auto-merge. A renamed or removed token waits for a tech owner (docs/BUILD-REQUESTS.md).
Protected branches
main, master
Branch prefix
bridge/
Set in
bridge.config.json, governance; docs/GOVERNANCE.md

Safety

What keeps unchecked changes out of the library, and when Bridge shows a change before and after.

Protection

Checking whether every change goes through review.

Visual before and after

Automatic

Runs on every change to tokens or components.

Your team approves it before it applies.

Figma and Claude

Work on the library from Figma or from your own Claude.

Figma plugin

Brings tokens into Figma Variables and pushes your edits back. New token values reach the library after the automatic checks, new components go to developers to build.

Community page in review

Your own Claude

Gives your Claude 68 tools on this design system. Claude drafts a change and sends it for review: nothing reaches the library until a person approves it.

Set it up

Products

The products your team designs for. Their explorations happen in a copy, and the developers get a task when a designer is done.

Art print shop

Explorations for Art print shop live in the-bridge-company/art-print-shop-design.

Dasboard Data test D

Explorations for Dasboard Data test D live in the-bridge-company/dasboard-data-test-d-design.

Your AI tools

The AI you build with: Bridge shows the next step in these only. Your own choice.

AI tools you use

Bridge shows the next step in these tools only. Only you see this choice.

Appearance

How Bridge looks for you, only in this browser. It changes nothing for your team.

Theme