agentleFS
Sign inStart free
joinwell52-AIjoinwell52-AI/CodeFlowMu-open/skills/ui-visual-consistency/SKILL.md

ui-visual-consistency

Skill2 starsChanged 4 months agoMITView on GitHub

Review CodeFlowMu UI for visual consistency, component fit, readable typography, responsive layout, and operational clarity. Use when checking Panel screens, modals, tables, filters, cards, buttons, or icons.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use during UI review or before accepting a UI design/patch.

    line 10
  2. Distinctive:

    Keep text readable and non-overlapping.

    line 15
  3. Distinctive:

    Use familiar controls for common actions.

    line 16
  4. Distinctive:

    Keep operational tools calm, dense, and scannable.

    line 17
  5. Distinctive:

    Do not create card-in-card layouts.

    line 25
  6. Distinctive:

    Do not rely on viewport-scaled text.

    line 26
  7. Distinctive:

    Do not accept UI copy that misstates state.

    line 27

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

UI Visual Consistency

When to use

Use during UI review or before accepting a UI design/patch.

Rules

  • Match existing component patterns.
  • Keep text readable and non-overlapping.
  • Use familiar controls for common actions.
  • Keep operational tools calm, dense, and scannable.

Required output

Use docs/skills/ui-playbook/visual-consistency.md.

Forbidden actions

  • Do not create card-in-card layouts.
  • Do not rely on viewport-scaled text.
  • Do not accept UI copy that misstates state.

Minimal example

Issue: action label wraps into icon
Impact: mobile overlap
Fix: icon-only button with tooltip

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.

Check your setup, free