What does the pbakaus/impeccable plugin do?

It adds the `impeccable` skill to Claude Code for shaping, critiquing, auditing, and polishing a frontend interface, plus four agents that support that work: producing assets from an approved reference, applying live browser edits back to source, reviewing a finished build, and writing up the result in DESIGN.md. Flowy's index counts 6 components for it in total.

What do the four agents in impeccable do?

`impeccable-asset-producer` turns an approved mock reference into clean, reusable image assets without changing the design. `impeccable-manual-edit-applier` applies a batch of live manual edits back to source code. `impeccable-finish-reviewer` checks a finished build against its own brief and returns an ordered list of fixes, and `impeccable-documenter` records DESIGN.md from what actually shipped.

Why does Flowy show 2 skills for a plugin with one impeccable skill?

Flowy's crawl found the `impeccable` skill indexed twice under an identical name and description, so the component count reads 2 skills even though there is a single distinct skill to install. The 4 agents are the part of the count that names four separate, real components.

Is pbakaus/impeccable only for Claude Code?

No. Its own project documentation describes support for several other AI coding tools. Flowy indexes only the Claude Code plugin surface here, the `impeccable` skill and its four agents, which is what the component counts on this page describe.

Impeccable for Claude Code: design review, assets, and docs

By Flowy · Updated 2026-08-28

pbakaus/impeccable is a Claude Code plugin for shaping and finishing a frontend interface. Its impeccable skill covers design, redesign, critique, audit, and polish work, and four agents support it: one turns an approved reference into image assets, one applies live browser edits back to source, one reviews a finished build, and one writes up the result in DESIGN.md.

What is pbakaus/impeccable

pbakaus/impeccable is a Claude Code plugin that Flowy indexes from its public GitHub repository, which carries 60,567 stars in the design category. Flowy's crawl counts 6 components for it: 4 agents, and 2 entries for the impeccable skill, which the crawl found listed twice under an identical name and an identical description.

Per that description, the skill is meant to fire whenever someone wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface, and it names websites, landing pages, dashboards, product UI, app shells, components, and forms as the surfaces it covers. The indexed description is cut off right after "forms," so this guide does not claim what the rest of that list adds.

The plugin's own summary explains the mechanism behind that long verb list: it produces UI assets, documentation, and finish reviews using AI agents inside a Svelte-based HTML flow, running on live browser iteration and pushing edits back to source through git commits. The four agents below are the specialists that flow calls on. The project behind this plugin is also bigger than what Flowy indexes here: its own documentation describes a much longer menu of design commands plus a separate command-line design linter, and neither is broken out as a component on this page.

What the four agents do

Two of the four sit at the production ends of a design pass. impeccable-asset-producer runs once a direction is already approved, turning approved mock references into clean, reusable raster assets without redesigning that direction, so it is a production step rather than a design decision. impeccable-manual-edit-applier closes the loop on the plugin's live browser mode: it takes a batch of manual copy edits made during a live session, applies them to the project's source, and returns what its description calls canonical Apply results, which is the git-commit half of the summary above.

The other two check and record the work once a build is finished. impeccable-finish-reviewer compares a finished build against its direction contract, the approved comp, and what its own description calls "the chosen world's quality bar," returning an ordered list of material fixes rather than a pass or fail verdict. impeccable-documenter then records DESIGN.md and a sidecar file from that same finished build, building the design system description from what actually shipped instead of from what was originally intended.

Why the impeccable skill is listed twice

The 2 in "2 skills" on the listing page is not two different skills. Flowy's crawl found impeccable in two places in the repository, with the same name and the same description both times, so it gets counted twice. The 4 agents are where the real variety is: four separate names, four separate jobs. If you are trying to picture the actual inventory of this plugin from Flowy's index, treat it as one skill plus four agents, with the count reflecting a repository that happens to package that skill more than once.

Who this is actually for

This plugin fits a project that treats a frontend surface as something to shape, ship, and then check, rather than a single "make it look nicer" request. The direction-contract-and-comp language in the finish reviewer's own description implies a design direction gets agreed on before a build starts, which matters less if your process is closer to open-ended iteration with no fixed target to check the result against. If you want a live browser loop where manual tweaks get pulled back into committed source, and a written record in DESIGN.md afterward, this plugin is built around exactly that path. For a single one-off fix to a component with no review or paper trail, the impeccable skill's own broad trigger list still covers the request, just without the rest of the agents doing anything.

How do I install it

Flowy indexes pbakaus/impeccable from its public GitHub repository. It does not own, host, or modify the project. Install it from the listing page linked at the top of this guide, which derives the current install command from the plugin's own manifest rather than repeating one here.

Common questions

What does the pbakaus/impeccable plugin do?: It adds the `impeccable` skill to Claude Code for shaping, critiquing, auditing, and polishing a frontend interface, plus four agents that support that work: producing assets from an approved reference, applying live browser edits back to source, reviewing a finished build, and writing up the result in DESIGN.md. Flowy's index counts 6 components for it in total.
What do the four agents in impeccable do?: `impeccable-asset-producer` turns an approved mock reference into clean, reusable image assets without changing the design. `impeccable-manual-edit-applier` applies a batch of live manual edits back to source code. `impeccable-finish-reviewer` checks a finished build against its own brief and returns an ordered list of fixes, and `impeccable-documenter` records DESIGN.md from what actually shipped.
Why does Flowy show 2 skills for a plugin with one impeccable skill?: Flowy's crawl found the `impeccable` skill indexed twice under an identical name and description, so the component count reads 2 skills even though there is a single distinct skill to install. The 4 agents are the part of the count that names four separate, real components.
Is pbakaus/impeccable only for Claude Code?: No. Its own project documentation describes support for several other AI coding tools. Flowy indexes only the Claude Code plugin surface here, the `impeccable` skill and its four agents, which is what the component counts on this page describe.
How do I install pbakaus/impeccable?: Install it from the listing page linked at the top of this guide, which derives the current install command from the plugin's own manifest. Flowy indexes the plugin from its public GitHub repository and does not host or modify it.

See the listing and install it Browse every plugin