Spec Writer
garrytan/gstack
Converts a vague idea into a precise, executable spec in five phases, files it as an issue and can start an agent on it in a fresh worktree.
Validate DSDS specs against the bundled schema and check for consistency issues.
Apache-2.0Auto-check passed
Install Dsds Validate
$ npx skills add somerandomdude/design-system-documentation-schema --skill dsds-validate -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install somerandomdude/design-system-documentation-schema dsds-validate --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-validate .claude/skills/dsds-validate && 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-validate" agent skill from https://github.com/somerandomdude/design-system-documentation-schema/tree/main/.agents/skills/dsds-validate into .claude/skills/dsds-validate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dsds-validate", 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-validateType 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-validate -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install somerandomdude/design-system-documentation-schema dsds-validate --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-validate .agents/skills/dsds-validate && 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-validate" agent skill from https://github.com/somerandomdude/design-system-documentation-schema/tree/main/.agents/skills/dsds-validate into .agents/skills/dsds-validate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dsds-validate", 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-validate -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install somerandomdude/design-system-documentation-schema dsds-validate --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-validate .cursor/skills/dsds-validate && 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-validate" agent skill from https://github.com/somerandomdude/design-system-documentation-schema/tree/main/.agents/skills/dsds-validate into .cursor/skills/dsds-validate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dsds-validate", 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-validate--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-validate -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install somerandomdude/design-system-documentation-schema dsds-validate --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-validate .gemini/skills/dsds-validate && 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-validate" agent skill from https://github.com/somerandomdude/design-system-documentation-schema/tree/main/.agents/skills/dsds-validate into .gemini/skills/dsds-validate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dsds-validate", 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-validateInstalls 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-validate -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-validate .github/skills/dsds-validate && 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-validate" agent skill from https://github.com/somerandomdude/design-system-documentation-schema/tree/main/.agents/skills/dsds-validate into .github/skills/dsds-validate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dsds-validate", 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-validate -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-validate --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-validate .opencode/skills/dsds-validate && 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-validate" agent skill from https://github.com/somerandomdude/design-system-documentation-schema/tree/main/.agents/skills/dsds-validate into .opencode/skills/dsds-validate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dsds-validate", 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-validate- GitHub stars
- 114
- Token cost
- ~1.3k tokens
- SKILL.md length
- 567 words
- Files
- 1
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Validate DSDS specs against the bundled schema and check for consistency issues.
- Works in 3 steps: Schema compliance (every file validates… → Semantic rules (DSDS-01–DSDS-11, via npx… → Documentation-quality advisories…
- SKILL.md covers Quick Command, Documentation-Quality Checks…, Full Validation and Interpreting Failures, plus 3 more sections
- Calls npx; reaches designsystemdocspec.org
What it does
Dsds Validate is an agent skill from somerandomdude/design-system-documentation-schema. Validate DSDS specs against the bundled schema and check for consistency issues. Triggers on "validate specs", "check specs", "spec errors", "run validation".
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The licence is Apache-2.0.
Example prompts
- “validate specs”
- “check specs”
- “spec errors”
- “/dsds-validate”
Requirements
- Node.js
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Schema compliance (every file validates against the bundled schema)
- Semantic rules (DSDS-01–DSDS-11, via npx dsds-validate)
- Documentation-quality advisories (DSDS-12–DSDS-23, informational, via npx dsds-lint)
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 Validate loads about 1.3k tokens when it runs. Until then it costs about 43 tokens; SKILL.md has 567 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). 567 words, ~1,280 tokens.
Download SKILL.mdSave it as
.claude/skills/dsds-validate/SKILL.md (or your agent's skills folder).- name
- dsds-validate
- description
- Validate DSDS specs against the bundled schema and check for consistency issues. Triggers on "validate specs", "check specs", "spec errors", "run validation".
- metadata.version
- 0.21.2
Validate DSDS Specs
Run schema and semantic validation on your .dsds.yaml documents.
Quick Command
npx dsds-validate <files-or-globs>This validates every file given against the DSDS v0.21.2 bundled schema using Ajv2020, plus a set of semantic rules JSON Schema alone can't express — the DSDS-01–DSDS-11 catalog (resolution, uniqueness, platform vocabulary, composes/depends-on cycles, and file-existence checks), each tagged structural or semantic. Pass --strict to promote the warning-only rules (DSDS-05, DSDS-08, DSDS-09, DSDS-11) to hard failures.
Documentation-Quality Checks (advisory)
A second, separate tier (DSDS-12–DSDS-23) that answers "is this documentation good?" rather than "is this document allowed?" — RFC 2119 keyword casing, a token description that just restates its id or its scale position, a hard-requirement guideline with no checkedBy, a component with no when-to-use guidance, and (DSDS-17–DSDS-23) whether an entry/document follows the style guide's field order, section grouping, and guideline-item ordering. Warnings only; never blocks a build on their own. Ships in the published package as its own command:
npx dsds-lint <files-or-globs>Full Validation
- Schema compliance (every file validates against the bundled schema)
- Semantic rules (
DSDS-01–DSDS-11, vianpx dsds-validate) - Documentation-quality advisories (
DSDS-12–DSDS-23, informational, vianpx dsds-lint)
Interpreting Failures
| Error pattern | Fix |
|---|---|
must have required property 'id'/'kind'/'name'/'description' | Every entry needs all four — add the missing field |
must have required property 'entries' | A base document (has schemaVersion) needs a non-empty entries array |
must match pattern (on an entry id) | Use lowercase, dash-separated segments, optionally dot-chained (e.g. color.action.primary) |
must match pattern (on a trait id or enum value) | Copy the real prop/attribute name in whatever case it uses (isDisabled) — any case is accepted, but a dot never is, since a combo addresses a value as traitId.valueId |
must match pattern (on a token id) | Same as a trait id, plus dot or slash chaining — a design tool's own path (Color/Action/Primary) is valid as written |
must have required property 'traitType' | Every trait declares traitType: variant or traitType: state alongside its kind |
unevaluatedProperty on a trait | A trait's fields are closed: traitType, kind, id, name, description, purpose, examples, since, refs, and values on an enum. A trait carries no $extensions of its own — put vendor data on the entry instead |
[DSDS-04] id "..." is declared more than once | Two entries (or an entry and a shared item) share an id — rename one |
[DSDS-05] ... targets unknown entry/shared / unknown item | A ref's to: "entryId#itemId" doesn't resolve — check the target id and item id both exist |
[DSDS-06]/[DSDS-07] cycle | A composes or depends-on ref chain loops back on itself — break the cycle |
[DSDS-11] ... doesn't exist on disk | A relative sourceFiles[].file, source, or rel: file href doesn't resolve — warning-only unless run with --strict |
| Id doesn't match filename | Not validator-enforced, but a convention worth following anyway (e.g. checkbox → checkbox.dsds.yaml) — makes a spec discoverable by id alone |
Show full SKILL.md (122 more words)Show less
Validation Loop
- Run
npx dsds-validate <files-or-globs> - If errors, fix the first reported file
- Re-run validation
- Repeat until all pass
Schema Sources
The validation schema comes from the DSDS project:
- Bundled schema (used by
dsds-validate):https://designsystemdocspec.org/v0.21.2/dsds.bundled.schema.json, ornode_modules/design-system-documentation-schema/schema/dsds.bundled.schema.jsonif installed as a dependency - This is a single-file version with every schema file's own
$idstill present, so$refs resolve without needing to be inlined
If validation fails on a field you're unsure about, consult the relevant docs page:
- https://designsystemdocspec.org/schema#how-the-schema-is-organized (how the schema is organized)
- https://designsystemdocspec.org/conformance (full rule catalog and conformance classes)
/schema/sections-<kind>.mdon this site (per-section constraints) — for example sections-guidelines.md/schema/entries-<kind>.md(per-entry constraints) — for example entries-component.md
When to Validate
- After creating or modifying any
.dsds.yamlfile - Before committing changes
© 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-validate of somerandomdude/design-system-documentation-schema.
Open the folder on GitHubat commit 52790fe
Compare with similar skills
Dsds Validate 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 Validate this skillsomerandomdude/design-system-documentation-schema | 114 | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Spec Writergarrytan/gstack | 136k | — | ~14k | Automated safety check: Notes | MIT | |
| Specgarden-co/classic-jazz | 2.5k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Spec Driven Workflowalirezarezvani/claude-skills | 28k | — | ~3.9k | Automated safety check: Pass | MIT | |
| Sparc Specruvnet/ruflo | 74k | — | ~1.1k | Automated safety check: Notes | MIT | |
| Write A Specdifferent-ai/openwork | 24k | — | ~3.3k | Automated safety check: Pass | Custom licence |
Similar skills
Spec
garden-co/classic-jazz
Implement features using Spec Driven Development (SDD) workflow.
Spec Driven Workflow
alirezarezvani/claude-skills
A skill your agent uses when the user asks to write specs before code, define acceptance criteria, plan features before implementation, generate tests from specifications, or follow spec-first…
Sparc Spec
ruvnet/ruflo
Run the SPARC Specification phase — gather requirements, define acceptance criteria, identify constraints, and store the spec in memory
Write A Spec
different-ai/openwork
Write or extend an E2E journey spec in evals/specs that proves a PR's change to a human reviewer.
To Spec
vinvcn/mattpocock-skills-zh-CN
把当前对话转成 spec 并发布到项目 issue tracker——不做访谈，只综合已经讨论的内容. An agent skill from vinvcn/mattpocock-skills-zh-CN.
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 Update
somerandomdude/design-system-documentation-schema
Update an existing DSDS spec based on implementation changes, Figma updates, or written instructions.
Questions about Dsds Validate
What does Dsds Validate do?
Validate DSDS specs against the bundled schema and check for consistency issues. Dsds Validate is an agent skill from somerandomdude/design-system-documentation-schema. Validate DSDS specs against the bundled schema and check for consistency issues.
How do I install Dsds Validate in Claude Code?
Run `npx skills add somerandomdude/design-system-documentation-schema --skill dsds-validate -a claude-code`. Or copy the skill folder (.agents/skills/dsds-validate in somerandomdude/design-system-documentation-schema) into .claude/skills/dsds-validate in your project. Claude Code loads it when a task matches its description.
How do I install Dsds Validate in Codex?
Run `npx skills add somerandomdude/design-system-documentation-schema --skill dsds-validate -a codex`. Or copy the skill folder (.agents/skills/dsds-validate in somerandomdude/design-system-documentation-schema) into .agents/skills/dsds-validate in your project. Codex loads it when a task matches its description.
Can I use Dsds Validate 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-validate -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-validate, .gemini/skills/dsds-validate, .github/skills/dsds-validate and .opencode/skills/dsds-validate in your project.
What does Dsds Validate need to run?
Going by SKILL.md and its folder, Dsds Validate needs the command-line tools its instructions call (npx). Our summary lists: Node.js.
Does Dsds Validate 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 Validate 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 Validate use?
Dsds Validate 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 Validate use?
About 1.3k tokens (SKILL.md is roughly 5.1k 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 Validate?
Skills that share tags, products or a category with Dsds Validate: Spec Writer (garrytan/gstack, 136k stars), Spec (garden-co/classic-jazz, 2.5k stars), Spec Driven Workflow (alirezarezvani/claude-skills, 28k stars) and Sparc Spec (ruvnet/ruflo, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Dsds Validate?
somerandomdude (a GitHub user) maintains it in somerandomdude/design-system-documentation-schema, which has 114 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.