Use this skill when the user explicitly asks to map, document, or onboard into an existing codebase. Trigger for prompts like "map this codebase", "document this architecture", "onboard me to this repo", or "create codebase docs". Do not trigger for routine feature implementation, bug fixes, or narrow code edits unless the user asks for repository-level discovery.
anti-ui-slop
anti-ui-slop is an open-source frontend skill for Claude Code, Cursor, Codex, and GitHub Copilot, published by github. Its author describes it as: “Stop Codex, GitHub Copilot, Claude Code, and Cursor from shipping generic UI. Use UIZZE’s public catalogue of 800,000+ real web and iOS screens to extract product-specific design decisions and enforce a hard finish ga…”. The project has 38k stars on GitHub and is available under the MIT license. Add it to your setup with `git clone https://github.com/github/awesome-copilot ~/.claude/skills/anti-ui-slop`.
What anti-ui-slop does
Use this skill when building, refactoring, or reviewing a web or iOS interface. The goal is not to make a generic layout prettier. The goal is to make the interface visibly belong to this product, support its real user job, and behave correctly in every important state.
Installation
Add anti-ui-slop to your agent with:
git clone https://github.com/github/awesome-copilot ~/.claude/skills/anti-ui-slopAlways review a skill's source before installing it. This command comes from the skill's public repository; the linked repo is the source of truth for exact setup steps.
What's inside
The SKILL.md for anti-ui-slop is organised into these sections:
- 1. Inspect the Product Before Designing
- 2. Collect Real Interface Evidence
- 3. Write a Design Contract
- 4. Build in the Product’s Language
- 5. Run the Finish Gate
- Product specificity
- Interaction completeness
- Responsive and accessible behavior
- Design-system integrity
- 6. Handoff Format
When to use it
Reach for anti-ui-slop when you want frontend help from Claude Code without writing the same instructions every session. Load the skill and the agent picks it up automatically for relevant tasks.
Strengths
- Clear MIT license — safe to read and adapt
- Ships in github/awesome-copilot, an established project with 37,982 GitHub stars
- Declares compatibility with Claude Code, Cursor, Codex, GitHub Copilot
- Actively maintained (recent commits)
Topics
Frequently asked questions
- What does anti-ui-slop do?
- Stop Codex, GitHub Copilot, Claude Code, and Cursor from shipping generic UI. Use UIZZE’s public catalogue of 800,000+ real web and iOS screens to extract product-specific design decisions and enforce a hard finish gate for web and iOS interfaces.
- How do I install anti-ui-slop?
- Run git clone https://github.com/github/awesome-copilot ~/.claude/skills/anti-ui-slop in your agent, then reload your skills. Review the source at https://github.com/github/awesome-copilot before installing.
- Is anti-ui-slop free to use?
- Yes. anti-ui-slop is free and open source under the MIT license, so you can read, run, and adapt it within that license's terms.
- Which agents does anti-ui-slop work with?
- anti-ui-slop declares compatibility with Claude Code, Cursor, Codex, and GitHub Copilot. Agent Skills use a portable SKILL.md format, so other compatible clients can usually load it too.
- Where does anti-ui-slop come from?
- anti-ui-slop ships inside github/awesome-copilot, a repository that contains 41 catalogued skills in total. The repository's 37,982 GitHub stars apply to that whole collection, not to this skill on its own.
Related skills
More Frontend →
Accessibility audit skill for scanning, fixing, and verifying WCAG 2.2 Level A and AA compliance across React, Next.js, Vue, Angular, Svelte, and plain HTML codebases. Use when auditing accessibility, fixing a11y violations, checking color contrast, generating compliance reports, or integrating accessibility checks into CI/CD pipelines.
Company Architect: builds a business from scratch as an OKF (Open Knowledge Format) bundle — a tree of version-controllable .md files with frontmatter type, links forming a graph, and reserved index.md/log.md, readable by humans and agents. Guides the founder through a 12-phase interview (foundation, strategy, market, financial, sales, marketing, product, operations, tech, people, legal, governance), one phase at a time, few questions per block, and generates the concepts as conformant markdown. Trigger when the user wants to create, structure, or document an entire company in folders and .md files; when they mention build my company from scratch, company as code, company knowledge base for AI to read, company wiki for agents, OKF, or knowledge bundle. In English.
Assembles comprehensive board and investor update decks by pulling perspectives from all C-suite roles. Use when preparing board meetings, investor updates, quarterly business reviews, or fundraising narratives. Covers structure, narrative framework, bad news delivery, and common mistakes.
Run tests on BrowserStack. Use when user mentions "browserstack", "cross-browser", "cloud testing", "browser matrix", "test on safari", "test on firefox", or "browser compatibility".