How do I install the Gsa Usds skill?

Run npx skillmds@latest add blencorp/gsa-usds in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Gsa Usds safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Gsa Usds?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Gsa Usds free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Gsa Usds?

blencorp (@blencorp) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Gsa Usds by blencorp — Agent Skill

Name: Gsa Usds
Author: blencorp

Gsa Usds

Builds dense operational federal React interfaces with GSA TTS's A U.S. Design System, semantic tokens, accessible components, and light/dark modes. Use for staff tools, dashboards, permitting, and similar systems that explicitly choose this pre-npm Git distribution; it is not USWDS — use the uswds skill for USWDS work.

blencorp 3accb01 4 files · 5.2 KB Updated Sep 17, 2026

File contents

GSA TTS A U.S. Design System

Before editing

Confirm the product is inside this system's scope.
Read references/implementation.md before installing, copying, or changing upstream assets.
Read references/sources.md for provenance, version, and license.
Inspect and preserve the target project's framework, package manager, asset pipeline, and accessibility tests.

Workflow

Choose one documented delivery path and pin an exact package, commit, release, or downloaded asset snapshot.
Use only official components, tokens, templates, and examples that are actually public.
Extend through documented mechanisms. Label every unsupported addition as custom.
Record the upstream version or commit and the accepted maturity/maintenance risk.
Test keyboard operation, focus, names/roles/states, errors, status messages, contrast, zoom/reflow, responsive behavior, and supported browsers.

Boundaries

Scope: Dense operational federal applications. Do not confuse this React system, named USDS, with the government-wide U.S. Web Design System (USWDS).
Delivery: React and TypeScript components installed directly from the official Git repository.
Release: Installed from the official GitHub repository; no npm package is published. Pin an exact commit or tag.
Do not invent a registry package, public repository, component API, or release commitment.
Do not imply that a beta, hosted asset, code example, or product-specific repository is government-wide.
Do not claim legal or WCAG conformance for the completed service solely from component use.
If this system does not fit the product's requirements, route to the governing system or stop and explain the gap.

References

Implementation
Sources

---name: gsa-usdsdescription: Builds dense operational federal React interfaces with GSA TTS's A U.S. Design System, semantic tokens, accessible components, and light/dark modes. Use for staff tools, dashboards, permitting, and similar systems that explicitly choose this pre-npm Git distribution; it is not USWDS — use the uswds skill for USWDS work.---# GSA TTS A U.S. Design System## Before editing1. Confirm the product is inside this system's scope.2. Read [references/implementation.md](references/implementation.md) before installing, copying, or changing upstream assets.3. Read [references/sources.md](references/sources.md) for provenance, version, and license.4. Inspect and preserve the target project's framework, package manager, asset pipeline, and accessibility tests.## Workflow1. Choose one documented delivery path and pin an exact package, commit, release, or downloaded asset snapshot.2. Use only official components, tokens, templates, and examples that are actually public.3. Extend through documented mechanisms. Label every unsupported addition as custom.4. Record the upstream version or commit and the accepted maturity/maintenance risk.5. Test keyboard operation, focus, names/roles/states, errors, status messages, contrast, zoom/reflow, responsive behavior, and supported browsers.## Boundaries- **Scope:** Dense operational federal applications. Do not confuse this React system, named USDS, with the government-wide U.S. Web Design System (USWDS).- **Delivery:** React and TypeScript components installed directly from the official Git repository.- **Release:** Installed from the official GitHub repository; no npm package is published. Pin an exact commit or tag.- Do not invent a registry package, public repository, component API, or release commitment.- Do not imply that a beta, hosted asset, code example, or product-specific repository is government-wide.- Do not claim legal or WCAG conformance for the completed service solely from component use.- If this system does not fit the product's requirements, route to the governing system or stop and explain the gap.## References- [Implementation](references/implementation.md)- [Sources](references/sources.md)

Frequently asked questions