How do I install the Public Sector Design Systems skill?

Run npx skillmds@latest add blencorp/public-sector-design-systems 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 Public Sector Design Systems 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 Public Sector Design Systems?

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 Public Sector Design Systems free to use?

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

Who published Public Sector Design Systems?

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

Public Sector Design Systems by blencorp

Name: Public Sector Design Systems
Author: blencorp

Public Sector Design Systems

Routes federal, state, District of Columbia, and U.S. territorial digital-service work to the correct official public design system. Use when selecting a government design system, checking whether a jurisdiction has reusable public implementation, or avoiding unsupported cross-jurisdiction substitutions.

blencorp Updated Sep 17, 2026

File contents

Public-sector design-system router

Choose the authoritative system before writing interface code.

Route the request

Identify the government owner, product, and channel. Distinguish a statewide system from an agency- or product-specific system.
Read references/catalog.md for the current public evidence and corresponding implementation skill.
If a matching implementation skill is installed, read and follow that skill. If it is not installed, tell the user its exact skill name and continue only from the public material available in this router.
If the row is guidance-only, internal, legacy, or not found, say so before producing code. Do not invent component names, tokens, packages, or source availability.
Use USWDS as a fallback only when the official system inherits USWDS or the user explicitly authorizes that fallback.

Source precedence

Use evidence in this order:

Current official government documentation
Official government-controlled source repository
Package registry metadata linked to that source
Official policy, procurement, audit, or annual-report evidence

Do not treat third-party catalogs, screenshots, look-alike packages, university systems, or agency examples as statewide authority.

Output contract

When routing, state:

jurisdiction and product scope;
system name and release state;
installable skill name, if one exists;
official documentation and source/package links;
any limitation that prevents a grab-and-build implementation.

For product work, preserve the target project's framework and build tooling unless the official system requires a specific integration.

Guardrails

A design system helps accessibility work; it does not prove legal or WCAG conformance for the finished service.
Do not mix state branding or federal product branding without authorization.
Do not present an internal platform component as portable source.
Do not start new work on a superseded system when a current successor is documented.
Recheck dated package versions before changing dependencies.

Read references/methodology.md when assessing a new or changed upstream system.

---name: public-sector-design-systemsdescription: Routes federal, state, District of Columbia, and U.S. territorial digital-service work to the correct official public design system. Use when selecting a government design system, checking whether a jurisdiction has reusable public implementation, or avoiding unsupported cross-jurisdiction substitutions.---# Public-sector design-system routerChoose the authoritative system before writing interface code.## Route the request1. Identify the government owner, product, and channel. Distinguish a statewide system from an agency- or product-specific system.2. Read [references/catalog.md](references/catalog.md) for the current public evidence and corresponding implementation skill.3. If a matching implementation skill is installed, read and follow that skill. If it is not installed, tell the user its exact skill name and continue only from the public material available in this router.4. If the row is guidance-only, internal, legacy, or not found, say so before producing code. Do not invent component names, tokens, packages, or source availability.5. Use USWDS as a fallback only when the official system inherits USWDS or the user explicitly authorizes that fallback.## Source precedenceUse evidence in this order:1. Current official government documentation2. Official government-controlled source repository3. Package registry metadata linked to that source4. Official policy, procurement, audit, or annual-report evidenceDo not treat third-party catalogs, screenshots, look-alike packages, university systems, or agency examples as statewide authority.## Output contractWhen routing, state:- jurisdiction and product scope;- system name and release state;- installable skill name, if one exists;- official documentation and source/package links;- any limitation that prevents a grab-and-build implementation.For product work, preserve the target project's framework and build tooling unless the official system requires a specific integration.## Guardrails- A design system helps accessibility work; it does not prove legal or WCAG conformance for the finished service.- Do not mix state branding or federal product branding without authorization.- Do not present an internal platform component as portable source.- Do not start new work on a superseded system when a current successor is documented.- Recheck dated package versions before changing dependencies.Read [references/methodology.md](references/methodology.md) when assessing a new or changed upstream system.

Frequently asked questions