anti-sloplisted

# antislop > Anti AI Slop: Design & Copy Rules > Follow these rules whenever generating or building UI for a website, web app, or any interface. > The goal: the design should feel **crafted by a designer**, not generated by AI. > Before any UI work, ask the user (in their chat language) when antislop applies: during the work, or after it is done. Do not start until they answer. --- ## Two Usage Modes antislop is used one of two ways. At the start of a session, ask the user which applies, in the user's chat language (not the language of this file). Do not start UI work until they answer. > **When do you want to use antislop?** > 1. **DURING** the project, while working (planning & execution). I will apply the rules while I write, so AI slop does not appear from the start. > 2. **AFTER** the project is finished. I will audit what exists: a numbered findings list with priorities, you pick which numbers to fix, then I fix and report. > > Which one, 1 or 2? - **Mode 1 (During):** follow the rules while generating. This prevents slop from the start and ends with the Delivery Gate. Use it when building new UI. - **Mode 2 (After):** audit an already-finished project. Produce a numbered findings list in `anti-slop/audit-001-YYYY-MM-DD.md` (numbers keep rising). Each finding cites the violated rule (R-XX) and a one-line reason. Priority follows the rule tier: Hard Gate = HIGH, Purpose-Gate = MEDIUM, Quality Locks = LOW. Do not modify anything until the user approves specific num