impeccablelisted
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.
RubyEyedReaper/Odin-Skills · ★ 0 · Web & Frontend · score 64
Install: claude install-skill RubyEyedReaper/Odin-Skills
<!-- odin:suppressed-under-operational -->
**Odin routing note — suppressed under the `operational` memory class.** This is a product-web skill. `.claude/hooks/odin-skill-gate.sh` emits its suggestion arm only when the active memory class is in-project (`task:<slug>` in `.claude/.runtime/active-mem-class`); under `operational` — harness-only work, and the default when that file is absent — the arm is suppressed and nothing here is ever suggested by intent. Invoke it explicitly with the `Skill` tool when it is wanted during harness work. Checked by `.claude/scripts/skill-reachability-check.sh`.
<!-- /odin:suppressed-under-operational -->
Designs and iterates production-grade frontend interfaces. Real working code, committed design choices, exceptional craft.
## Setup
You MUST do these steps before proceeding:
1. Run `node .claude/skills/impeccable/scripts/context.mjs` once per session. If the request names or implies a file, route, or app inside a monorepo, infer the concrete path and run `node .claude/skills/impeccable/scripts/context.mjs --target <path>` instead. If you've already seen its output in this conversation, do not re-run it. The script either prints the project's PRODUCT.md (and DESIGN.md when present) as a markdown block, or tells you it's missing. Follow whatever it prints. **If it reports `NO_PRODUCT_MD`, stop and follow `reference/init.md` before doing anything else.** If the output ends with an `UPDATE_AVAILABLE` directive, follow it (ask the user once ab