Evidence gates can make Codex-built UIs less sloppy
Codex-style can be good at changing code but still weak at judging whether a looks polished. A React build can pass while the screen still feels generic because of default typography, uneven spacing, random gradients and shadows, and components that do not feel like one . Superloopy is a small MIT plugin and CLI that tries to make Codex finish frontend work with evidence, not just changed files.
Before coding, it pushes the agent to define a DESIGN.md file and a contract, then blocks common AI-looking defaults. It uses a 92-item brand and style reference library to give the work a clearer visual direction. It also checks for undeclared colors and spacing that falls outside the agreed scale, captures real browser at mobile, tablet, and desktop widths, and produces visual diff or hotspot output when there is a reference target.
A visual QA artifact under .superloopy/evidence/ is required before the task is treated as done. The same evidence-gate idea is also used for research and authorized website-clone work, with cited research and a claim ledger.
Key points
- Codex-style agents can pass a build while producing a weak-looking UI.
- Superloopy adds evidence gates for frontend work instead of accepting file changes as done.
- It asks for DESIGN.md, , and checks against undeclared colors or off-scale spacing.
- It captures real browser across mobile, tablet, and desktop sizes.
- It requires a visual QA artifact in .superloopy/evidence/ before completion.
Sources covering this story (4)
- r/codexcliEvidence gates can make Codex-built UIs less sloppy ↗
- Hacker NewsShow HN: Peek-CLI: Let Claude Code See the Browser ↗
- r/ArtificialInteligenceAI-built UIs need evidence gates: design tokens, screenshots, visual QA ↗
- r/OpenAIHow do you keep AI coding agents from shipping generic frontend slop? ↗