web-craftlisted

# web-craft > The difference between "AI made this" and "someone made this" is almost never talent. > It is that a person made **decisions and wrote them down**, then did passes the generator never does. This skill is a **process**, not a style. It does not tell you to use navy, or uppercase display type, or a marquee. It tells you what has to be *decided*, *recorded*, and *checked* so the output holds together. Every code sample here is illustrative of a pattern, not a palette to copy. --- ## When this fires Use it when the deliverable is a real site or page whose quality is the point — marketing, landing, brand, portfolio, client work. Use it on redesigns and polish passes too ("this looks like slop, fix it"). Do **not** use it for internal dashboards, admin CRUD, data tables, or docs sites. Those want consistency and density, not craft theatre. Different job. --- ## The core claim AI-generated UI fails in a specific, diagnosable way. It is not ugly. It is **undecided**. Every value is a local guess, so nothing accumulates into a system: | Slop tell | What it actually means | | --- | --- | | Every card has `border: 1px solid #e5e7eb` | No depth model was chosen, so a border stands in for one | | Three equal feature cards | No hierarchy was decided, so everything is peer-level | | Type sizes are 16/18/24/32/48 | The scale is the framework's default, not a decision | | One flat `opacity` fade on scroll | Motion was added, not designed | | Text is `#666` on `#fff` ev