agentleFS
Michael-cmd-sysMichael-cmd-sys/claude-skills/refactoring-ui/SKILL.md

refactoring-ui

Skill0 starsChanged 7 months agoNo licenceView on GitHub

Apply the design principles from Adam Wathan and Steve Schoger's Refactoring UI book to build clean, professional, polished interfaces. Use this skill whenever building, refining, or critiquing any UI — web pages, components, dashboards, forms, landing pages, artifacts, mockups, marketing sites, app screens — even when the user does not explicitly ask for 'design help'. Trigger on cues like 'make this look better', 'why does this look amateur', 'design a [page/component]', 'build me a [dashboard/landing page/form]', 'style this UI', or any task that produces visual output where polish matters. The skill provides systematic rules for hierarchy, spacing, type scales, color palettes, depth/shadows, imagery, and finishing touches. Use it together with the frontend-design skill when bold aesthetic direction is also needed; this skill handles foundational craft, frontend-design handles distinctive visual character.

20 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use prototype and grill-me.

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.
  • GoogleSkill

    prototype

    Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.

    Also in 4 projects that use this

  • GoogleSkill

    grill-me

    A relentless interview to sharpen a plan or design.

    Also in 4 projects that use this

The file

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. 0 are common, 11 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 19 edited versions we read keep these.

  • 11

    Distinctive

    This author's own choices. Worth a look.

  • 2

    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 19 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.