agentleFS
Sign inStart free
podopodo/design-agent-skills/skills/impeccable/SKILL.md

impeccable

Skill32 starsChanged 6 months agoMITView on GitHub

Design fluency for frontend development. One skill with a suite of slash commands (/impeccable polish, /impeccable audit, /impeccable critique, etc.), curated anti-pattern detection, and a runtime launcher script. Covers UI design, redesign, critique, accessibility, motion, theming, typography, and component craft across websites, dashboards, and apps.

168 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use cloud-architecture-diagram, shelra-workspace-quality and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MicrosoftSkill

    cloud-architecture-diagram

    Create, edit, or troubleshoot Azure-first architecture diagrams as editable draw.io files, with AWS and multicloud topology support and identity, API, and CI/CD flow diagrams. Use for architecture visualization, network boundaries, interaction flows, or missing diagram icons. Not for deploying infrastructure, live cloud discovery, security certification, or unrelated charts.

    Also in 3 projects that use this

  • ShelraSkill

    shelra-workspace-quality

    Audit or refine ShelraCode's main OpenTUI coding workspace when chat activity, live status, plan/context sidebar, agent visibility, or verification UX must match a supplied visual specification. Do not use for onboarding, settings, or unrelated screens.

    Also in 3 projects that use this

  • owshq-mecSkill

    layout

    Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy. Use when the user mentions layout feeling off, spacing issues, visual hierarchy, crowded UI, alignment problems, or wanting better composition.

    Also in 8 projects that use this

  • FldicoahkiinSkill

    contribute-catalog

    Author a new HyperFrames registry block (caption style, VFX block, transition, lower third) or component (text effect, overlay, snippet) and ship it as an upstream PR to the hyperframes repo. Use ONLY when the user wants to CONTRIBUTE to the public catalog — for in-project caption/transition authoring use the `hyperframes` skill, for installing existing registry items use the `hyperframes-registry` skill.

    Also in 3 projects that use this

  • HK-hubSkill

    overdrive

    Pushes interfaces past conventional limits with technically ambitious implementations — shaders, spring physics, scroll-driven reveals, 60fps animations. Use when the user wants to wow, impress, go all-out, or make something that feels extraordinary.

    Also in 11 projects that use this

  • HK-hubSkill

    bolder

    Amplify safe or boring designs to make them more visually interesting and stimulating. Increases impact while maintaining usability. Use when the user says the design looks bland, generic, too safe, lacks personality, or wants more visual impact and character.

    Also in 12 projects that use this

  • +3 more from HK-hub

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 167 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run /impeccable <command> <target>, and /impeccable init once per project to capture PRODUCT.md

    line 71

“Common” is measured: kept by at least 6 in 10 of the 167 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

impeccable

Catalogue stub — full skill: pbakaus/impeccable

<!-- das:install:start — generated from stub.yaml by `npm run generate`; edit stub.yaml, not this block -->

Decision tree

  1. Is the full skill already installed?
    • Global: f=~/.agents/skills/impeccable/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer"
    • Project: f=.agents/skills/impeccable/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer"
    • installed → the skill is installed as impeccable, invoke it and proceed
    • pointer → go to step 2

  2. Detect scope, then install:

    [ -e ~/.agents/skills/impeccable ] && echo "global" || echo "project"

    Global:

    npx skills add pbakaus/impeccable --skill impeccable -g -y

    Project:

    npx skills add pbakaus/impeccable --skill impeccable -y

    Claude Code: send a command as a chat message starting with ! to run it without leaving the conversation.

Claude Code plugin route:

/plugin marketplace add pbakaus/impeccable
/plugin install impeccable@impeccable

Heads-up

  • Requires: the skill's launcher (scripts/impeccable) downloads a native engine binary to ~/.impeccable/bin on first run; anonymous usage telemetry is on by default (opt out with IMPECCABLE_NO_TELEMETRY=1 or DO_NOT_TRACK=1)
  • License: Apache-2.0
  • Large download (~854 MB): the skills CLI gives up cloning after 300 s; if it times out, retry with SKILLS_CLONE_TIMEOUT_MS=900000.
<!-- das:install:end -->

Invoke after install

  • Skill name: impeccable
  • Run /impeccable <command> <target>, and /impeccable init once per project to capture PRODUCT.md
  • Restart your agent session after installing so the skill and commands load

npx skills add installs the skill only. Upstream's own installer (npx impeccable install) also registers edit hooks that run the design detector after UI file edits; review those hooks before using it.

What it does

A single skill whose commands are invoked as /impeccable <command>:

CommandPurpose
shapePlan UX/UI before writing code
init / documentCapture product context (PRODUCT.md) and generate DESIGN.md from existing code
critiqueUX design review with heuristic scoring
auditTechnical quality checks (accessibility, performance, responsive)
polishFinal quality pass before shipping
bolder / quieter / distillAmplify, calm down, or simplify a design
animate / colorize / typeset / layout / delightTargeted enhancement passes
harden / onboard / clarify / adapt / optimizeEdge cases, first-run flows, UX copy, responsiveness, performance
live / generatePick elements in the browser and iterate on variants
+ moreSee the upstream README and the skill's command table

It also ships a detector for design anti-patterns that can run from the command line. Commands read PRODUCT.md for durable product context; missing it, the skill runs init for a new surface rather than guessing.

When NOT to use

  • Backend, API, or data-pipeline work
  • Non-UI tasks (routing, auth, database)
  • Deep color-science work such as OKLCH palette generation (use color-expert)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free