impeccable

Refine frontend interfaces across design, UX critique, and technical hardening.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/LinCie/lentera-ops --skill impeccable-lincie
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: impeccable
Source: https://github.com/LinCie/lentera-ops/tree/main/.agents/skills/impeccable
Command: npx skills add https://github.com/LinCie/lentera-ops --skill impeccable-lincie

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

The impeccable skill helps you create, critique, and finalize frontend interfaces so they look intentional and behave correctly in real-world usage, including accessibility, performance, responsive layout, and edge cases.

Core Features & Use Cases

  • End-to-end frontend design improvements: redesign and polish UI for landing pages, dashboards, app shells, forms, settings, onboarding, and empty/error states.
  • UX and UI quality passes: critique, audit, and refine with specific guardrails on hierarchy, typography, spacing, theming, and anti-patterns.
  • Production hardening: address validation, long text, loading and error states, i18n/RTL, and resilient interactions so the UI holds up under imperfect data.
  • Optional enhancement workflows: add purposeful motion and micro-interactions, strengthen layout rhythm, improve copy clarity, colorize monochrome designs, and improve typography.

Quick Start

Tell the assistant what UI you want to improve (page/component) and what outcome you want, for example: "Shape a clearer onboarding for the dashboard settings page and then critique it for accessibility and hierarchy."

Frequently Asked Questions about impeccable

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

FAQPage Schema
How do I harden frontend UI for accessibility and responsive design in production?

To harden frontend UI for accessibility and responsive design in production, you critique and refine interfaces using deterministic rules. This process enforces guardrails for hierarchy, theming, and motion constraints to ensure correct real-world behavior across edge cases.

What is the best way to audit empty and error states for dashboard components?

Auditing empty and error states for dashboard components involves running a production hardening pass. This validates long text handling, loading states, and resilient interactions so the UI holds up correctly under imperfect data conditions.

Can I use this approach to improve i18n and RTL layout behavior for web forms?

Yes, you can improve i18n and RTL layout behavior for web forms through targeted UI hardening. This addresses validation, localized text expansion, and interaction resilience to ensure forms behave correctly across different languages and reading directions.

Do I need a design system setup to critique and refine my landing page UX?

You do not need a design system setup to critique landing page UX, but providing a PRODUCT.md file is required for deterministic context. An optional DESIGN.md file can further enhance design-system tokenization workflows during the refinement process.

Why does my UI layout break when handling long text and loading states?

Your UI layout breaks when handling long text and loading states due to missing production hardening guardrails. Applying UX quality passes addresses validation, edge cases, and resilient interactions to prevent visual breakage under imperfect data loads.