impeccable
impeccable shapes production frontend interfaces through design iteration, critique, and craft. It handles everything from visual hierarchy and accessibility to responsive layouts, design systems, and micro-interactions—grounded in project context via PRODUCT.md and DESIGN.md. Real working code, committed design choices.
impeccable designs and iterates production-grade frontend interfaces with committed craft and real working code.
AI-generated summary based on this skill's SKILL.md
Install
joewinke/jat/impeccable · repository language: Svelte
git clone https://github.com/joewinke/jat
cp -r jat/.agents/skills/impeccable ~/.claude/skills/impeccableFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How does impeccable help design and iterate frontend interfaces?
impeccable shapes production frontend interfaces through design iteration, critique, and craft. It guides you from initial concept through refinement, handling visual hierarchy, layout decisions, accessibility, and responsive design. By grounding work in your project context via PRODUCT.md and DESIGN.md, impeccable ensures iterations stay aligned with your product vision and deliver real working code with committed design choices.
Can impeccable improve UI and UX for my website?
Yes. impeccable evaluates and critiques UI/UX for design quality and usability issues, then refines existing interfaces through polishing, enhancement, or toning down visual design. It addresses everything from typography and spacing to color strategy, visual hierarchy, and information architecture—helping you identify problems and execute improvements with craft.
What technical UI problems can impeccable fix?
impeccable fixes technical UI problems including accessibility compliance, responsive design across mobile and tablet screens, performance optimization, and edge-case hardening. It also handles i18n considerations and ensures your interface works reliably across contexts. These fixes integrate seamlessly with your design refinements.
Does impeccable help create design systems and component libraries?
impeccable can extract and document design systems, tokens, and reusable components from your interfaces. While this is a lighter focus than its core design and iteration work, it supports you in building scalable, maintainable design infrastructure grounded in your actual codebase and design decisions.
How can impeccable polish my app interface before launch?
impeccable polishes app interfaces by refining visual design, adding animations and micro-interactions, clarifying UX copy and error messages, and auditing for performance and usability. It reviews your dashboard or product interface holistically, tightens details, and hardens the experience for real users—ensuring your launch feels intentional and delightful.
What license does impeccable use?
impeccable is released under the MIT license, allowing you to use, modify, and distribute it freely in both open-source and commercial projects.
SKILL.md
rendered from the published skill — quoted content, verbatim
name: impeccable description: 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.
── Open Design sidecar ───────────────────────────────────────────────────
App-specific metadata behind a namespaced key (OD's od: pattern — see
open-design/docs/skills-protocol.md). A plain Claude-Code harness ignores
this block; OD-aware tooling reads it.
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 15 files
.agents/skills/impeccable/SKILL.md
.agents/skills/impeccable/agents/openai.yaml
.agents/skills/impeccable/evals/README.md
.agents/skills/impeccable/evals/craft.evals.json
.agents/skills/impeccable/evals/critique.evals.json
.agents/skills/impeccable/evals/polish.evals.json
.agents/skills/impeccable/evals/run.mjs
.agents/skills/impeccable/reference/adapt.md
.agents/skills/impeccable/reference/animate.md
.agents/skills/impeccable/reference/audit.md
.agents/skills/impeccable/reference/bolder.md
.agents/skills/impeccable/reference/brand.md
.agents/skills/impeccable/reference/clarify.md
.agents/skills/impeccable/reference/cognitive-load.md
.agents/skills/impeccable/reference/color-and-contrast.md