@jakubkrehel

oklch-skill explains perceptually uniform color spaces and references conversion, palette generation, contrast checking, and tailwind integration workflows without procedural depth or actionable steps.

better-writing establishes principles for clear, consistent user-facing copy across interfaces, emphasizing clarity over cleverness and adherence to existing product voice before writing any new text.

better-layout covers foundational principles for web layout: grouping, alignment, spacing, and adaptive breakpoints. defers accessibility, visual polish, and typography to sibling skills. references numeric starting points but lacks concrete step-by-step procedures.

better-ui covers design polish through motion, surfaces, and composition details. guides reviewers on inspecting animations and references related typography and accessibility skills.

better-interface coordinates cross-discipline review by delegating domain rules to specialist skills and consolidating findings into one prioritized verdict, with scope inference and coverage modes (quick/full) to bound work.

Interface review of a change rather than a screen: uncommitted work, the current branch, or a pull request. Covers interface quality, not correctness, tests,…

Accessibility engineering for product interfaces. Use when building or reviewing UI components and custom widgets, or when the user reports a keyboard or…

Color systems for digital products. Use when creating or extending a palette, theming light and dark appearances, or auditing the colors in a codebase.…

Web typography. Use when picking or pairing typefaces, setting up a type scale, or styling and truncating text in components. Triggers on typography, font…

Design engineering principles for making interfaces feel polished. Use when building UI components, reviewing frontend code, implementing animations, hover…