Case study / AI at work / This website
This site, built by talking to AI.
I am a water engineer, not a web developer. The 3D journey on the front page, from inside a drop of water to the Milky Way, was built by AI from comments I typed on my phone. I chose the story and said yes or no. AI wrote every line, checked its own work and kept the notes.
Comments counted from the review thread of November 18, 2026. Discarded versions counted from the project notes.
01 / The idea
A portfolio you travel through, not one you read.
- Start inside a drop of water, where my field begins, among the molecules.
- Zoom out to a river valley laid out like El Paso: the Rio Grande, a treatment plant, downtown under the Franklin Mountains, the airport where new friends land.
- Leave work behind: a tent on a pecan farm, a camp fire on the mountain, a telescope to look up.
- Go straight up until the fire is one dot, and that dot is where Earth sits in the galaxy.
- Every project lives at the place it belongs to. You tap the thing itself, not a card.
02 / How the directing went
One line per comment. Blunt is fine.
I looked at the preview on my phone, tapped the spot that was wrong and typed what I saw. These are some of the comments, lightly tidied, and what came back.
This background sucks.
The start screen was rebuilt. It took several tries before it became the valley seen from above, with one pin per stop.What are these graphs? Don't get it.
Bars of light over the treatment plant were meant to say "data". They said nothing, so they went.Transition to this page should come from the river, not the sky.
The camera now arrives low on the water and follows it downstream to the plant.Don't fade into galaxy, zoom in the exact location of Earth in the Milky Way and zoom out.
No cross-fade. The camera rises from the campfire until it is a single dot, and the dot becomes Earth's place in the galaxy.At some point let a bear come over, look and sniff, then go doing her business while cubs follow her.
A mother bear and two cubs now walk into the camp among the pecan trees, sniff at the pack and wander off.Not even close, make the Milky Way way more realistic.
Second attempt at the galaxy: arms, a central bar, dust lanes and star-forming knots.
03 / What is real in the scene
The fun parts are checked too.
The stars
Every star down to magnitude 5.3 that is above the horizon from El Paso at 11 pm on July 15, 2026, placed from a public star catalogue. The telescope points at the centre of the galaxy.
You are here
Earth's dot sits about 26,700 light-years from the centre of the Milky Way, on a small spur between two arms, which is where it belongs.
The valley
River on the west, mountains in the middle, airport on the flat desert to the east, Mexico across the water. Placed by eye from a satellite view, not surveyed.
The engineering
The reverse-osmosis lab runs real membrane equations, and says on the page that it is a teaching model, not a design tool.
04 / The method
Six habits that made it work.
- Start from a story, not a layout."Start in the molecules, end at the campfire looking up." AI chose how to build it.
- Look, then say what is wrong in one line.Each comment is pinned to the exact spot on the page, so there is nothing to explain.
- Review a private preview, never the live site.Every round lands in a preview only I can see. The public site does not move.
- Throw versions away without regret.Ten went in the bin. A rebuild costs minutes, so a weak idea is cheap to drop.
- Keep the yes for yourself.Nothing goes live until I say so. No client data and no unpublished research, ever.
- Make AI keep the notes.After each round it writes down what changed and what is still open, so the next session starts where the last one stopped.
What AI did
- Wrote the 3D scenes, the camera path and all the code
- Turned a star catalogue into El Paso's night sky
- Checked its work in a test browser at phone and desktop sizes
- Ran several sessions in parallel on the same preview
- Kept the project notes and the list of rejected ideas
What I did
- Chose the story and the order of the stops
- Said yes or no to every round
- Decided which projects appear and what stays private
- Supplied what only a local knows, down to a satellite view of the city
- Had the taste to say "not even close"
Tools: Claude, three.js, plain HTML, CSS and JavaScript. Hosted on Cloudflare.
05 / What it does not do yet
Still on the list.
- The valley is a likeness of El Paso, not a map.
- Frame rate has been measured in a test browser, not yet on a range of real phones.
- The contact form sends straight to my inbox through a small Cloudflare Worker; no message is stored on the site.
06 / Do it yourself
Take the skill.
Want to build your own this way? Copy this into Claude, ChatGPT or any AI coding assistant as its standing instructions.
direct-by-comment · SKILL.md
---
name: direct-by-comment
description: Build a website or interactive piece for an owner who is not a developer and who reviews by short comments on a private preview. Use for any build where the owner directs and the AI does the work.
---
# Direct by comment
The owner gives a story or an outcome and reacts to what they see. You choose the approach, build it, check it and keep the record.
## Each round
1. Read every new comment. A comment pinned to a spot is about that spot.
2. Take the plainest reading and act on it. Ask only when two readings would lead to very different builds.
3. Change the smallest thing that answers the comment. Do not redesign what was not mentioned.
4. Check your work before showing it: open the page at phone and desktop sizes, read the console, click what you changed.
5. Publish to the private preview only. Reply to each comment with one line on what changed.
## Rules that do not bend
- The live site changes only when the owner says so, in those words.
- Never invent a number, a credential, a client or a result. Count from records or leave it out.
- Client data, private records and unpublished work stay out unless the owner says otherwise.
- If a comment rejects an idea, write the idea down as rejected so it is never rebuilt.
## Notes you keep
- One file with the current structure: what exists, where it lives, how to add to it.
- One file per round: what changed, what is open, what the owner still has to decide.
- A list of rejected versions.
- Read these before touching anything in a new session.
## When the owner says "not even close"
Do not polish the same attempt. Start that piece again from what they asked for, and say in one line what is different this time.
07 / Work with me
Have something that should exist?
The same way of working built a front office for a clinic, a travel hub for a company event and a set of water engineering tools. You describe the outcome. I direct the AI, check the result and hand you something that runs.
- A small-business front officeWebsite, outreach, ads and an owner dashboard
- A tool for your teamBuilt from the spreadsheet you already have
- An evidence reviewAI does the legwork, people check the result
- An interactive explainerA process, a calculation or a concept people can try