Agent skill · Audited from source
Cds Design To Code
skill · coinbase/cdsNOASSERTION licenceAudited 14 Oct 2026 · source a03fbe3db14b
Is it safe? With care — CAUTION, grade B (89/100). We read this skill's source at commit a03fbe3db14b and found no filesystem, network or shell access and no hard-coded secrets. The audit raised 2 findings, 0 critical or high. What it does: Turn Figma designs into CDS React (cds-web) or React Native (cds-mobile) code. Use when the user shares a Figma design URL (e.g. `figma.com/design/...?node-id=...`) or asks to "implement this design" or "build this from…
Cite
Cite this page
ModelsAtlas. “Cds Design To Code (coinbase/cds)”. Retrieved 14 Oct 2026. https://modelsatlas.com/skills/coinbase/cds-design-to-code
Trust audit
Audit 0.4.1 · source read 14 Oct 2026
CAUTION means the audit found things worth knowing before you trust this skill. Grade B is shared by 17,406 of 18,389 audited skills.
What the source does
- FilesystemNone observedNo reads or writes in the source
- NetworkNone observedNo outbound calls in the source
- ShellNone observedNo commands run in the source
- DependenciesPinnedNothing floats
- SecretsNone foundNo keys in source
Five audit layers
| Layer | What we check | Result | Findings |
|---|---|---|---|
L0 Provenance | Repo owner, licence, archive status, activity | WARN | 2 |
L1 Static source | Secrets, path traversal, supply chain, hidden code | NA | 0 |
L2 Instructions | Prompt injection, authority framing, hidden directives | PASS | 0 |
L3 Inventory | The files and declarations match the source | PASS | 0 |
L4 Sandbox | Run in isolation and watch behaviour | SKIPPED why | 0 |
Gates applied: no behavioural pass.
Findings (2)
MEDIUMInventory / provenanceinv.symlink · .claude/skills/git.resolve-version-conflicts
.claude/skills/git.resolve-version-conflicts
- Why
- link not followed
- Fix
- —
MEDIUMInventory / provenanceinv.symlink · .claude/skills/skill-creator
.claude/skills/skill-creator
- Why
- link not followed
- Fix
- —
Audit 0.4.1 · source sha a03fbe3db14b · 14 Oct 2026Report an issue or request a re-scan
Provenance
Who published it, and what the verdict is pinned to
- Publishercoinbase GitHub organizationOwner of the repository this skill is read from
- Source foldercoinbase/cds/skills/cds-design-to-codeThe exact folder we audited
- LicenceNOASSERTIONAs the repository states it
- Commit pinned for this verdicta03fbe3db14bA new audit runs when the source changes
- Repository statusNot archivedLast push 7 days ago
- Sandboxed runNot runSkills are read, not executed; layer L4 is skipped
What it tells the agent
Full source on GitHub ↗Its description: Turn Figma designs into CDS React (cds-web) or React Native (cds-mobile) code. Use when the user shares a Figma design URL (e.g. `figma.com/design/...?node-id=...`) or asks to "implement this design" or "build this from…
--- name: cds-design-to-code description: | Turn Figma designs into CDS React (cds-web) or React Native (cds-mobile) code. Use when the user shares a Figma design URL (e.g. `figma.com/design/...?node-id=...`) or asks to "implement this design" or "build this from Figma" in a frontend project that is using Coinbase Design System (CDS). Do not use for general CDS UI work with no Figma reference (use `cds-code`), or for design critique without an implementation request. license: Apache-2.0 metadata: version: '2.0.0' --- # CDS Design To Code This skill provides a structured workflow for translating Figma designs into CDS-first production code with high visual fidelity. It bridges the Figma MCP server with the Coinbase Design System, ensuring that designs are implemented using real CDS components and conventions rather than raw Figma HTML output. The goal is not to copy the Figma output literally. The goal is to use Figma MCP as the design source, then adapt that output into the target project's real CDS component stack. ## When to use - Use when the user shares a Figma URL like `figma.com/design/...?node-id=...` and wants it implemented. - Use when translating a Figma design into CDS React or React Native code. - Use when the user asks to "implement this design" or "build this from Figma." - Do not use when there is no Figma design to reference -- use the `cds-code` skill instead for general CDS UI work. - Do not use for design feedback or critique without an implementation request. ## Prerequisites This skill is a thin bridge that leans on `cds-code` for all CDS component selection, styling, doc lookup, and code quality standards. Verify the following before starting. - **Figma MCP server (required)** -- must be connected and accessible. Verify by checking whether `get_design_context` is available as an MCP tool. **Early exit:** if the Figma MCP server is missing or `get_design_context` is not available, **stop immediately**. Tell the user that this workflow depends on the Figma MCP server and its `get_design_context` tool, suggest they configure a Figma MCP server in their project (e.g. via `.cursor/mcp.json` or their agent's MCP settings), then run this workflow again. - **`cds-code` skill (strongly recommended)** -- provides component selection, styling rules, doc lookup workflow, and code quality standards. If the `cds-code` skill is not available, do not exit. Instead, ask the user whether they want to proceed using only the Figma MCP server, explaining that the `cds-code` skill significantly improves the quality of the CDS code written (correct component selection, style props over inline styles, valid import paths). It is still possible to produce decent CDS code from Figma without it -- the skill only makes the output better. Proceed only if the user confirms; otherwise wait for them to install/enable `cds-code`. - **`cds-docs` skill (recommended)** -- provides CDS component documentation (routes, props, examples) used by the `cds-code` skill. If it is not available you may continue, but documentation greatly improves accuracy. - User must provide a Figma URL in the format: `https://figma.com/design/:fileKey/:fileName?node-id=1-2` ## Required Workflow **Follow these steps in order. Do not skip steps.** ### Step 1: Optionally enable the `cds-code` skill Start by grounding yourself in the current repo by enabling the `cds-code` skill. Upon activation, the skill should provde you with information about which CDS NPM packages are installed. Use this to determine if you are working with `cds-web` or `cds-mobile` (a React or React Native project respectively). If the `cds-code` skill is not available, and the user has opted out of enabling it, try your best to determine which CDS package is used by inspecting the project's source. Do not infer the platform from the Figma designs alone -- the repo is the source of truth. If both web and mobile exist and the target is genuinely ambiguous, ask one concise clarifying question. ### Step 2: Fetch Figma Design Context Use Figma MCP's `get_design_context` tool with the extracted file key and node ID parameters. **IMPORTANT:** Set the `clientFrameworks` parameter to request the correct CDS code connect mappings. Many components in Figma maintain 2 mappings, one for `cds-web` and one for `cds-mobile`. Always call `get_design_context` with `disableCodeConnect: false` so Code Connect context is used whenever it is available. Never set `disableCodeConnect` to true. Always keep screenshots enabled. **If Figma MCP prompts to create Code Connect mappings for unmapped components:** Designs will commonly contain components without Code Connect mappings -- either custom one-off components in the design file, or CDS components whose mappings have not been published yet. This is the expected common case, not an error. When `get_design_context` returns a response indicating components are missing Code Connect mappings (e.g. a prompt like "Would you like to connect code components to the Figma design?"), **do not surface this to the user and do not ask them about Code Connect mappings**. Authoring `.figma.ts` Code Connect files is a CDS team responsibility, not something customers using this skill should do. Instead, **silently skip the prompt** and immediately call `get_design_context` again with `disableCodeConnect: false` to get the best available context, then proceed with implementation. Treat unmapped components like any other fallback HTML/Tailwind output per the confidence matrix in Step 5. **If the response is too large or truncated:** 1. Keep the original user node as the source-of-truth entry point. 2. Run `get_metadata(fileKey=":fileKey", nodeId="1-2")` to get the high-level node map and discover child node IDs. 3. Identify the most relevant child frame or section for the requested implementation scope. 4. Re-run `get_design_context` on the narrower child node. 5. Tell the user briefly that you narrowed to
Excerpt, first 6,000 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.
Install
Pinned to the audited commit a03fbe3
git clone https://github.com/coinbase/cds git -C cds checkout a03fbe3db14b
The author documents no install command, so this uses the repository directly. Our verdict covers commit a03fbe3db14b only.
Works in which agents?
What its own text says, not a test
| Agent | Status | More |
|---|---|---|
| Cursor | Mentioned in its text, not tested | Skills for Cursor · About Cursor |
Audit history
Every audit, every source change
- !CAUTION B 89 / 100
first audit · source
a03fbe3db14b
README badge
For maintainers · shows the latest audit
[](https://modelsatlas.com/skills/coinbase/cds-design-to-code/)
The badge shows our verdict and grade for this skill, and links back to this page. It changes when the audit does.
Similar skills
All design & front-end skills →mattpocock/skills
Implement a piece of work based on a spec or set of tickets.
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
mattpocock/skills
Pursue a long-running goal in a single session by co-ordinating subagents.
Add this badge to your README
[](https://modelsatlas.com/skills/coinbase/cds-design-to-code/)
<a href="https://modelsatlas.com/skills/coinbase/cds-design-to-code/"><img src="https://modelsatlas.com/skills/coinbase/cds-design-to-code/badge.svg" alt="ModelsAtlas: CAUTION B"></a>
Questions about Cds Design To Code
What does the Cds Design To Code skill do?
Is Cds Design To Code safe to install?
What can Cds Design To Code access on my machine?
What do I need installed to use Cds Design To Code?
Which assistants does Cds Design To Code work with?
How current is this page?
Sources
- github.com/coinbase/cds/tree/master/skills/cds-design-to-code — the audited source at commit a03fbe3db14b and every finding aboveObserved · 14 Oct 2026
Spotted something wrong? Report a correction · Methodology
Keep going in your AI
Opens with this page as the source. We add nothing else to the prompt.
- What does the Cds Design To Code skill do?
- Is Cds Design To Code safe to install?
- What can Cds Design To Code access on my machine?