design-system-foundations
Design System Foundations
Overview
Use this skill to establish stable UI foundations that multiple teams can adopt without diverging conventions.
Scope Boundaries
- Use this skill when the task matches the trigger condition described in
description. - Do not use this skill when the primary task falls outside this skill's domain.
Shared References
- Lifecycle governance guidance:
references/foundation-lifecycle-guidance.md
Templates And Assets
- Foundation inventory:
assets/foundation-inventory-template.csv
- Ownership and lifecycle model:
assets/foundation-ownership-model-template.md
Inputs To Gather
- Current component inventory, duplication hotspots, and drift patterns.
- Product surface priorities and expected growth areas.
- Engineering constraints (frameworks, theming model, release cadence).
- Governance expectations (ownership, review, and change control model).
Deliverables
- Foundation architecture map (primitives, composition rules, and boundaries).
- Ownership model with lifecycle states (draft/active/deprecated/retired).
- Adoption strategy with migration sequence and risk notes.
- Decision log for rejected alternatives and rationale.
Quick Example
- Primitive ownership: typography, spacing, and color scale managed centrally.
- Shared component ownership: cross-product components owned by design system team.
- Product extension policy: local variants allowed only with expiration and convergence plan.
- Lifecycle rule: deprecated components blocked for new usage after defined cutoff.
Quality Standard
- Foundation boundaries are explicit and do not overlap ambiguously.
- Ownership and lifecycle are defined for every foundation artifact.
- Adoption plan minimizes breaking migrations for active teams.
- Accessibility and localization constraints are baked into foundation definitions.
Workflow
- Audit existing UI patterns and capture inventory in
assets/foundation-inventory-template.csv. - Define foundational primitives and composition boundaries.
- Assign ownership and lifecycle governance per foundation area using
assets/foundation-ownership-model-template.md. - Validate technical feasibility with implementation teams.
- Publish adoption plan with phased migration guidance and lifecycle policy from
references/foundation-lifecycle-guidance.md.
Failure Conditions
- Stop when foundation scope is too broad to govern consistently.
- Stop when ownership is undefined for shared artifacts.
- Escalate when migration cost is known but lacks mitigation plan.
More from kentoshimizu/sw-agent-skills
graph-algorithms
Graph algorithm workflow for modeling entities/relations and selecting traversal, path, ordering, or flow strategies. Use when correctness or performance depends on graph representation and algorithm choice; do not use for schema-only modeling or deployment topology planning.
14bash-style-guide
Style, review, and refactoring standards for Bash shell scripting. Trigger when `.sh` files, files with `#!/usr/bin/env bash` or `#!/bin/bash`, or CI workflow blocks with `shell: bash` are created, modified, or reviewed and Bash-specific quality controls (quoting safety, error handling, portability, readability) must be enforced. Do not use for generic POSIX `sh`, PowerShell, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
11architecture-clean-architecture
Clean Architecture workflow for enforcing dependency direction, stable domain boundaries, and use-case-centered application design. Use when teams must separate business rules from frameworks and delivery mechanisms; do not use for isolated module cleanup without boundary implications.
11powershell-style-guide
Style, review, and refactoring standards for PowerShell scripting. Trigger when `.ps1`, `.psm1`, `.psd1` files, or CI workflow blocks with `shell: pwsh` or `shell: powershell` are created, modified, or reviewed and PowerShell-specific quality controls (error handling, parameter validation, readability, operational safety) must be enforced. Do not use for Bash, generic POSIX `sh`, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
10github-codeowners-management
Govern CODEOWNERS rules so review routing reflects real ownership and risk boundaries on GitHub. Use when repository ownership mapping or mandatory reviewer rules must be defined, updated, or audited; do not use for non-GitHub runtime architecture or data-layer design.
9security-authentication
Security workflow for authentication architecture, credential lifecycle, and session/token assurance. Use when login, identity proofing, MFA, or session security decisions are required; do not use for authorization policy design or non-security quality tuning.
9