impeccable

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

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/abhinaaaavvv/dotfiles --skill impeccable-abhinaaaavvv
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: impeccable
Source: https://github.com/abhinaaaavvv/dotfiles/tree/main/.agents/skills/impeccable
Command: npx skills add https://github.com/abhinaaaavvv/dotfiles --skill impeccable-abhinaaaavvv

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Frontend interfaces built quickly often end up generic, inconsistent, or off-brand, and teams lack a systematic way to design, audit, and refine UI quality. This Skill provides a structured design workflow that loads project context (PRODUCT.md and DESIGN.md), enforces design laws, and offers 20+ targeted commands for building, evaluating, and polishing interfaces. ## Core Features & Use Cases - Command-driven design workflow: Commands like craft, shape, critique, audit, polish, bolder, quieter, animate, colorize, typeset, layout, harden, and adapt cover the full lifecycle from planning to production-ready UI. - Project context grounding: Loads PRODUCT.md (users, brand, principles) and DESIGN.md (colors, typography, components) via a context script so output stays on-brand instead of generic. - Anti-pattern enforcement: Shared design laws ban AI-slop patterns (gradient text, side-stripe borders, glassmorphism, hero-metric templates) and enforce OKLCH color, typography hierarchy, and motion standards. - Use Case: A developer building a landing page runs the teach command to capture brand context, uses shape to plan the UX with a confirmed brief, builds with craft, then runs audit and polish to fix accessibility, performance, and responsive issues before shipping. ## Quick Start Ask the agent to run the impeccable teach command to set up your project's PRODUCT.md and DESIGN.md context, then request a design task such as crafting or critiquing a specific page.

Frequently Asked Questions about impeccable

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

FAQPage Schema
How do I improve a bland or generic frontend design?▼

Run the bolder command on the target to amplify visual impact through stronger hierarchy, committed color strategies, and typographic contrast. The skill first loads your PRODUCT.md and DESIGN.md context so changes stay on-brand rather than defaulting to generic patterns.

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

Use the audit command, which scores five dimensions (accessibility, performance, theming, responsive design, anti-patterns) from 0-4 and produces a report with P0-P3 severity ratings. Each finding includes the file location, user impact, and a recommended follow-up command.

What are PRODUCT.md and DESIGN.md files used for?▼

PRODUCT.md captures users, brand, tone, and strategic principles, while DESIGN.md records colors, typography, and components. The skill loads both before any design work so output matches your project instead of producing generic results.

Does this skill work for backend or non-UI tasks?▼

No, it is explicitly scoped to frontend interface work such as pages, components, forms, and design systems. Backend-only or non-UI tasks fall outside its stated boundaries and should use other tools.

Why does the skill refuse to edit files before setup passes?▼

The preflight gates require loaded context, a valid PRODUCT.md, and a user-confirmed shape brief for craft commands. Skipping these gates produces generic output that ignores the project's brand and design system.