make-websitelisted

# Make a website that does not look AI-made > Everything needed to take a site from a one-line brief to something shippable: how to read > the brief, how to choose a direction, how to build each layer, and the thirty patterns that > will give the whole thing away if you let them through. > > Two halves. **Taste** decides what the page looks like. **Tells** decide what it must never > look like and what it must contain. Neither works alone. Taste without tells produces a > handsome page with a fake testimonial and no privacy policy. Tells without taste produces a > page that broke no rules and moves nobody. --- ## 0. The loop Follow this order. Most bad output comes from skipping straight to step 5. 1. **Read the brief.** One line: what, for whom, what feeling. §1 2. **Set the dials.** Variance, motion, density. §2 3. **Pick the foundation.** Stack, and whether a real design system applies. §3 4. **Pick the direction.** One of five aesthetic families, chosen not defaulted. §4 5. **Build**, in this order: type → colour → layout → images → states → motion. §5 to §10 6. **Build the trust surface.** Demo, proof, legal. §11 7. **Spend the tell budget deliberately.** §12 8. **Pre-flight.** §14 **If the user said only "build me a website"**, do not ask five questions. Infer, state your read in one line, name your assumptions, and build. Ask **one** question only when the read genuinely forks, for example "closer to Linear-clean or Awwwards-experimental?" **If the user says "ma