agentleFS
rschuftrschuft/ai-frontend-skill-packs/skills/design-rhythm-and-pattern/SKILL.md

design-rhythm-and-pattern

Skill4 starsChanged 5 days agoMITView on GitHub

Repair inconsistent visual repetition and pattern across UI cards, icons, spacing, backgrounds and pages while preserving salience and avoiding overwhelming decorative rhythm.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    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. Distinctive:

    Use this specialist when the actual task involves rhythm issues.

    line 10
  2. Very specific:

    Read references/playbook.md for exact discriminating checks, implementation examples, tradeoffs and acceptance tests.

    line 20

≈ “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

Rhythm and pattern

Scope

Use this specialist when the actual task involves rhythm issues. Check documented brand/system decisions before prescribing changes. Do not conflate taste with accessibility standards or make assumptions from screenshots alone.

Affecting category: rhythm. Related governing principles: pattern, unity. Route from design-diagnose or design-review when observations match this category, or load directly during a focused implementation.

Procedure

  • inconsistent-components: Consolidate component styles and spacing into semantic tokens; permit role-based variants only. Verify: Comparison of three pages reveals consistent role treatments.
  • wall-of-identical-cards: Preserve component system but vary content weight/featured layout for genuinely different priority. Verify: Viewer can find featured item in a short scanning task.
  • pattern-overpowers-content: Reduce scale/opacity and remove texture behind readable content; avoid visual flicker. Verify: Body/controls remain legible and attention goes to content, not motif.

Read references/playbook.md for exact discriminating checks, implementation examples, tradeoffs and acceptance tests. Keep the fix within the existing component architecture. Report original observation, selected recipe and evidence. For usability, engage ux-*; for normative accessibility, engage wcag-*.

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.