feat: add USWDS Developer agent to Engineering Division

[epowelljr]

Summary

Adds a USWDS Developer agent to the Engineering Division — a government-focused frontend developer who builds trustworthy, accessible, consistent federal interfaces with the U.S. Web Design System, theming through design tokens and Sass settings instead of overriding the framework, reaching for the maintained accessibility-tested component before hand-rolling a custom one, and treating accessibility and 21st Century IDEA conformance as the baseline rather than a later phase.

What's included

• USWDS theme settings (design tokens) — a real _uswds-theme.scss showing token-based theming of color, spacing (units()), type scale, fonts, and grid, with explicit rules against override CSS and editing vendor files
• Component implementation spec — a usage contract that defaults to the official component, customizes only at the seams (settings/utilities/composition, never forking), and preserves built-in accessibility
• Required federal elements checklist — the .gov banner, the USWDS Identifier with its required links, header/footer patterns, and HTTPS/trust requirements
• Responsive layout spec — mobile-first layout on the USWDS grid with breakpoint behavior, touch targets, and 400% reflow verification
• CMS integration plan — USWDS in Drupal (theme/SDC/Twig, form theming) and WordPress (theme/blocks/enqueue) with upgrade-safe separation from the package
• 5-step workflow process — establish the foundation, theme through tokens, build with official components, integrate into the CMS, then verify accessibility/compliance/maintainability
• Domain expertise — USWDS tokens/settings/components/utilities and uswds-compile, accessible-by-default patterns and the federal design language, the compliance landscape (21st Century IDEA, Federal Website Standards, Section 508), and CMS/responsive engineering
• Success metrics dashboard — 10 metrics covering token-based theming, official-component usage, zero forked vendor files, conformance, required elements, contrast, and USWDS upgradability

Why it's broadly useful

Federal and public-sector sites are required to follow the federal design language and meet 21st Century IDEA, and the most common failure mode is overriding USWDS into something neither on-brand nor accessible nor maintainable. This agent encodes the theme-through-tokens, use-the-official-component, stay-upgradable discipline that keeps a government interface trustworthy, accessible, and able to take every upstream USWDS fix.

cc @msitarzewski

🤖 Generated with Claude Code