agentleFS
Darcos-LoftDarcos-Loft/fluid/redesign/SKILL.md

redesign

Skill3 starsChanged 5 months agoMITView on GitHub

Audit an existing web UI and produce a modernization plan plus a fresh design system. Use when a site or app already works but looks dated or generic and needs a proper visual audit and a redesign pass, not a rebuild from scratch. Preserves content, routes, and SEO.

14 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use critique, decide and 1 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.
  • GoogleSkill

    critique

    Expertise in auditing and fixing repository scripts and GitHub Actions workflows to ensure technical robustness and security.

    Also in 4 projects that use this

  • dirienSkill

    decide

    Three-agent adversarial debate protocol for strategic decisions. Two advocates steelman opposing positions while a moderator identifies risks and synthesizes a binding consensus. Use when choosing between alternatives, evaluating tradeoffs, or making high-stakes decisions.

    Also in 3 projects that use this

  • HK-hubSkill

    polish

    Performs a final quality pass fixing alignment, spacing, consistency, and micro-detail issues before shipping. Use when the user mentions polish, finishing touches, pre-launch review, something looks off, or wants to go from good to great.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 14 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    Audit: Run the fluid detector on the codebase (or read the live DOM and CSS).

    line 17
  2. Very specific:

    Re-skin, do not rebuild: Keep the markup and structure, swap the look: tokens, type, motion.

    line 21
  3. Very specific:

    Pre-flight: Run the detector again, check design-system/reference/rules.md (locks, hero discipline, bans).

    line 22

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

Redesign

Audit-first. For a site that already works but looks templated or dated, this finds what is wrong, decides what to keep, and ships a committed new identity, without throwing away working structure.

When to use

  • An existing site (Webflow, WordPress, an old React app) needs to look current.
  • A client hands you a live URL and wants it modernized.
  • A redesign that must preserve content, SEO, and routes.

The workflow

  1. Audit. Run the fluid detector on the codebase (or read the live DOM and CSS). Catalogue the generic-look tells: fonts, palette, spacing, shadows, the slop list. Note what is genuinely good and worth keeping.
  2. Draw the keep/change line. Preserve: content, information architecture, routes, anything that converts. Change: the identity (palette, type, surface, motion), the layout repetition, the bans.
  3. Generate the new identity with the design-system skill. Brief it from the brand, pick from data/, commit. Two redesigns in the same sector get different palettes.
  4. Map old to new. A token migration: old hardcoded values become new CSS variables, component by component. Keep a small table so nothing is missed.
  5. Re-skin, do not rebuild. Keep the markup and structure, swap the look: tokens, type, motion. Add fluid motion where it earns its place.
  6. Pre-flight. Run the detector again, check design-system/reference/rules.md (locks, hero discipline, bans). Produce a before/after so the value is visible.

Rules

  • Preserve what converts. A redesign that drops content or breaks routes is a rewrite, not a redesign.
  • One identity, committed. Never half-redesign (new colors on old fonts).
  • Show the before and after.

Pairs with: design-system (the new identity), fluid (the motion and the detector audit).

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.