hmziq

I don't write briefs.

I don't know what I want until I see it. So the agent shows me, I react, and we go again.

  1. 1Ask for options, not answers.Several versions side by side, with one thing changing at a time.
  2. 2Pick in one line.Mine looked like this: square logo, rings hero, soft corners, ring markers.
  3. 3Say what's wrong.Voice notes, mostly. "Horrible" is useful feedback.
  4. 4Ask for sliders.When words run out, I get a tweaker, tune it by hand and paste the settings back.
  5. 5Turn the answer into a rule.It goes in the rules file, so nobody has to ask again.
  6. 6Make the build check it.A rule the machine can check is a rule that stays.

How it actually went.

This kit, from my notes.

  • 24 SepEmpty repo. The first round of fonts: "not human-readable".
  • 24 SepRound 8. The landing page gets to "about perfect".
  • 25 SepRound 12. The logo is final, with no rings in it.
  • 27 SepSliders for the rings and the lattice. The ball-and-stick versions: "more horrible".
  • 28 SepReact goes. SvelteKit and Astro stay.
  • 9 OctThe React lab is deleted, once both kits match it piece for piece.
  • 13 OctA color per product: "looks horrible". Glass stays.
  • 6 NovKeep every piece until the live sites move over, then delete what they didn't use.

Your site should look like someone made it.