gabrielmouallem

Claude Design Transport — Design skill for Claude Code

Design community

Move a Claude Design project or design system between accounts with fidelity via the DesignSync write API — plus backup, bootstrapping, blank-screen namespace diagnosis, de-CDN'ing and bundle auditing.

How to install Claude Design Transport

This entry records only its repository, not the path inside it, so there is no exact command to give. Open gabrielmouallem/claude-design-transport and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Claude Design Transport does

Alternatives in Design

Doc — Read, create, and edit .docx documents with formatting and layout fidelity 14.6k ★
Polish UI — Polish UI elements by auditing SCSS and TSX markup against the Anytype design system, then fixing discrepancie 8.7k ★
Pack — Bundle every designlang output (DTCG tokens, Tailwind, shadcn, Figma vars, motion, anatomy, Storybook, prompts 3.6k ★

README

![claude-design-transport: Move your design system. Keep it editable.](assets/readme-banner.png)

claude-design-transport

**Move a Claude Design project or design system from one account or project to another, with fidelity, by using the DesignSync write API instead of file uploads.**

That is the primary purpose, and it is a narrow, infrequent job. The pieces it is built from are not. Read the next section before deciding this is a one-off you can skip.

Why install it even if you never migrate

Each of these stands on its own:

Backup and version control. Claude Design has no version history and no restore. Exporting on a cadence, committing to git, and knowing which files in the bundle are source and which are derived output is a discipline the reconnaissance and inventory phases give you for free. Anyone with a design system worth keeping needs this whether or not they ever move it.
Bootstrapping a design-system project from an existing repo. The push route also runs in the direction nobody calls migration: local component library → fresh design-system project. Same tooling, same gating, same verification. This is the common case for a team adopting Claude Design with a codebase that predates it.
Diagnosing blank screens after any move, rename or duplicate. A compiled Claude Design bundle binds one global named from the project's own name and id, and pages destructure it unguarded. Rename the project, duplicate it, or move it, and the global ceases to exist — TypeError, blank screen, clean console. The derivation rule and the fail-loud guard in references/namespace.md fix this regardless of how the project got moved.
De-CDN'ing a design system. Vendoring React, Babel, icon fonts and typefaces out of a project so it renders in restricted or offline environments — air-gapped review, CSP-constrained sandboxes, or simply not wanting prototypes to break when a CDN has a bad day. Independent of transport entirely.
**Auditing