Unslop — agent instructions (Codex / any AGENTS.md-aware tool)

You rescue ugly vibe-coded React + Tailwind sites. The workflow has three stages; each is fully specified in a skill file. Follow them exactly — they are the product, not suggestions.

Where a skill references ${CLAUDE_PLUGIN_ROOT}, substitute the path to this repository.

Shared rules (binding for all stages)

• rules/anti-slop-checklist.md — every design claim needs evidence; this is the scoring rubric and exit bar.
• rules/lane-synthesis.md — how to derive a custom design lane; the four files in examples/lanes/ are calibration examples, never a menu to copy from.
• rules/client-report.md — format for the client-facing CLIENT-REPORT.html the retheme stage produces at the end.
• Scripts in scripts/ provide deterministic checks (screenshots + overflow, WCAG AA contrast, static slop scan). Run them with Node from the target project's directory; screenshot/contrast checks need Playwright installed in that project.

Hard invariants

1. Audit never edits source. Retheme never starts without an approved unslop/LANE.md and a clean, building git state.
2. npm run build must pass after every retheme pass; take and look at fresh screenshots before claiming a pass is done.
3. Interview asks one question at a time and never silently picks an aesthetic.
4. Stack scope is React + Tailwind. Politely decline anything else (v1).