impeccable

Request guidelines for a specific component and the Skill restates the design intent, defines token constraints, then specifies anatomy, variants, states, and interaction behavior. Output ends with accessibility acceptance criteria and a QA checklist for code review.

Impeccable uses primary #CC8800 amber, secondary #C55221 burnt orange, semantic success/warning/danger colors, Chakra Petch typography on a 12/14/16/20/24/32 scale, and a 4/8/12/16/24/32 spacing scale.

Yes, all guidelines target WCAG 2.2 AA with keyboard-first interactions and visible focus states. Every accessibility statement must be testable in implementation, and conflicts between aesthetics and accessibility are resolved in favor of accessibility.

Guidelines define default, hover, focus-visible, active, disabled, loading, and error states as relevant. They also describe keyboard, pointer, and touch interaction behavior plus responsive edge cases like long labels and empty states.

Avoid it when your project uses a different brand identity or token set, since all rules are anchored to Impeccable's specific palette, fonts, and spacing. It also does not generate production code, only specification documents.