impeccable

Designs, critiques, audits, and refines frontend interfaces across web and native platforms.

Updated Oct 7, 2022
One-click install
npx skills add https://github.com/tamagusko/linux-cfg --skill impeccable-tamagusko
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: impeccable
Source: https://github.com/tamagusko/linux-cfg/tree/main/dotfiles/claude/skills/impeccable
Command: npx skills add https://github.com/tamagusko/linux-cfg --skill impeccable-tamagusko

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Frontend design work often ships bland, generic, or inconsistent interfaces because AI assistants default to safe patterns. This Skill provides a structured design workflow with commands for building, evaluating, refining, and fixing UI so interfaces reach a deliberate, product-specific quality bar. ## Core Features & Use Cases - Command-driven design workflow: 20+ commands such as shape, critique, audit, polish, bolder, quieter, animate, typeset, and harden, each backed by a dedicated reference playbook. - Web and native platform support: Separate guidance for web, iOS, and Android, including platform conformance checks, safe-area handling, and Material/HIG alignment. - Persistent design context: Captures product strategy in PRODUCT.md and visual systems in DESIGN.md so every command works from confirmed brand and token decisions. - Use Case: A developer asks to redesign a landing page; the Skill loads the product context, deals concept directions via its seed script, builds the surface, then runs audit and polish passes with scored accessibility, performance, and responsive findings. ## Quick Start Ask the assistant to use the impeccable skill to critique and polish the main landing page of your project.

Frequently Asked Questions about impeccable

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

FAQPage Schema
When should I not use this Skill?

Do not use it for backend-only or non-UI tasks; its commands and references all target frontend interfaces. It also requires a project context to be most effective, so one-off questions unrelated to a UI surface gain little from it.