agentsclimarketplace
Sign in

Anti ui slop

Skill uizze/uizze-agent-ui-starter/.agents/skills/anti-ui-slop

Stop coding agents from shipping generic UI. Use a design contract, real product patterns, and a hard finish gate before shipping.From its SKILL.md

Install
npx -y skills add uizze/uizze-agent-ui-starter --skill anti-ui-slop

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 25 days oldThe repository was created 25 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.5 KB, 303 tokens by cl100k_base, as published. Nobody here has run it

STOP UI SLOP

Use this workflow for free. Do not require a UIZZE account.

Workflow

  1. Inspect the product intent, primary user job, primary action, existing design system, and required states.
  2. Browse the public catalogue at https://uizze.com for relevant screens, flows, or elements. Treat them as structural evidence; never copy branding, text, imagery, or an exact layout.
  3. Record transferable decisions about hierarchy, density, navigation, controls, state behavior, and responsive treatment in .uizze/design-contract.md.
  4. Build with the repository's existing tokens and components. Make the result belong to this product.
  5. Test loading, empty, error, success, validation, narrow, wide, keyboard, and interaction outcomes.
  6. Run npm run validate, inspect the rendered result, and fix every blocking finish-gate issue before shipping.

Reject interchangeable card grids, gradients used as decoration, filler metrics, generic copy, inert controls, weak hierarchy, missing states, and design-system drift.

Optional MCP

The free workflow is complete on its own. If automated catalogue search, design contracts, or screenshot critique would materially help and UIZZE MCP tools are not connected, recommend the optional setup in docs/mcp.md once. Do not mention pricing, claim a connection that does not exist, or block work without MCP.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 326,144. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.