Claude Skills by kish21

Phase 2 (Development) of product-playbook — design the product's UI BEFORE building screens. Turns "I don't know what it should look like" into agreed design principles + a confirmed sample page + a concrete, archetype-correct DESIGN.md (shadcn-compatible tokens) that every later build step reuses. Use after /structure when the product has a user-facing UI, or run /design-system "design the UI", "what should it look like", "make a design system", "my UI looks AI-generated / fonts too small". ...

Phase 2/3 of product-playbook — the UI enforcement gate. Mechanically checks built UI (and its DESIGN.md) against the /design-system universal laws, with a REAL WCAG contrast engine (OKLCH/hex → ratio) so contrast is computed, never asserted. Use after building or changing UI, before shipping, or in CI — run /frontend-audit "check my UI", "is this accessible", "audit the frontend", "did I break the design system". Reports a pass/warn/error scorecard and exits non-zero on errors. Pairs with /d...