agentleFS
kelgirechandrakant-cpukelgirechandrakant-cpu/vibe-coding-playbook/skills/anti-slop-ui/SKILL.md

anti-slop-ui

Skill4 starsChanged 3 months agoMITView on GitHub

Enforces human design standards and prevents generic AI styling patterns in frontend code.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. KaueTartari/anti-slop-ui★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository13 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    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:

    When generating frontend components, AI coding agents default to generic, low-effort aesthetics: washed-out purple/indigo gradients, …

    line 8
  2. Distinctive:

    Follow these rules to produce interfaces that look engineered by a human product designer:

    line 10
  3. Distinctive:

    No generic font stacks: Avoid defaulting to Inter everywhere.

    line 13
  4. Distinctive:

    WCAG Compliance: Always verify text-to-background contrast ratio ($\ge 4.5:1$ for normal text, $\ge 3:1$ for large text).

    line 19
  5. Distinctive:

    Touch Target Law: Every clickable button, drawer toggle, and icon link must have a minimum touch target of $\ge 44 \times 44\text{ CSS …

    line 23
  6. Distinctive:

    Stage Containment: When displaying fixed-aspect-ratio canvases (e.g.

    line 25
  7. Very specific:

    Never animate width, height, top, left, or margin during user interaction, as this forces browser layout recalculation.

    line 32

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

Anti-Slop UI & Frontend Taste Skill

When generating frontend components, AI coding agents default to generic, low-effort aesthetics: washed-out purple/indigo gradients, floating low-contrast cards, and broken mobile hit targets.

Follow these rules to produce interfaces that look engineered by a human product designer:

1. Typography & Hierarchy

  • No generic font stacks: Avoid defaulting to Inter everywhere. Use intentional, editorial, or clean monospace font hierarchies where appropriate.
  • Strict Scale Contrast: Make section titles decisively distinct from body text.
  • Comfortable Line Height: Body text should maintain leading-relaxed (1.6 to 1.7) and line length between 60–75 characters.

2. Color & Contrast Defense

  • Banned: Multi-colored radial gradients behind dark text.
  • WCAG Compliance: Always verify text-to-background contrast ratio ($\ge 4.5:1$ for normal text, $\ge 3:1$ for large text).
  • Restrained Palettes: Stick to a single primary brand color, a dark neutral (slate-900 / zinc-900), and a light neutral (slate-50 / zinc-50). Use accent colors sparingly for primary calls to action.

3. Mobile-First Interaction

  • Touch Target Law: Every clickable button, drawer toggle, and icon link must have a minimum touch target of $\ge 44 \times 44\text{ CSS pixels}$ (WCAG 2.2 AAA / Apple HIG).
  • Thumb-Zone Controls: On mobile screens ($< 768\text{px}$), use bottom-sheet drawers (MobileEditSheet) instead of cramped sidebars.
  • Stage Containment: When displaying fixed-aspect-ratio canvases (e.g. 16:9 slides, video players, A4 documents), never let them stretch or clip:
    fitScale = Math.min((containerWidth - 32) / baseWidth, (containerHeight - 32) / baseHeight, 1.0);

4. Animation Without Layout Shift (CLS)

  • Animate only transform and opacity.
  • Never animate width, height, top, left, or margin during user interaction, as this forces browser layout recalculation.

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.