The technical specification for Buford's birthday page was four words:
"Make it utterly insane."
Claude produced a 688-line HTML file with 7 progressively unhinged color palettes, flying photos with velocity-based physics, text explosions, screen shake, and a death sequence at 50 clicks where everything collapses like the page lost electricity.
The Two Modes
For the Google Slides project (Post 2), my prompts were surgical:
"Create a text box at position (311700, 445025) EMU with Poppins font at 24pt."
That's appropriate when precision matters. The output is either correct or it isn't.
For Buford's birthday page, precision would have killed it. If I'd said "implement a click handler that spawns text elements with random velocity vectors and applies gravitational acceleration," I would have gotten exactly that: a physics simulation that technically met the spec and had zero personality.
Instead:
"Make it utterly insane with spinning images." "Sporadically splash the words YOU YOU YOU YOU on the screen." "After 50 clicks make it all collapse like it lost electricity."
"Like it lost electricity" is not a technical specification. It's a feeling. And Claude translated it into a six-step death sequence:
- Every animated element gets
.gravity-death. All CSS animations stop cold. - Physics kicks in:
vy += 0.5applies gravity. Everything starts to fall. - The background fades to black over 2 seconds.
- The birthday message rotates 45 degrees and drops off-screen using
cubic-bezier(0.55, 0, 1, 0.45), a curve that mimics actual gravitational acceleration. - A death screen appears: "... system overload ..."
- A 10-second countdown. Everything reboots.
The cubic bezier is the detail that makes it. Claude didn't use a linear fall or a basic ease-out. It used a curve where the drop is slow at the start and fast at the end, like gravity. The birthday message doesn't disappear. It falls, like someone cut its strings.
I didn't ask for realistic gravitational physics. I said "lost electricity" and Claude decided things should fall like they have weight. Unreasonable behavior for a birthday page. Exactly right for this one.
Good Calls I Didn't Ask For
Here's the thing that surprised me: Claude was performance-aware even in chaos mode. The code includes mobile detection that caps flying images at 15 (vs. 40 on desktop) and throttles spawn rates. I asked for "utterly insane." Claude understood that "utterly insane" on a phone with 4GB of RAM means "completely broken" and self-imposed constraints I never specified.
It also added keyboard triggers. Every keystroke spawns more chaos. I never asked for this. But if you're building a chaos page, why would the keyboard be exempt?
This is what Level 2 looks like. I wasn't directing every detail. I was reviewing Claude's output, noticing the decisions it made autonomously (mobile performance, keyboard integration, the specific gravity curve), and approving the ones that were right. Claude proposes, I review, we iterate.
The Framework
| Technical Prompts | Creative Prompts | |
|---|---|---|
| Goal | Correctness | Expression |
| Style | Precise, specific | Vague, emotional |
| Example | "24pt Poppins at (311700, 445025)" | "Make it collapse like it lost electricity" |
| AI latitude | Low: do exactly this | High: interpret the vibe |
| Review focus | Is this correct? | Does this feel right? |
The skill isn't knowing how to prompt. It's knowing which kind of prompt the situation calls for. Technical work needs precision. Creative work needs vibes. Confuse them and you get mediocre results in both directions.
The Takeaway
Buford clicked 50 times in about 12 seconds. He did not ask about the cubic bezier curve. He loved it.
I didn't know which CSS animation curve mimics gravitational acceleration. Claude did. I knew that "lost electricity" should feel heavy and final. Claude didn't, until I told it. The skill isn't prompting. It's knowing when to say "24pt Poppins at position 311700" and when to say "make it collapse like it lost electricity."