agency-uswds-developer

Enforce USWDS components and design tokens for federal web interfaces.

Updated Jul 23, 2026
One-click install
npx skills add https://github.com/rajyeole6/AI-RECRUITER --skill agency-uswds-developer-rajyeole6
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agency-uswds-developer
Source: https://github.com/rajyeole6/AI-RECRUITER/tree/main/.agents/skills/engineering-uswds-developer
Command: npx skills add https://github.com/rajyeole6/AI-RECRUITER --skill agency-uswds-developer-rajyeole6

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the challenge of maintaining accessibility, consistency, and compliance with federal standards (21st Century IDEA, Section 508) when building government websites, preventing the common pitfalls of ad-hoc CSS overrides and non-compliant custom components.

Core Features & Use Cases

  • Token-Driven Theming: Customizes the U.S. Web Design System (USWDS) using design tokens and Sass settings rather than brittle CSS overrides.
  • Component Governance: Ensures the use of accessibility-tested, official USWDS components like banners, identifiers, and form patterns.
  • Use Case: A developer needs to theme a new agency site to match brand guidelines while ensuring the .gov banner, footer, and mobile-first grid remain fully compliant with federal website standards.

Quick Start

Use the agency-uswds-developer skill to audit the current project theme settings and ensure all color and spacing customizations are implemented via design tokens.

Frequently Asked Questions about agency-uswds-developer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a federal website that meets 21st Century IDEA and Section 508 compliance?

To build a federal website that meets 21st Century IDEA and Section 508 compliance, standardize development using U.S. Web Design System components and mobile-first design tokens. This approach enforces accessible government interfaces and prevents non-compliant custom components.

What is the best way to customize U.S. Web Design System themes without breaking accessibility?

Customizing U.S. Web Design System themes safely requires using Sass settings and design tokens rather than brittle CSS overrides. This token-driven theming architecture maintains accessible, mobile-first federal interfaces while adhering to brand guidelines.

How do I implement the .gov banner and footer using the U.S. Web Design System?

Implementing the .gov banner and footer requires using official, accessibility-tested U.S. Web Design System components. This component governance ensures your government website includes mandated identifiers while maintaining full federal compliance.

Can I use custom CSS overrides instead of Sass design tokens for USWDS components?

Custom CSS overrides should be avoided for USWDS components. Standardizing federal interface development relies on applying design tokens and Sass settings to ensure maintainable theming architectures and prevent ad-hoc non-compliant styling.

Does the U.S. Web Design System support mobile-first federal website requirements?

Yes, the U.S. Web Design System supports mobile-first federal website requirements. Standardizing development with USWDS components and design tokens ensures interfaces remain fully responsive and compliant with federal website technical mandates.

Why does my government website fail Section 508 accessibility requirements?

Government websites fail Section 508 accessibility requirements when developers use ad-hoc CSS overrides and non-compliant custom components. Enforcing official U.S. Web Design System components ensures consistent design language and adherence to federal accessibility mandates.