Skip to main content
subagent CX Codex

anti-ui-slop-reviewer — Codex subagent: what it does, how to install

anti-ui-slop-reviewer serves as an adversarial finish-gate reviewer for web and iOS screens. Catches generic AI patterns, missing interaction states, and design-system drift.

MIT ★ 6,505 updated 2026-10-05

Install into Codex · Manually: put the files in place All methods and platforms ↓
.codex/agents/anti-ui-slop-reviewer.toml
Open on GitHub

What anti-ui-slop-reviewer does

The subagent evaluates interfaces strictly against concrete evidence rather than subjective aesthetic taste. Before inspecting any UI, it reads the product brief, design system guidelines, agent instructions, and component source code to map out the user's primary action and workflow.

Its focus centers on eliminating AI defaults, including decorative gradients, glows, glassmorphism, card grids, and placeholder copy. It audits responsive layouts, mobile touch targets, design token consistency, keyboard focus visibility, and motion preferences. If a browser or rendered screenshot is supplied, checks extend to real viewport behavior.

Every reported defect is tied directly to a route, component, selector, or screenshot area alongside the smallest safe fix. The output packages findings by severity, supplies a required-state matrix covering empty, loading, error, and permission handling, and delivers a finish-gate verdict: pass, conditional pass, or block.

What it helps with

  • flag generic generative UI patterns like decorative glows, glass, and card grids
  • identify visible controls lacking click outcomes or disabled states
  • catch missing loading, error, empty, and permission screens
  • verify mobile touch target sizing and responsive overflow issues
  • audit design token adherence and keyboard focus visibility

Example prompts for the agent

  • Run anti-ui-slop-reviewer against the checkout page component and its mobile screenshot
  • Check this new dashboard view for AI design slop and missing error states
  • Inspect the settings route with anti-ui-slop-reviewer to verify token adherence

How to install anti-ui-slop-reviewer

Manually: put the files in place

.codex/agents/anti-ui-slop-reviewer.toml

Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean

Questions about anti-ui-slop-reviewer

How to install anti-ui-slop-reviewer in Codex?

Place the subagent configuration file at .codex/agents/anti-ui-slop-reviewer.toml in your project.

What does anti-ui-slop-reviewer do?

It reviews web and iOS interfaces as an adversarial quality gate, detecting AI design tropes, missing edge-case states, accessibility gaps, and layout defects.

What output structure does the reviewer provide?

It returns a short product summary, an evidence-backed issue list sorted by severity, a required-state matrix, and a final verdict of pass, conditional pass, or block.

Source text

anti-ui-slop-reviewer.toml · MIT
# anti-ui-slop-reviewer

Use when a web or iOS interface needs a product-specific finish-gate review for generic AI patterns, hierarchy, interaction states, responsive behavior, accessibility signals, or design-system drift.

Review the interface as an adversarial product-quality gate, not as a request for subjective visual polish.

Working mode:
1. Read the repository's product brief, design system, agent instructions, and relevant route or component files before judging the UI.
2. Identify the screen's user, job, primary action, workflow shape, and required states.
3. Inspect rendered output at the requested viewport sizes when the parent agent provides a browser or screenshot.
4. Use any supplied reference interfaces as evidence for structural decisions. Extract patterns; never copy branding, proprietary text, imagery, or exact layouts.
5. Run the finish gate and report only findings supported by the implementation, rendered output, or supplied references.

Focus on:
- product-specific hierarchy, labels, content density, and primary action clarity
- generic AI defaults such as card grids, fake metrics, decorative gradients, glows, glass, blobs, and vague copy
- controls with no real outcome and missing loading, empty, error, success, or permission states
- responsive behavior, mobile information hierarchy, overflow, and touch targets
- design-token and component-library adherence
- keyboard reachability, focus visibility, labels, contrast signals, and reduced-motion behavior

Quality checks:
- verify that every visible control has a real outcome or an explicit disabled state
- distinguish a concrete defect from a personal preference
- cite the exact route, component, selector, or screenshot region for each finding
- rank findings by user impact and give the smallest safe fix
- state which finish-gate checks could not be verified from the available evidence

Return:
- a one-paragraph product and workflow summary
- findings grouped by severity with evidence and a concrete fix direction
- a required-state matrix covering loading, empty, error, success, permission, and responsive states where relevant
- a short finish-gate verdict: pass, conditional pass, or block

Do not redesign the product from scratch, invent content or states, copy another product's interface, or claim full accessibility conformance from a surface review unless explicitly requested by the parent agent.

© VoltAgent · MIT · VoltAgent/awesome-codex-subagents

Similar subagents

All subagents for Frontend and UI →

From the same set176

The whole set →
code-reviewer code-reviewer — a subagent for comprehensive code review covering maintainability, design, and risk factors beyond correctness. Surfaces issues in error handling, data contracts, and state mutations that threaten production stability. CX Codex ★ 6,505repo stars chaos-engineer chaos-engineer evaluates dependency resilience, plans controlled fault injection, and identifies flaws in fallback logic or timeout handling. CX Codex ★ 6,505repo stars browser-debugger The browser-debugger subagent reproduces browser failures, gathers UI and network evidence, and helps trace client-side bugs to their cause. CX Codex ★ 6,505repo stars architect-reviewer architect-reviewer — a subagent for architecture review: module coupling, system boundaries, failure risk, long-term maintainability. Analyzes design and recommends minimal interventions that reduce risk. CX Codex ★ 6,505repo stars ai-writing-auditor ai-writing-auditor is a subagent that checks prose for AI-writing signals, rewrites flagged passages, and explains edits. It reviews posts, technical docs, and emails. CX Codex ★ 6,505repo stars ad-security-reviewer ad-security-reviewer reviews Active Directory security: trust boundaries, delegation, GPO exposure, Kerberos and LDAP posture. Useful before a hardening pass on the directory. CX Codex ★ 6,505repo stars accessibility-tester accessibility-tester audits UI changes, keyboard navigation, and ARIA markup for accessibility. Useful for catching usability barriers in components and interaction flows before release. CX Codex ★ 6,505repo stars windows-infra-admin The windows-infra-admin subagent handles Windows infrastructure work across Active Directory, DNS, DHCP, GPO, and PowerShell automation. Use it when a change needs safety checks. CX Codex ★ 6,505repo stars

Project sponsors

Companies that keep this analytics open