impeccable

Audit and polish frontend interfaces for UX, accessibility, and responsiveness.

Updated May 17, 2026
One-click install
npx skills add https://github.com/ohdaveed/director-hearing-manager --skill impeccable-ohdaveed
Or copy as Structured Prompt for Agentâ–¼
Please help me install this Agent Skill.
Skill: impeccable
Source: https://github.com/ohdaveed/director-hearing-manager/tree/main/.agents/skills/impeccable
Command: npx skills add https://github.com/ohdaveed/director-hearing-manager --skill impeccable-ohdaveed

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Improve a frontend interface from concept to production-grade quality, including UX clarity, visual hierarchy, accessibility, responsiveness, performance, and polish, without drifting into backend-only or non-UI work.

Core Features & Use Cases

  • End-to-end UI improvement: Design, redesign, critique, audit, harden, and polish frontend screens and components with production-grade intent.
  • UX and interface quality checks: Identify cognitive-load issues, accessibility gaps, anti-patterns, and visual or interaction inconsistencies before shipping.
  • Practical iteration workflows: Plan UX/UI first, generate or refine design direction, apply targeted enhancements (copy, layout, color, motion), and validate with audits.

Quick Start

Use impeccable to audit and improve the user experience of the "Hearing Packet" screen in the project.

Frequently Asked Questions about impeccable

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

FAQPage Schema
How do I audit my frontend UI for accessibility and visual hierarchy issues?â–¼

A frontend UI audit identifies cognitive-load issues, accessibility gaps, and visual or interaction inconsistencies before shipping. The process evaluates screens and components against structured design constraints and anti-pattern guardrails to ensure production-grade quality.

What is the best way to redesign a dashboard interface for responsive design and UX clarity?â–¼

Redesigning a dashboard for responsive design and UX clarity requires planning interactions first, applying targeted enhancements to layout and copy, and validating with hardening checks. This ensures the interface remains accessible and consistent across light and dark themes.

Can I use this workflow to polish onboarding flows and error states without touching backend logic?â–¼

Yes, you can polish onboarding flows and error states while remaining strictly UI-focused. The workflow targets copy, layout, color, and motion refinements for frontend interfaces without drifting into backend-only or non-UI development tasks.

How do you improve interaction states and performance-sensitive UI in web app components?â–¼

Improving interaction states and performance-sensitive UI involves applying targeted enhancements to component-level changes and validating with audits. This approach refines visual hierarchy and interaction consistency while maintaining responsiveness across different layouts.

When do I need to harden frontend screens before shipping to production?â–¼

You need to harden frontend screens before shipping when you must resolve visual or interaction inconsistencies, close accessibility gaps, and reduce cognitive load. This production-grade polishing step uses anti-pattern guardrails to validate UI quality.