Audit an existing interface
Use a targeted audit or critique to identify hierarchy, interaction, accessibility, or responsive issues in a known screen.
Impeccable by pbakaus
Use Impeccable by pbakaus to design, critique, and refine frontend interfaces through one Skill and its commands. Review hierarchy, typography, responsive behavior, and edge cases, preserve the project’s intended identity, and inspect rendered results as you improve the surface for its actual users.
Install and get started
Choose your agent to see how to get started. In Floatboat, copy a request that asks the agent to read the original instructions. Other options show the Skill installation command or the publisher’s native setup steps.
Choose an agent
Start in Floatboat
Copy the request into a Floatboat conversation
Read the original Impeccable instructions at https://github.com/pbakaus/impeccable/blob/main/.agents/skills/impeccable/SKILL.md. Explain its purpose, required tools, and installation options, then help me use it.Let the agent read the original instructions and check how to use them in your environment.
Download Floatboat ↗Try this request
Use Impeccable to audit this checkout form. Preserve the existing visual identity, focus on hierarchy, keyboard use, validation, and empty or error states, and report findings before editing.
About Impeccable
Impeccable is a design Skill and supporting tool workflow published by pbakaus. Its single Skill routes interface tasks to commands such as audit, critique, polish, and harden, rather than treating each command as a separate capability package. The current distribution includes a launcher and a self-contained engine, with provider-specific installation and optional native hooks. It reads project context to distinguish refinement from redesign and adjusts the approach to the type of surface. Use it with a concrete interface, a user task, and the identity or behavior that must remain. Installation details differ by host, and rendered verification remains part of the design work.
Use Cases for Impeccable
Explore interface work with a specific quality problem or a clear redesign goal. Audit a working screen, polish a nearly finished page, or harden forms and empty states, choosing the command that matches the task while keeping existing product truth and user behavior in view.
Polish a nearly finished page
Refine typography, alignment, spacing, and consistency while preserving the interface direction and behavior that already work.
Harden form and edge states
Review validation, errors, loading, and empty states so the page continues to guide users when ordinary input or data is missing.
How to Use Impeccable
Install Impeccable for your host, then initialize a new project with /impeccable init or check its existing product context. Give the agent a specific interface task, distinguish refinement from redesign, and inspect the rendered result at representative sizes before accepting changes.
- 01
Install and initialize the project
Use the provider-specific installer and reload the host. In a new project, run /impeccable init inside the agent to establish PRODUCT.md; for an existing project, review that context and follow any hook-trust prompts.
- 02
Scope the interface task
Provide the route or source file and explain what must remain. Choose the relevant command and distinguish refinement from redesign.
- 03
Review rendered changes
Inspect the updated interface at the sizes it supports. Verify interaction and content, then refine the issues that the rendered result reveals.
Explore More Agent Skills
Read another Skill guide and check its original source before using it.
Impeccable FAQ
Are audit and polish separate Skills?
In the current distribution, commands route through the single impeccable Skill. Standalone shortcuts can be pinned, but that does not make each command an independent package.
Does a plain SKILL.md copy install the complete setup?
No. The current workflow includes references, a launcher, an engine, and provider-specific packaging. Use the documented installer or complete distribution for your host rather than copying only the entry file.
Why does installation mention hooks?
Some providers receive native hooks in addition to the Skill. Their trust and activation rules differ by host; follow the upstream verification instructions and review any requested project hook approval.
Does Impeccable require Node at runtime?
The README describes a self-contained engine launched by a small script. Node is used by the npx installer path; the manual and Git setup paths have different requirements. The engine may be downloaded on first use.
Will a refinement request replace my whole design?
The source distinguishes refinement from redesign. State which identity, content, behavior, and scope must stay; a refinement should work within those constraints rather than silently choosing a new visual world.
Can I use it when the app cannot run locally?
The source allows inspecting existing visual evidence and project context, but freshness and correspondence matter. Mark what cannot be rendered or verified instead of presenting a source-only review as a tested interface.