Skip to content

github/awesome-copilot / skills/anti-ui-slop

anti-ui-slop

Unverified

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".

FileKindSize
CHECKSUMS.sha256other1.1 KB
LICENSEother10.5 KB
MANIFEST.jsonconfig448 B
MODIFICATIONS.mdmarkdown275 B
NOTICEother401 B
SKILL.mdskill md3.2 KB
agents/openai.yamlconfig235 B
reference/audit.mdmarkdown827 B
reference/distill.mdmarkdown1.1 KB
reference/ios.mdmarkdown1.2 KB
reference/new-work.mdmarkdown1.7 KB
reference/operate.mdmarkdown1.3 KB
reference/polish.mdmarkdown1.1 KB
references/uizze-reference-policy.mdmarkdown1.1 KB

reference/new-work.md

View on GitHub
# New interface or major redesign

Start from the product, not from a style trend. Read the brief, existing components, content, constraints, and any current interface before choosing a direction.

## Decide the interface

- Identify the primary user, their main task, and the one action that matters most on this surface.
- Choose one coherent visual direction that fits the product. Do not present style menus or invent novelty for its own sake.
- Establish a clear reading order: orientation, primary content, primary action, then secondary detail.
- Reuse the existing design system when one exists. Extend it only where the requested work genuinely needs something new.
- Keep familiar controls familiar. Distinction should come from the product's content, structure, typography, imagery, and interaction—not from making standard controls strange.

## Build the complete state

- Use real or clearly marked placeholder content that exercises the layout.
- Include the states required by the task: loading, empty, error, success, disabled, or recovery when they can actually occur.
- Define responsive behavior structurally. Decide what stacks, collapses, scrolls, or remains fixed instead of merely shrinking the desktop layout.
- Keep typography, spacing, color, radius, icon style, and motion internally consistent.
- Use motion only to explain a transition, reveal state, or provide feedback.

## Verify once

Render the result at the relevant sizes when the environment supports it. Fix observable clipping, overlap, distorted media, inaccessible controls, broken focus, unreadable hierarchy, or inert interactions. Stop when the requested interface works and feels coherent; do not add a separate ceremony around the work.
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 322kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 197kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 197kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 197kUpdated Claude CodeCodexVerifiedInstall