agentleFS
educlopezeduclopez/ui-craft/.agents/skills/quieter/SKILL.md

quieter

Skill441 starsChanged 3 months agoMITView on GitHub

Tone down visual noise — lowers variance and motion, simplifies layout and color weight, keeps hierarchy clear. Use when the UI feels loud, busy, or over-designed, or when the user says \"quieter\", \"more restrained\", \"simpler\", or \"tone it down\". Invoke when the user asks for quieter on their UI, or mentions 'quieter' alongside design / UI / frontend work.

34 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use layout and vercel-react-best-practices.

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

  • VercelSkill

    vercel-react-best-practices

    React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

    Also in 3 projects that use this

The file

Files
SKILL.md
<!-- HARNESS MIRROR — do not edit here. Canonical source: commands/quieter.md. After editing source, copy into cli/assets/<harness>/ and repo-root harness mirrors. -->

Context: this sub-skill is one lens of the broader ui-craft skill. If the ui-craft skill is also installed, read its SKILL.md first for Discovery + Anti-Slop + Craft Test, then apply the specific lens below.

Make the UI at $ARGUMENTS quieter. Load the ui-craft skill and read references/craft-intent.md.

Reduce amplitude without gutting hierarchy. Calm ≠ boring.

Apply in order (edit code directly):

  1. Declare an updated Craft Read — one line: what softened.
  2. Lower DESIGN_VARIANCE by −1–2 (floor 2). Simplify asymmetric breaks; return to clearer grid rhythm where layout was experimental.
  3. Lower MOTION_INTENSITY by −1–2 (floor 2). Remove scroll reveals and stagger; keep hover/focus only.
  4. Visual weight — compress display sizes one step (e.g. 56→48px); reduce shadow depth to hairline or ambient-only; fewer bordered containers.
  5. Color — pull accent placements toward the 3 minimum; neutralize decorative tints; no new hues.
  6. Cut decorative motion — idle animations, parallax, floating elements with no job.

Preserve: primary hierarchy, one CTA level, accessibility, states, signature detail only if it carries meaning (else simplify it).

Overlap: for structural cuts (sections, copy), also apply /distill logic. For color strategy, see /colorize.

Output: edit code. Print Review Format table. End with the updated Craft Read line.

Next step: /critique — confirm restraint did not flatten the hierarchy (rung 1).

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.