What problem does it solve?
It solves the problem of choosing the right specialist and orchestration path for complex design-system work, so you don’t waste cycles guessing whether you need audit, governance, token work, accessibility, or implementation.
Core Features & Use Cases
- Specialist routing for design-system needs: Maps your request to the appropriate specialist agent(s) and command(s), with an explicit rationale.
- Multi-agent workflow coordination: Coordinates end-to-end pipelines such as full audits, component creation, design-system setup, and app-level design system builds.
- Strategic squad overview when uncertain: Helps when the request spans multiple domains or you need a consolidated plan before execution.
Use cases: auditing an existing design system, planning a new design system from scratch, generating components consistently across tokens and accessibility, and aligning frontend architecture with governance and documentation.
Quick Start
Activate design-design-chief and ask for an orchestration plan by describing what you want to achieve for your design system (for example, an audit, a new component, or a full setup) rather than trying to pick the exact specialist yourself.
