Use this skill FIRST for any UI-facing task. Do not jump straight to implementation patterns, component tweaks, or styling edits before setting design direction and applying these guardrails.

If this skill applies and you skip it, generic UI is the usual result: weak hierarchy, default-library aesthetics, and interaction quality that feels assembled rather than designed.

Related Skills

design-interaction-motion-craft: motion behavior validation
copywriting: marketing copy generation and rewrite support
humanizer: remove AI-writing artifacts in UI copy

Routing discipline:

Announce design-skill usage before substantial UI work.
Establish design direction before writing or revising UI code.
Route specialized subproblems immediately after direction-setting: motion to design-interaction-motion-craft; marketing copy to copywriting; anti-slop copy polish to humanizer.
Keep shared goal explicit: we want interfaces that feel intentional, usable, and specific to the product.