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

refine

Skill3 starsChanged 5 months agoMITView on GitHub

A shared vocabulary of named refine commands for existing UI (typeset, colorize, animate, settle, flow, bolder, quieter, distill, regroup, glass, iconify, deslop, brandward, productward, audit, critique, harden, polish). Use when the user asks to improve, fix, tighten, calm, strengthen, or polish a UI with a precise verb instead of a vague "make it better". Each command is one scoped move wired to the rest of the suite.

44 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use addskill, apply-firmware 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.
  • ryanportfolioSkill

    addskill

    Create, import, update, or install repo or personal skills: runtime ownership, resources, discovery checks.

    Also in 6 projects that use this

  • ryanportfolioSkill

    apply-firmware

    Bring current folder (plain folder, existing repo, old or partial firmware copy) up to full Harness Firmware in place. Mirror external repo → adopt-repo.

    Also in 6 projects that use this

  • +10 more from ryanportfolio

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 38 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:

    Before shipping: audit → harden → polish, then the output gate.

    line 68

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

Refine

A shared vocabulary of small, named moves you make on UI that already exists. Each command is one verb with one job. "Make it better" is vague and drifts; typeset then quieter then polish is precise, repeatable, and reviewable.

This is the granular layer of the suite. design-system creates an identity, fluid sets the motion, output gates the ship. refine is the set of verbs you use in between to push a screen from done to right.

How to invoke

The user names the verb, in their words or as a slash command:

  • "typeset this", "make the hero bolder", "calm the motion", "/polish the pricing section"

Apply exactly that move, nothing else. Do not colorize when asked to typeset. If the user named a region (a section, a component, a selection), scope to it; otherwise apply to the current view. State the change in one line, then run audit if motion or color was touched.

Commands compose. Chain them in the order the user implies, or in the natural order: structure, then type, then color, then motion, then polish. Full definitions, with what each one enforces and leaves alone, are in reference/commands.md.

The vocabulary

Type

  • typeset — repair typography: a distinctive pairing from the database, a real scale, measure under ~75 characters, tracking eased on large headings. Kills justified, sub-10px, and crushed text.
  • recase — fix casing tics: drop all-caps body, keep uppercase kickers to one if at all.

Color

  • colorize — apply or repair the palette: commit to a dominant with one rationed accent, near-black not pure black, no purple-wash gradient, body contrast 4.5:1.
  • tone — shift the mood (warmer, cooler, darker, more muted) without breaking the locks.

Motion

  • animate — add motion on purpose, with the house easings and a reduced-motion path. Reveals, heroes, hovers, counters.
  • settle — calm janky or excessive motion: instant on frequent interactions, named transitions over transition: all, scale(0.93) not scale(0), fixed transform-origin.
  • flow — give many small animations one shared physics source (one scroll velocity, one progress value) so they read as one system.

Emphasis

  • bolder — increase force: widen the type jump, raise contrast, give one element a real moment.
  • quieter — dial it down: ration the accent, hairlines over fills, more whitespace, fewer effects.

Structure

  • distill — strip slop structure: flatten nested cards, vary identical card grids, drop the icon-tile-above-every-heading and the 01/02/03 markers. Cut copy to the essential.
  • regroup — fix hierarchy and sectioning: correct heading order, group what belongs together, separate brand from product.

Surface

  • glass — apply the liquid-glass treatment to signal depth or dismissal, not as decoration.
  • iconify — replace emoji and stock icons with a consistent bespoke SVG set.

Copy

  • deslop — kill marketing buzzwords, manufactured "not X but Y" contrast, and em or en dashes. Say the concrete thing.

Register

  • brandward — push toward impression-led brand work (a landing page): more air, more type, a stronger hero moment.
  • productward — push toward task-led product UI (a dashboard): denser, calmer, faster, information-first.

Gates

  • audit — run the deterministic detector (29 rules) and report.
  • critique — qualitative review against the by-hand catalog (the structural and semantic tells the detector cannot see).
  • harden — accessibility and robustness: reduced-motion in CSS and JS, visible focus, contrast, color-scheme.
  • polish — the final craft micro-pass: press and hover feedback, optical alignment, consistent radii and spacing, the details that separate a demo from a shipped build.

Composition

  • New screen lands generic: distill → typeset → colorize → polish.
  • Motion feels off: audit → settle → flow.
  • Hero is flat: bolder → animate → polish.
  • Landing page reads like a dashboard: brandward → typeset → glass.
  • Before shipping: audit → harden → polish, then the output gate.

Wiring

These commands are not new rules. They are named entry points into rules the suite already holds.

  • typeset and colorize draw from design-system/data/ (the palette and type-pairing database) and design-system/reference/rules.md.
  • animate, settle, and flow apply the fluid SKILL rules and the house easings.
  • glass and iconify use design-system/reference/glass.md and reference/icons.md.
  • audit runs fluid/detector/detect.mjs. critique reads fluid/reference/anti-patterns.md.
  • harden and polish enforce the output checklist.

Pairs with: every skill in the suite. refine is the verb layer over all of them.

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.