impeccable

Designs, critiques, and refines production-grade frontend interfaces through structured commands.

Updated Jun 16, 2026
One-click install
npx skills add https://github.com/Arthakula/arthakula-landingpage --skill impeccable-arthakula
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: impeccable
Source: https://github.com/Arthakula/arthakula-landingpage/tree/main/.gemini/skills/impeccable
Command: npx skills add https://github.com/Arthakula/arthakula-landingpage --skill impeccable-arthakula

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Frontend interfaces built quickly often suffer from generic AI-generated aesthetics, weak visual hierarchy, accessibility gaps, and inconsistent design systems. This Skill provides a structured workflow for designing, auditing, and polishing UI so the output looks intentional and distinctive rather than templated. ## Core Features & Use Cases - Command-driven design workflow: Over 20 sub-commands (craft, shape, audit, polish, bolder, quieter, typeset, layout, animate, colorize, and more) each load a dedicated reference file defining a step-by-step flow for building, evaluating, refining, or fixing UI. - Anti-slop design rules: Enforces concrete bans on saturated AI patterns (gradient text, side-stripe borders, glassmorphism, eyebrow kickers, cream backgrounds) plus typography, color, motion, and accessibility guidelines with WCAG contrast requirements. - Context-aware setup: Scripts detect project context (PRODUCT.md, DESIGN.md), generate brand palette seeds in OKLCH, and route work to brand or product registers based on the surface being designed. - Use Case: A developer building a Nuxt landing page runs the audit command to score accessibility, performance, theming, responsiveness, and anti-patterns, then applies the polish and typeset commands to fix the findings before shipping. ## Quick Start Ask the assistant to use the impeccable skill to critique the landing page and suggest the highest-value design improvements.

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-looking landing page design?

Use the bolder command to amplify safe designs through stronger hierarchy, committed scale, and decisive typography, or the colorize command to introduce a strategic palette. Both commands reject saturated AI defaults like purple-blue gradients and glassmorphism before amplifying.

How to audit frontend UI for accessibility and performance issues?

Run the audit command, which scores five dimensions (accessibility, performance, theming, responsive design, anti-patterns) from 0-4 each and produces a report with P0-P3 severity-tagged findings. Each finding maps to a recommended follow-up command for fixing it.

What is the difference between the critique and audit commands?

Critique performs a UX design review with heuristic scoring focused on design quality, while audit runs technical code-level checks on measurable issues like contrast ratios, touch targets, and layout thrashing. Audit documents issues without fixing them.

Does this design workflow support dark mode and theming?

Yes, the color guidance covers two-layer token systems with primitive and semantic tokens, where dark mode redefines only the semantic layer. It specifies OKLCH color space, tinted neutrals, and surface elevation scales for dark themes.

When should I not use this frontend design skill?

It is not suited for backend-only or non-UI tasks, as its entire workflow targets visual interfaces. It also defers to existing committed brand identities rather than replacing them, so it preserves established design systems instead of forcing redesigns.