# Update kit

> Bring a new release of the Figma kit and your own work together. Your agent moves your brand modes and screens to the new copy, or brings new components into your file, relinked by name.

## Before you start

A new release of the [Figma kit](https://pro.shadcn.co/docs/figma-kit) arrives as a new copy, and your current file stays as it is. This skill brings the two together.

It changes one of the two files. It needs Figma's remote MCP server, edit access to the file that changes, view access to the other one and a Figma plan that lets agents write to files. See [Skills that write to Figma](https://pro.shadcn.co/docs/agent-skills/setup#skills-that-write-to-figma).

## Usage

### Open the new release

Open [Account → Downloads](https://pro.shadcn.co/account/downloads) and click **Open in Figma**. Figma creates a new copy of the kit in **Drafts**.

### Save a version

In the file that will change, choose **File → Save to version history**. The agent can't do this for you, and it's your way back.

### Run the skill

Give the agent both links: your file and the new copy.

```text title="Prompt"
/shadcnpro-update-kit

My file: https://figma.com/design/abc123/Kit
New copy: https://figma.com/design/def456/Kit-new
```

### Choose the way

The agent compares the two files and tells you what only you have, such as brand modes, variables and pages, and what is new in the release. Then you choose one of the two ways below.

### Paste when the agent asks

The agent tells you what to copy from one file and paste into the other. It relinks what you pasted and reports what it changed.

## Two ways to update

| | Move to the new copy | Bring new parts into your file |
|---|---|---|
| Fits when | Your work is brand modes, variable values and your own screens or components | You edited the kit's own components and want to keep them |
| You end up with | The new copy as your working file, complete and current | Your file, plus the new components you picked |
| Effort | Small. Modes are moved by the agent, and your pages are pasted once. | Grows with every component |

The agent recommends moving to the new copy unless you changed the kit's components.

### Move to the new copy

1. The agent creates your own variables in the new copy, then your brand modes, with every value they have in your file. Variables that are new in the release get the values of the style your brand started from.
2. You copy your screens and components and paste them onto a new page in the new copy.
3. The agent relinks what you pasted to the new copy.
4. For files that use your old copy as a library, you publish the new copy and use Figma's [Swap library](https://help.figma.com/hc/en-us/articles/4404856784663-Swap-style-and-component-libraries).

### Bring new parts into your file

1. The agent lists the components that are new in the release, and you pick the ones you want.
2. You copy them in the new copy and paste them onto a new page in your file.
3. The agent relinks them to your file, and tells you which components and variables they need that your file doesn't have yet.
4. Components you edited are never replaced. To take the release's version of one, you paste it next to yours and decide which one stays.

## Why you paste and the agent relinks

An agent works inside one Figma file at a time and can't carry layers from one file to another. Your copy and paste does that, and it keeps every component exact.

What you paste still points to the file it came from: instances to its components, colors and numbers to its variables, text to its styles. The agent points each of them to the part with the same name in the file it is in now:

- **Instances** switch to the local component with the same name and variant.
- **Variables** on fills, strokes, effects, text and component properties switch to the local variable with the same collection and name.
- **Styles** for text, color and effects switch to the local style with the same name.
- **Modes** set on a frame switch to the local mode with the same name.

It runs as a report first, so you see what will change. Anything without a match by name is listed, never guessed. Afterwards the agent runs the report again and compares screenshots of the relinked frames with the originals.

## What it never does

- It never changes or deletes your components, variables or modes.
- It never replaces a component you edited with the release's version on its own.
- It never matches by a similar name. A variable that was renamed in the release is reported as missing, and you decide what takes its place.

## Without write access

When the agent can't write to the file, Figma's own tools still move a brand mode. In your file, open the Variables view, right-click the mode and choose **Export mode**. In the new copy, duplicate the mode of the style your brand started from, rename it, right-click it and choose **Import mode**. Figma updates the variables whose names match. See [Figma's guide to modes](https://help.figma.com/hc/en-us/articles/15343816063383-Modes-for-variables).
