Design System Engineering

Create an operating system for recurring interface decisions that exists in the actual design and code surfaces. This skill owns foundations, component contracts, migration, and governance. A DESIGN.md, moodboard, or remembered convention is evidence to inspect, not proof of a system.

Use when

• Repeated UI patterns have diverged across product surfaces or repositories.
• Tokens, components, documentation, and implemented behaviour need reconciliation.
• A team needs an incremental path from ad-hoc UI to a maintained system.

Do not use when