Code Review & Testing · IN-DEPTH PROFILE

Anti UI Slop Skill

Instruction-only, product-specific UI design contracts with optional real-interface evidence and a hard finish gate.

View listed source ↗Installation guide ↓
Best for

Product teams fighting generic generated UI

What you get

Inspect the product + Build a design contract

Main limitation

Repository evidence is required; UIZZE references or user-provided screenshots are optional, and missing reference evidence should be labeled rather than guessed.

First risk

Copying external interface patterns too literally. Reference browsing can pull proprietary wording, branding, or layout into the product. Transfer principles and workflow structure only, record sources, and preserve the product's own visual language.

EVIDENCE FRESHNESS

Three checks, kept separate

A recent source check is not a runtime test or security audit.

Upstream sourceChecked 2026-09-24

Pinned revision · 1f564408

Open pinned commit ↗
SkillSignal profileEditorial metadata

Updated 2026-09-24

Runtime & securityNot independently verified

Source review does not certify behavior or safety.

IN PLAIN ENGLISH

What it does—and when it fits

Anti UI Slop is an instruction-only workflow for Codex, GitHub Copilot, Claude Code, and Cursor that makes web and iOS interfaces visibly specific to the product. It combines repository evidence, optional public real-interface references, a concrete design contract, complete state handling, and a finish gate for responsiveness and accessibility; it does not require credentials or execute third-party code.

This is aimed at Product teams fighting generic generated UI. Compare the examples below with your task, then review the limitations, permissions, and risks before installing.

What you get
  • Inspect the productIdentify the user job, primary action, real nouns, states, and existing design system.
  • Build a design contractTranslate three to five relevant references into product-specific hierarchy and behavior rules.
  • Run the finish gateBlock completion on generic patterns, inert controls, missing states, or accessibility failures.
What makes it different
  • Connects visual decisions to the real user job instead of generic aesthetics.
  • Makes responsive, state, and accessibility completeness part of the design contract.
Community signalNo attributed third-party rating yet

No verified review text is in the current dataset. Use the linked source for the latest discussion.

Read the source note ↗

INSTALL BY AGENT

Choose your Agent

Paths come from official Agent docs or the universal installer behind skills.sh. Compatibility still follows this Skill's record.

Native

This Skill's current record explicitly names this Agent. Still inspect scripts, permissions, and external dependencies first.

Project install (recommended)
npx skills add github/awesome-copilot --skill anti-ui-slop --agent claude-code
Personal install
npx skills add github/awesome-copilot --skill anti-ui-slop --agent claude-code -g

Project install stays with this repository for team sharing. Personal install adds -g and works across repositories.

View install paths
Project path.claude/skills/anti-ui-slop/
Personal path~/.claude/skills/anti-ui-slop/
Official agent docs

Claude Code discovers custom Skill folders automatically at project or personal scope.

View path evidence ↗

TYPICAL WORKFLOW

A practical workflow

01

Inspect the product

Identify the user job, primary action, real nouns, states, and existing design system.

02

Build a design contract

Translate three to five relevant references into product-specific hierarchy and behavior rules.

03

Run the finish gate

Block completion on generic patterns, inert controls, missing states, or accessibility failures.

THE TRADEOFFS

Advantages and tradeoffs

Notable strengths

  1. Connects visual decisions to the real user job instead of generic aesthetics.
  2. Makes responsive, state, and accessibility completeness part of the design contract.

Limitations

  1. Repository evidence is required; UIZZE references or user-provided screenshots are optional, and missing reference evidence should be labeled rather than guessed.
  2. Reference-driven design still requires judgment and cannot prove usability without user research.

COMPARE THE TRADEOFF

Consider these close alternatives

These are deterministic nearby candidates, not paid placements or a universal ranking. Open the full profile before choosing.

01

Same job family · native to GitHub Copilot + Codex

bug-receipt

Close defects with a structured diagnosis and verification receipt.
Tradeoff to check
Detailed package files are not fully catalogued.
First risk
Review before install · Medium
Source state
Pinned · 1f564408
Open bug-receipt profile ↗
02

Same job family · native to GitHub Copilot + Codex

csharp-async

Apply safe, modern asynchronous programming patterns in C#.
Tradeoff to check
Detailed package files are not fully catalogued.
First risk
Review before install · Medium
Source state
Pinned · 1f564408
Open csharp-async profile ↗
03

Same job family · native to GitHub Copilot + Codex

csharp-mstest

Write modern MSTest tests with data-driven patterns.
Tradeoff to check
Detailed package files are not fully catalogued.
First risk
Review before install · Medium
Source state
Pinned · 1f564408
Open csharp-mstest profile ↗
Compare more in the directory →

BEST FIT

Who it is for

→

Product teams fighting generic generated UI

→

Frontend and iOS developers defining a verifiable design direction

BEFORE YOU USE IT

Risks to review before use

Medium

Copying external interface patterns too literally

Reference browsing can pull proprietary wording, branding, or layout into the product. Transfer principles and workflow structure only, record sources, and preserve the product's own visual language.

SECURITY

What the permission profile means

  • The indexed workflow is instruction-only and does not require credentials or execute third-party code; still do not expose private product data while searching public references.
  • Treat external screenshots as design evidence, not permission to copy assets.

Not a security certification. External ratings are attributed references. SkillSignal has not independently executed or security-reviewed this Skill.

COMMON QUESTIONS

Anti UI Slop Skill FAQ

What is the Anti UI Slop Skill?

Instruction-only, product-specific UI design contracts with optional real-interface evidence and a hard finish gate. Anti UI Slop is an instruction-only workflow for Codex, GitHub Copilot, Claude Code, and Cursor that makes web and iOS interfaces visibly specific to the product. It combines repository evidence, optional public real-interface references, a concrete design contract, complete state handling, and a finish gate for responsiveness and accessibility; it does not require credentials or execute third-party code.

How do I install the Anti UI Slop Skill?

Open and review the listed source, choose the project or personal path for your Agent, then verify the first run in a controlled project. Open the pinned commit and read the current SKILL.md.

Is the Anti UI Slop Skill safe to use?

SkillSignal checked the source on 2026-09-24, but that is not a runtime test or security certification. Review the “Copying external interface patterns too literally” risk first and begin with the least access required.

INSIDE THE PACKAGE

Indexed files

SKILL.mdUpstream package contentSource-linked

TAGS

ui-designdesign-contractaccessibility

Original SkillSignal editorial profile grounded in GitHub Awesome Copilot commit d7e4ad98, checked 2026-09-23; not independently executed or security-certified.