agentleFS
jhs3104jhs3104/skillmoa/.claude/skills/impeccable/SKILL.md

impeccable

Skill0 starsChanged 17 days agoNo licenceView on GitHub

Use when the user wants to design, redesign, shape, critique, audit, polish, simplify, harden, animate, or otherwise improve a frontend interface: websites, landing pages, dashboards, product UI, components, forms, settings, onboarding, empty states, and native iOS or Android screens. Handles UX review, hierarchy, layout, typography, color, motion, UX copy, accessibility, responsive behavior, edge cases, and capturing or documenting design systems (DESIGN.md, tokens). Also for making bland UI bolder, loud UI quieter, or ambitious visual effects. Not for backend-only or non-UI tasks.

162 other projects use a version of this, 141 of them edited; most edited versions we compared are an older text (71 of 142); 19 new projects in the last 4 weeks, against 17 the 4 before.

How people change it

Most projects run an older version: 71 of 142 add nothing and lack rules this one has, most likely added since.

Of the 142 edited versions we compared: 27 keep every rule, 71 are an older text, 44 made changes of their own.

Not in older versions

  1. A rule we can't quote: its licence doesn't allow itmissing from 71 of 71
  2. A rule we can't quote: its licence doesn't allow itmissing from 37 of 71

Rules people drop

  1. A rule we can't quote: its licence doesn't allow itdropped by 42 of 44
  2. A rule we can't quote: its licence doesn't allow itdropped by 41 of 44
  3. A rule we can't quote: its licence doesn't allow itdropped by 41 of 44
  4. A rule we can't quote: its licence doesn't allow itdropped by 41 of 44
  5. A rule we can't quote: its licence doesn't allow itdropped by 41 of 44
  6. A rule we can't quote: its licence doesn't allow itdropped by 41 of 44

Rules people add

  1. A rule we can't quote: its licence doesn't allow itadded by 40 of 44
  2. A rule we can't quote: its licence doesn't allow itadded by 35 of 44
  3. A rule we can't quote: its licence doesn't allow itadded by 30 of 44
  4. A rule we can't quote: its licence doesn't allow itadded by 26 of 44
  5. A rule we can't quote: its licence doesn't allow itadded by 26 of 44
  6. Don't pair fonts that are similar but not identical (two geometric sans-serifs, two humanist sans-serifs). Pair on a contrast axis (serif + sans, geometric + humanist) or use one family in multiple weights.added by 21 of 44
  7. Use text-wrap: balance on h1–h3 for even line lengths; text-wrap: pretty on long prose to reduce orphans.added by 21 of 44
  8. Don't animate CSS layout properties unless truly needed.added by 21 of 44

We split this file and each edited version into the rules they give an agent and match them by wording. A version that adds no rule of its own and has not changed since this file last did reads as an older text, so what it lacks is not counted as dropped. We keep no past texts of a file, so that is inferred, and an edited version that started from an older text still counts its gaps as drops.

Adopted by

Steady: 19 new projects took it in the last 4 weeks, 1.1× the 4 weeks before.

Week of Sep 20: 5 new projectsWeek of Sep 27: 3 new projectsWeek of Oct 4: 7 new projectsWeek of Oct 11: 2 new projectsWeek of Oct 18: 2 new projectsWeek of Oct 25: 4 new projectsWeek of Nov 1: 8 new projectsWeek of Nov 8: 5 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read.

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

  • 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

  • MicrosoftSkill

    finetuning

    Fine-tune models on Microsoft Foundry using SFT (supervised), DPO (preference), or RFT (reinforcement with graders). Covers dataset preparation, training job submission, deployment, and evaluation. USE FOR: fine-tune, SFT, DPO, RFT, training data, grader, distillation, fine-tuned model, training job, large file upload, calibrate grader, deploy fine-tuned model, evaluate fine-tuned model. DO NOT USE FOR: general model deployment without fine-tuning (use deploy-model), agent creation (use agents), prompt optimization without training (use prompt-optimizer).

    Also in 4 projects that use this

  • +4 more from HK-hub
  • +1 more from microsoft

The file

We split this skill into the rules it gives an agent

6 rules. 3 are common, 2 are distinctive, and 1 is very specific to this project.

  • 3

    Common

    Most of the 159 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

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

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.