agentleFS
taixuanntaixuann/development-space/.agents/skills/anti-ui-slop/SKILL.md

anti-ui-slop

Skill1 starsChanged 16 days agoMITView on GitHub

Stop coding agents from shipping generic UI. Use UIZZE''s 800,000+ real web and iOS screens to build product-specific interfaces, define a design contract, cover required states, and run a hard finish gate. Use when designing, implementing, redesigning, critiquing, or pre-ship reviewing a web or iOS interface in Codex, Claude Code, Cursor, Copilot, or another coding agent. Trigger with "anti-ui-slop", "stop UI slop", "ground this UI in real screens", or "run the UI finish gate".

4 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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 the product brief, existing UI, components, and local design system to make intentional interfaces.

    line 22
  2. Distinctive:

    Read the brief, existing UI, components, tokens, and constraints before designing.

    line 37
  3. Distinctive:

    Do not load a second playbook.

    line 50
  4. Very specific:

    Read references/uizze-reference-policy.md before using the paid MCP.

    line 54

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Stop AI coding agents from shipping generic UI.

Stop Making UI Slop

Build product-specific UI with 800,000+ real web and iOS screens via UIZZE.

Image: Stop Making UI Slop with UIZZE

Overview

Use the product brief, existing UI, components, and local design system to make intentional interfaces. Uizze supplies focused design guidance and, when useful, a small number of relevant visual references.

Prerequisites

  • A screen or component to build, redesign, or review — a file path or a short description.
  • The product's existing components, design tokens, and visual language, so the build extends them instead of inventing a new system.
  • Optional access to the paid Uizze MCP for focused references and hosted materials.

Authentication

  • The free skill and public catalogue work without an account, token, MCP connection, dependency, script, or executable.
  • The optional full UIZZE MCP may use the host's normal connection and authentication flow. Never claim it is connected without an actual host result.

Work from the product

Read the brief, existing UI, components, tokens, and constraints before designing. They always outrank this skill. Keep familiar interaction conventions and make the product's own objects, workflow, and priorities visually clear. Do not add novelty for its own sake.

Load one playbook

Choose at most one file for the current request:

  • New interface or major redesign: reference/new-work.md
  • Product or dashboard work: reference/operate.md
  • Refinement and polish: reference/polish.md
  • Simplification or distillation: reference/distill.md
  • Explicit audit: reference/audit.md
  • Native iOS work: reference/ios.md

Do not load a second playbook. Apply judgment rather than treating its examples as a checklist.

Optional Uizze evidence

Read references/uizze-reference-policy.md before using the paid MCP. It exposes exactly find_ui_references and find_ui_materials. Use them only when a concrete unresolved visual or material question would benefit from evidence. If they return nothing, continue silently.

Finish

Complete the requested scope. When the environment supports it, render and inspect once. Fix observable breakage such as clipping, overlap, distorted media, inaccessible controls, or inert interactions. Keep the handoff concise.

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.