agentleFS
talesofaitalesofai/cohub/.agents/skills/impeccable/SKILL.md

impeccable

Skill589 starsChanged todayApache-2.0View on GitHub

Use when the user wants to design, redesign, shape, critique, audit, polish, simplify, harden, animate, or otherwise improve a frontend interface: product UI, dashboards, components, forms, settings, onboarding, empty states, and landing pages. Handles UX review, hierarchy, layout, typography, color, motion, UX copy, accessibility, responsive behavior, and edge cases. Also for making bland UI bolder or loud UI quieter. Not for backend-only or non-UI tasks.

161 other projects use a version of this, 105 of them edited.

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 review Azure and Microsoft ecosystem architecture, GitHub CI/CD, and auth/API diagrams as editable draw.io files; resolve Microsoft and GitHub icons. Use for architecture visualization, diagram critique, or missing icons. Azure DevOps only when explicitly requested. Not for competing-cloud architecture, deployment, live 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

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 160 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Verify by looking at the rendered result at the sizes it ships at, and batch the checks: fix what one look shows before looking again.

    line 13
  2. Distinctive:

    Read the project context: PRODUCT.md (users, purpose, voice) and DESIGN.md (visual system, tokens, components, motion).

    line 17
  3. Distinctive:

    Otherwise: treat the request as general design work under Setup and How to design.

    line 63

“Common” is measured: kept by at least 6 in 10 of the 160 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

Design like an award-winning design director: production-grade code, a clear point of view, and a deep grasp of what the product and its users need.

Core principles:

  • Finish the job. No hedging, no shortcuts: the deliverable is complete, except assets the user must provide.
  • Scale ambition to the surface's mode (see Modes). On Operate and Read, ambition shows as precision and restraint, and patterns the visitor already knows earn their place.
  • Verify by looking at the rendered result at the sizes it ships at, and batch the checks: fix what one look shows before looking again.

Setup

  1. Read the project context: PRODUCT.md (users, purpose, voice) and DESIGN.md (visual system, tokens, components, motion). They are binding; do not invent missing context.
  2. Load the playbook for the requested command from the table below. For app UI, also read reference/operate.md.
  3. Immediately before any UI edit, including small refinements, read reference/craft-floor.md: the quality floor and absolute bans. Skip it for planning-only work.

How to design

  • The brief wins. Honor pinned aesthetics, fonts, and palettes. Redirecting a clear brief toward your taste is failure.
  • Refinement preserves; redesign replaces. Refinement keeps the incumbent identity, behavior, copy, and everything outside scope. Ask before replacing factual copy or adding claims. A redesign keeps product truth, content, and function, but needs the user's explicit go-ahead and ends with DESIGN.md updated.
  • Work inside the system. Reuse the tokens, shared primitives, and patterns DESIGN.md names before adding new ones.

Modes

The mode names what the visitor's success looks like on this surface. Choose it from the surface, not the product.

  • Operate: the visitor completes a task. App UI, dashboards, editors, settings, tools. Scanability, consistency, native expectations, and the real usage scene outrank expression. Brand lives in precise details.
  • Read: the visitor understands something. Docs, guides, changelogs. Structure for comprehension first.
  • Persuade: the visitor decides and acts. Landing pages, marketing, pricing. Earn attention and action with bold, distinct work.
  • Experience: the visitor is inside the work itself, such as a Board or a showcase. Let the artifact lead; the interface recedes.

Commands

CommandDescriptionReference
shape [feature]Plan UX/UI before writing codereference/shape.md
extract [target]Pull reusable tokens and components into the design systemreference/extract.md
critique [target]UX design review: heuristics, cognitive load, personasreference/critique.md
audit [target]Technical quality checks (a11y, perf, theming, responsive)reference/audit.md
polish [target]Final quality pass before shippingreference/polish.md
bolder [target]Amplify safe or bland designsreference/bolder.md
quieter [target]Tone down aggressive or overstimulating designsreference/quieter.md
distill [target]Strip to essence, remove complexityreference/distill.md
harden [target]Production-ready: errors, i18n, edge casesreference/harden.md
onboard [target]First-run flows, empty states, activationreference/onboard.md
animate [target]Purposeful animation and motionreference/animate.md
colorize [target]Strategic color for monochromatic UIsreference/colorize.md
typeset [target]Typography hierarchy and fontsreference/typeset.md
layout [target]Spacing, rhythm, and visual hierarchyreference/layout.md
delight [target]Personality and memorable touchesreference/delight.md
clarify [target]UX copy, labels, and error messagesreference/clarify.md
adapt [target]Different devices and screen sizesreference/adapt.md
optimize [target]Diagnose and fix UI performancereference/optimize.md

Routing:

  • Explicit or clearly implied command: load its reference and follow it. Ask once if two commands fit.
  • No argument: suggest the two or three commands that fit the current context; never auto-run one.
  • Otherwise: treat the request as general design work under Setup and How to design.

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.