Figma Design System Builder
warpdotdev/warp
Builds or updates a design system in Figma from a codebase in ordered phases: discovery, variables and tokens, components, theming and documentation, with checkpoints.
Update an existing DSDS spec based on implementation changes, Figma updates, or written instructions.
Install Dsds Update
$ npx skills add somerandomdude/design-system-documentation-schema --skill dsds-update -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install somerandomdude/design-system-documentation-schema dsds-update --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/somerandomdude/design-system-documentation-schema.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/dsds-update .claude/skills/dsds-update && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "dsds-update" agent skill from https://github.com/somerandomdude/design-system-documentation-schema/tree/main/.agents/skills/dsds-update into .claude/skills/dsds-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dsds-update", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/somerandomdude/design-system-documentation-schema/tree/main/.agents/skills/dsds-updateType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add somerandomdude/design-system-documentation-schema --skill dsds-update -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install somerandomdude/design-system-documentation-schema dsds-update --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/somerandomdude/design-system-documentation-schema.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/dsds-update .agents/skills/dsds-update && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "dsds-update" agent skill from https://github.com/somerandomdude/design-system-documentation-schema/tree/main/.agents/skills/dsds-update into .agents/skills/dsds-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dsds-update", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add somerandomdude/design-system-documentation-schema --skill dsds-update -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install somerandomdude/design-system-documentation-schema dsds-update --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/somerandomdude/design-system-documentation-schema.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/dsds-update .cursor/skills/dsds-update && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "dsds-update" agent skill from https://github.com/somerandomdude/design-system-documentation-schema/tree/main/.agents/skills/dsds-update into .cursor/skills/dsds-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dsds-update", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/somerandomdude/design-system-documentation-schema.git --path .agents/skills/dsds-update--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add somerandomdude/design-system-documentation-schema --skill dsds-update -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install somerandomdude/design-system-documentation-schema dsds-update --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/somerandomdude/design-system-documentation-schema.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/dsds-update .gemini/skills/dsds-update && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "dsds-update" agent skill from https://github.com/somerandomdude/design-system-documentation-schema/tree/main/.agents/skills/dsds-update into .gemini/skills/dsds-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dsds-update", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install somerandomdude/design-system-documentation-schema dsds-updateInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add somerandomdude/design-system-documentation-schema --skill dsds-update -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/somerandomdude/design-system-documentation-schema.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/dsds-update .github/skills/dsds-update && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "dsds-update" agent skill from https://github.com/somerandomdude/design-system-documentation-schema/tree/main/.agents/skills/dsds-update into .github/skills/dsds-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dsds-update", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add somerandomdude/design-system-documentation-schema --skill dsds-update -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install somerandomdude/design-system-documentation-schema dsds-update --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/somerandomdude/design-system-documentation-schema.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/dsds-update .opencode/skills/dsds-update && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "dsds-update" agent skill from https://github.com/somerandomdude/design-system-documentation-schema/tree/main/.agents/skills/dsds-update into .opencode/skills/dsds-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dsds-update", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
dsds-update- GitHub stars
- 116
- Token cost
- ~1.1k tokens
- SKILL.md length
- 531 words
- Files
- 1
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Update an existing DSDS spec based on implementation changes, Figma updates, or written instructions.
- Works in 5 steps: Read the existing document. → Identify what changed — compare against… → Apply edits to the document, preserving… → …
- Add prop to spec
- SKILL.md covers Procedure, Common Updates, Rules and Schema References, plus 1 more section
- Calls npx; reaches designsystemdocspec.org
What it does
Dsds Update is an agent skill from somerandomdude/design-system-documentation-schema. Update an existing DSDS spec based on implementation changes, Figma updates, or written instructions. Triggers on "update spec", "modify spec", "add prop to spec", "sync spec", "spec drift".
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Frontend & Design. It works with Figma. The licence is Apache-2.0.
When your agent uses it
- Add prop to spec
Example prompts
- “update spec”
- “modify spec”
- “add prop to spec”
- “/dsds-update”
Requirements
- Node.js
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Read the existing document.
- Identify what changed — compare against the source (code diff, Figma update, user instructions).
- Apply edits to the document, preserving structure and existing content.
- Run npx dsds-validate .dsds.yaml — fix errors until it passes. Run npx dsds-lint .dsds.yaml for advisory documentation-quality warnings.
- If your project generates its own index or catalog from these documents, regenerate it now.
What it can do on your machine
Read from SKILL.md and the folder at commit 52790fe. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
npx
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
designsystemdocspec.org
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Dsds Update loads about 1.1k tokens when it runs. Until then it costs about 51 tokens; SKILL.md has 531 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from somerandomdude/design-system-documentation-schema at commit 52790fe, republished under its Apache-2.0 licence (© somerandomdude). 531 words, ~1,103 tokens.
Download SKILL.mdSave it as
.claude/skills/dsds-update/SKILL.md (or your agent's skills folder).- name
- dsds-update
- description
- Update an existing DSDS spec based on implementation changes, Figma updates, or written instructions. Triggers on "update spec", "modify spec", "add prop to spec", "sync spec", "spec drift".
- metadata.version
- 0.21.2
Update a DSDS Spec
Modify an existing .dsds.yaml file.
Procedure
- Read the existing document.
- Identify what changed — compare against the source (code diff, Figma update, user instructions).
- Apply edits to the document, preserving structure and existing content.
- Run
npx dsds-validate <the-file>.dsds.yaml— fix errors until it passes. Runnpx dsds-lint <the-file>.dsds.yamlfor advisory documentation-quality warnings. - If your project generates its own index or catalog from these documents, regenerate it now.
Common Updates
| Change | Location in the document |
|---|---|
| New prop | sourceFiles already points at the real file — no edit needed, unless there's no source file, in which case update the definitions section that stands in for the prop list |
| New API contract | specs (top-level, rel: contract) — the generated contract document, not the raw source sourceFiles names |
| New variant value | Top-level traits item with traitType: variant and kind: enum, in its values array |
| New state | Top-level traits item with traitType: state |
| Anatomy change | The definitions section with context: anatomy |
| New accessibility requirement | A guidelines item in a framing: how-to-use section, or a definitions section with context: keyboard |
| Status change | metadata.status (always an object: {status: "..."}) |
| New agent rule | A section with for: agent |
Rules
- Never remove existing content unless explicitly instructed — documents are additive by default.
- Preserve the existing order of
sectionsandtraitsitems. - When you add a new top-level field, insert it at its
style guide
position rather than appending it to the end — that guide's whole point is
that a reader can rely on the order. Field order never affects validity;
npx dsds-lintreports a deviation as an advisory warning (DSDS-17–DSDS-23), never a failure. Follow it because the next reader benefits, not because a tool will block you. Don't reshuffle fields that were already there just to comply; that turns a one-line edit into an unreviewable diff. - When adding trait values, place them in logical order (not necessarily alphabetical) — the first value is implied as the default. A value's
idis the real API name in whatever case the API uses. - Update
metadata.statusif the change constitutes a breaking API modification. - If adding a new relationship, use
common/ref's one form:{to: "<id>", rel: "<depends-on|extends|alternative-to|composes|...>"}for something in this document's own graph, or{href: "<url>", rel: "..."}for something outside it. A guideline'scheckstakesrel: test,rel: lint-rule, orrel: agent-test.
Show full SKILL.md (147 more words)Show less
Schema References
When adding new sections or fields, verify the exact fields:
- Bundled schema:
https://designsystemdocspec.org/v0.21.2/dsds.bundled.schema.json(ornode_modules/design-system-documentation-schema/schema/dsds.bundled.schema.jsonif DSDS is installed as a dependency) - Section reference:
/schema/sections-<kind>.mdon this site — for example sections-guidelines.md - Entry reference:
/schema/entries-<kind>.md— for example entries-component.md - Full architecture: https://designsystemdocspec.org/schema#how-the-schema-is-organized
Gotchas
- Modifying
idorkindis a breaking change — confirm with the user. - A trait's fields are closed, so a field the schema doesn't declare is a hard error, not a warning. Every trait carries
traitType(variantorstate) alongside itskind. - DSDS doesn't track which props are "required" as a schema fact — that lives in the real source file
sourceFilespoints at. A new required prop is still a breaking change worth calling out in aguidelinesitem, just not a field to flip in the spec itself. - Token references (in
traits,combos, or prose) must matchids of tokens actually documented intokens/.
© somerandomdude, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/dsds-update of somerandomdude/design-system-documentation-schema.
Open the folder on GitHubat commit 52790fe
Compare with similar skills
Dsds Update next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Dsds Update this skillsomerandomdude/design-system-documentation-schema | 116 | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Figma Design System Builderwarpdotdev/warp | 65k | 2 repos | ~4.4k | Automated safety check: Pass | AGPL-3.0 | |
| Figma use_figma Plugin API Ruleswarpdotdev/warp | 65k | 4 repos | ~4.4k | Automated safety check: Pass | AGPL-3.0 | |
| Figma Design to Codewarpdotdev/warp | 65k | 4 repos | ~2.9k | Automated safety check: Pass | AGPL-3.0 | |
| Figma Design System Rules Generatorwarpdotdev/warp | 65k | 3 repos | ~4.6k | Automated safety check: Pass | AGPL-3.0 | |
| Figma Code Connect Componentswarpdotdev/warp | 65k | 2 repos | ~4.2k | Automated safety check: Pass | AGPL-3.0 |
Similar skills
Figma use_figma Plugin API Rules
warpdotdev/warp
Required groundwork before any use_figma call: the rules and reference files for running JavaScript in a Figma file through the Plugin API without common failures.
Figma Design to Code
warpdotdev/warp
Turns a Figma frame or component into production code that matches the design, using the Figma MCP server and the project's own design system.
Figma Design System Rules Generator
warpdotdev/warp
Creates project-specific design system rules from your codebase so coding agents implement Figma designs with your components, naming and tokens.
Figma Code Connect Components
warpdotdev/warp
Maps published Figma components to their code implementations with Code Connect, using the Figma MCP suggestion and mapping tools.
Cc Design
ZeroZ-lab/cc-design
High-fidelity HTML design and prototype creation. An agent skill from ZeroZ-lab/cc-design.
More from somerandomdude/design-system-documentation-schema
Dsds Add
somerandomdude/design-system-documentation-schema
Author a new Design System Doc Spec (DSDS) spec from component implementation, Figma design, or written requirements.
Dsds Specs
somerandomdude/design-system-documentation-schema
Everything about Design System Doc Spec (DSDS) — entry kinds, sections, schema structure, and how it fits into the ecosystem.
Dsds Validate
somerandomdude/design-system-documentation-schema
Validate DSDS specs against the bundled schema and check for consistency issues.
Related
Works with
Categories
Questions about Dsds Update
What does Dsds Update do?
Update an existing DSDS spec based on implementation changes, Figma updates, or written instructions. Dsds Update is an agent skill from somerandomdude/design-system-documentation-schema. Update an existing DSDS spec based on implementation changes, Figma updates, or written instructions.
When should I use Dsds Update?
Dsds Update fits situations like: add prop to spec.
How do I install Dsds Update in Claude Code?
Run `npx skills add somerandomdude/design-system-documentation-schema --skill dsds-update -a claude-code`. Or copy the skill folder (.agents/skills/dsds-update in somerandomdude/design-system-documentation-schema) into .claude/skills/dsds-update in your project. Claude Code loads it when a task matches its description.
How do I install Dsds Update in Codex?
Run `npx skills add somerandomdude/design-system-documentation-schema --skill dsds-update -a codex`. Or copy the skill folder (.agents/skills/dsds-update in somerandomdude/design-system-documentation-schema) into .agents/skills/dsds-update in your project. Codex loads it when a task matches its description.
Can I use Dsds Update in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add somerandomdude/design-system-documentation-schema --skill dsds-update -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/dsds-update, .gemini/skills/dsds-update, .github/skills/dsds-update and .opencode/skills/dsds-update in your project.
What does Dsds Update need to run?
Going by SKILL.md and its folder, Dsds Update needs the command-line tools its instructions call (npx). Our summary lists: Node.js.
Does Dsds Update access the network?
SKILL.md names 1 domain. In commands or code: designsystemdocspec.org; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Dsds Update safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Dsds Update use?
Dsds Update is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Dsds Update use?
About 1.1k tokens (SKILL.md is roughly 4.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Dsds Update?
Skills that share tags, products or a category with Dsds Update: Figma Design System Builder (warpdotdev/warp, 65k stars), Figma use_figma Plugin API Rules (warpdotdev/warp, 65k stars), Figma Design to Code (warpdotdev/warp, 65k stars) and Figma Design System Rules Generator (warpdotdev/warp, 65k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Dsds Update?
somerandomdude (a GitHub user) maintains it in somerandomdude/design-system-documentation-schema, which has 116 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 7, 2026.
Source: somerandomdude/design-system-documentation-schema on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.