ui-designer

To turn UI concepts into implementable design specifications, you translate high-level UI goals into structured outputs covering information architecture, interaction flows, and visual tokens. This ensures consistent, repeatable implementations across product screens.

The best way to structure design system tokens for handoff is to define reusable component outlines with explicit state models, such as default, hover, active, and disabled, alongside concrete rules for color, spacing, and typography.

Yes, you can define interaction flows and state transitions as a cohesive specification. The skill captures layout and state transitions to provide actionable guidelines for developers, product managers, and QA to implement UI accurately.

UI implementation suffers from inconsistent results due to vague specs and missing design rules. Defining structured design-system alignment with explicit component tokens and consistency rules ensures engineers follow repeatable implementation patterns.

No, you do not need an existing design system to generate component definitions. You can start by defining a reusable component outline with specific states and tokens to establish design-system alignment and ensure handoff clarity.