impeccable

Designs, audits, and refines frontend interfaces through command-driven UX and visual workflows.

1|Updated Aug 6, 2026
One-click install
npx skills add https://github.com/luce12/agent-dev-workflow --skill impeccable-luce12
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: impeccable
Source: https://github.com/luce12/agent-dev-workflow/tree/main/toolkits/impeccable
Command: npx skills add https://github.com/luce12/agent-dev-workflow --skill impeccable-luce12

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Frontend interfaces often ship with bland visuals, weak hierarchy, accessibility gaps, and inconsistent design systems. This Skill gives an AI agent a structured design-director workflow with dedicated commands for building, critiquing, auditing, and refining UI so design work follows a repeatable quality floor instead of ad-hoc judgment. ## Core Features & Use Cases - Command-driven design operations: 20+ commands such as shape, critique, audit, polish, bolder, quieter, distill, harden, animate, colorize, typeset, layout, adapt, and optimize, each backed by a dedicated reference playbook. - Technical and UX audits: scored reports across accessibility, performance, theming, responsive design, and implementation integrity, with P0-P3 severity findings and recommended follow-up commands. - Product and design context capture: init and document commands write PRODUCT.md and DESIGN.md so subsequent work stays on-brand, with native iOS/Android platform guidance for mobile apps. - Use Case: A developer asks to audit a dashboard before release; the Skill runs the audit playbook, scores five dimensions, lists verified issues by severity, and recommends polish, adapt, and harden passes in priority order. ## Quick Start Ask the agent to run the impeccable audit command on your main dashboard page and report the highest-severity issues.

Frequently Asked Questions about impeccable

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit a frontend UI for accessibility and performance issues?▼

Run the audit command, which checks accessibility, performance, theming, responsive design, and implementation integrity. It produces a scored report out of 20 with P0-P3 severity findings and recommends specific follow-up commands to fix each issue.

How to make a bland landing page design more distinctive?▼

Use the bolder command to amplify a flat section using the existing design system's own vocabulary, or the overdrive command for technically ambitious effects. Both preserve confirmed brand commitments and scope changes to the named target.

Does this design workflow support native iOS and Android apps?▼

Yes, native platforms are supported through dedicated reference variants. iOS and Android projects route to platform-specific audit and adapt playbooks covering safe areas, Dynamic Type, Material Design 3, touch targets, and system gestures.

What is the difference between the critique and audit commands?▼

Critique evaluates design from a UX perspective with heuristic scoring and persona-based feedback. Audit runs code-level technical checks on accessibility, performance, theming, and responsive behavior, documenting measurable issues without fixing them.

When should I not use this UI design skill?▼

It is not intended for backend-only or non-UI tasks. It also avoids open-ended self-QA loops; verification is bounded to a small number of inspection passes before handing off to the polish command.