Agent Kit

The real kit files are not published from this personal copy of the site. The source templates and build script remain private, so the bundle can still be generated for an approved internal product team.

What the kit provides

The kit turns design-system guidance into files that coding agents can actually consume in another repo. This is the enablement layer, not just documentation.

• AGENTS.mdRepo-level instructions that tell coding agents which design-system files to read before producing UI, copy, or visual decisions.MD
• design-tokens.jsonMachine-readable token registry for color, typography, spacing, radius, shadow, motion, and layout.JSON
• design-tokens.cssCompiled CSS custom properties for light and dark themes.CSS
• pattern-registry.jsonComposition patterns with anatomy, variants, examples, accessibility rules, implementation notes, and review checklists.JSON
• anti-patterns.jsonDesign and implementation mistakes paired with safer alternatives for review and generation guardrails.JSON
• accessibility-basics.mdWCAG 2.2 AA baseline rules with practical examples for implementation.MD
• content-standards.mdVoice, tone, button-label, error-message, empty-state, and terminology rules.MD
• compliance-checklist.mdPreconditions an agent or reviewer must verify before UI ships.MD

Implementation model

The design system keeps a human-readable site and an agent-readable bundle in sync. The default portfolio build does not generate or publish the downloadable bundle.

1. Source files define the tokens, patterns, anti-patterns, principles, content rules, and accessibility rules.
2. The internal build script packages those files into a repo-ready kit for approved product teams.
3. The public build keeps the strategy and structure visible without exposing the complete downstream package.