Impeccable
Impeccable is an AI frontend design Skill for building and refining interfaces: typography, layout, accessibility, responsive behavior and browser iteration.
These skills push an agent's frontend output past the default generic look that people call AI slop. They include taste and style guides, image-to-UI conversion, component state modeling and stress tests that break a component on purpose.
31 skillsImpeccable is an AI frontend design Skill for building and refining interfaces: typography, layout, accessibility, responsive behavior and browser iteration.
Quickly deslop UI code by fixing spacing, hierarchy, typography, and small layout issues. Use when the interface needs a fast cleanup or polish pass.
Prevent and remove generic AI-generated design defaults, incoherent visual choices, and established UI defects while creating, revising, or reviewing websites, apps, screenshots, mockups, and design code. Use as a passive quality gate during UI work or for an explicit anti-slop cleanup; preserve the chosen art direction instead of forcing a neutral redesign.
Build multiple component variants in the real page and compare their tradeoffs.
Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions "my UI looks off" (or amateur/unprofessional), "fix the design", "Tailwind styling", "color palette", "visual hierarchy", "design system", "spacing scale", or "component styling". Also trigger when building consistent design tokens, creating dark mode themes, improving data-visualization clarity, or polishing UI details before launch. Covers grayscale-first workflow, constrained design scales, shadows, and component styling. For typeface selection, see web-typography. For usability audits, see ux-heuristics.
Implement an interface from a screenshot or mockup and compare the rendered result with the reference.
Render a chosen component in a temporary page under relevant stress scenarios.
Render a component’s states on a temporary page with mock data and a switcher.
Rebuild reference websites as editable Next.js pages with an AI coding agent. Inspect responsive layouts, assets and interactions, then compare the result with the source.
Apply Vue 3 component, reactivity and SSR guidance in a Vue project.
Build distinctive web interfaces with content-informed typography, composition and visual direction.
Use for UI design and implementation work to avoid generic AI-looking interfaces. Provides anti-slop rules, a required discovery phase before coding, and guidance for layout, typography, color, motion, accessibility, dashboards, tables, landing pages, theming, and polish. Trigger when editing UI code or reviewing and refining components, pages, screens, layouts, animations, responsive behavior, or design systems.
Work with Vite configuration, plugins, server-side rendering and library builds.
Use Vue component, reactivity and Composition API references.
Create or modify Voyager declarative plugins, site adapters and native primitives.
Art direction for AI-built websites and app screens, with real imagery, separate page and app workflows, and browser inspection. The main entry is design-taste-frontend.
Build responsive UI components with project design systems, accessible interactions and complete application states.
Audit websites, apps, screenshots, mockups, and design code for harmful AI-design clichés, generic generated defaults, and established UI defects. Use when the user wants evidence-backed design feedback, an anti-slop review, or a removal-first cleanup plan without a speculative redesign.
Deterministic design critique for HTML/CSS screens. Runs 73 slop guards extracted from the set of rules professional designers use in production-grade designs to catch the tells that make UI read as AI-generated (gradient-clipped headlines, the default indigo accent, puffy shadows, emoji icons, fake dot charts and decorated gauges, badges floated over the hero, eyebrow kickers above the H1, fake magazine mastheads, colored edge-stripe rails, two-tone headlines, over-designed list rows, layout-collapse bugs, em-dash copy, placeholder imagery), auto-fixes what can be safely rewritten, and reports the rest with concrete edits. Use whenever generated or hand-written HTML/CSS is about to be shown, exported, shipped, or committed, or when asked to critique a design, check it for slop, or give a second opinion on a generated screen.
This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.
Build multi-component HTML artifacts with React, state management and a bundled delivery workflow.
Work with Tailwind CSS v4 using a locally synchronized documentation snapshot, migration notes and implementation guidance.
Improve UI using a project’s existing components, design tokens and assets, with optional Uizze references.
Organize frontend code with Feature-Sliced Design v2.1, from placement and import boundaries to framework integration.
Implement UI from Figma or an image with the project’s existing components and tokens.
A collection of 14 agent skills for interface reviews, UI implementation, component testing and technical illustration.
Build Astro pages and components, configure adapters and use the framework's development commands.
Audit an existing product surface against its own design evidence, identify verified UI problems, and write self-contained implementation plans for another agent. Strictly read-only on product source. Use when asked to review, refine, improve, or clean up an interface without replacing its identity; investigate design-system drift; or prepare a design handoff.
Guidance on writing fast, robust, modern Svelte code. Load this skill whenever in a Svelte project and asked to write/edit or analyze a Svelte component or module. Covers reactivity, event handling, styling, integration with libraries and more.
Review a branch, pull request or uncommitted change for introduced UI regressions.
Build and refine user interfaces with typography decisions and screenshot-based review.
Compare AI design skills for design systems, shadcn/ui, frontend creation and interface refinement, with practical briefs to help you choose a workflow.
Pick a taste-focused skill when everything looks the same, image-to-UI when you have a mockup, and the stress-test or state-machine skills when components fail on edge cases.