What problem does it solve?
Compozy UI work drifts when contributors hardcode colors, re-implement shipped primitives, or copy prototype markup instead of following the canonical design system. This Skill centralizes the visual authority so production UI, static artifacts, and reviews stay consistent with tokens, components, and product voice.
Core Features & Use Cases
- Canonical authority chain: Points to tokens.css, DESIGN.md, the @compozy/ui primitive inventory, component recipes, COPY.md, and PRODUCT.md as the sources of truth.
- Reuse gate enforcement: Requires mapping every generic UI need to an exported @compozy/ui primitive before authoring new components, with lint-backed shadow-primitive prevention.
- Visual contract handling: Defines how to implement from named OpenDesign references, treating them as normative for visual language but lossy for content, data, and component identity.
- Use Case: When implementing a new dashboard panel from a mock, activate this Skill to map each region to shipped primitives, pull values from design tokens, and record authorized differences before claiming parity.
Quick Start
Use the eng-design skill to review my new settings panel component and verify it uses canonical tokens and @compozy/ui primitives.