Kenneth W. BinghamAI Prototyping Engineer · Full-Stack
Claude Code in VS Code

Anyone can type a prompt. The work is in the direction.

I cannot change the model. The provider owns the weights and the training. What I can change is how the instance in front of me behaves, by what I have it read before it starts and by what I refuse to accept when it finishes.

This page is that method: the loop I run, the standing rules I give the AI, real exchanges from the build record, and the times it got things wrong. None of it is secret, and it works on any capable model.

The loop

Five steps, repeated until the thing is right. The AI does most of the second. The rest is the job.

DirectSay what it is for, who will use it, and what must stay true. Not how to type it.
BuildThe AI writes the code and the tests, in small focused pieces I can read.
VerifyIt runs what it wrote and shows the output. I look at the real thing, in a browser, on the live address.
CorrectI say what is wrong in plain words. Most of my messages are this step.
ShipTests pass, links are checked, it is published, and the published copy is checked again.

The standing rules

These are loaded into every session before any work starts. Each one exists because of something that went wrong without it.

Direction, not commands

A command is carried out the same way whatever the context. Direction orients judgment and then requires it. I want to see the AI's judgment so I can correct it.

Not a yes-man

Everything is tested. Nothing is accepted as true until it is verified, including what I say. If I am wrong it tells me and shows why.

Say what was run

Every command is marked as run by the AI or left for me to run. A step that was not run is never presented as done.

Label the claim

Established, measured, an interpretation, or not claimed. Unverified is a holding state, not false, and not to be stated as fact.

Never fill the void

Where there is no evidence, mark the edge and stop. "I don't know" is an acceptable answer. A confident guess is not.

Tests that try to break it

A case worked by hand, the edges tried, and every tipping point checked by putting it back in. When a sound result fails a test, suspect the test first.

Small, plain code

Functions stay short and focused. Clarity over cleverness. Comments say why, in words a newcomer could follow.

Finish before switching

A new request is queued, not dropped into the middle of half-done work.

One style rule, to prove it listens

No long dashes, anywhere. It is trivial, instantly checkable, and shows whether an instruction is still being held an hour in.

Real exchanges

My messages are quoted from the record with only the spelling tidied. I type fast and in my own voice. What matters is that each one carries a decision the AI could not have made for me.

If I stumbled on this site right now, I would think it was mainly to compare airline fares.

What had happened: the AI led the page with a single example because it was the easiest to demonstrate.

What I was doing: reading it as a stranger would. The code was fine. The first impression was wrong.

Useful right up front. Not just informational, but useful to them.

What had happened: a tidy page that explained things well and gave a visitor nothing to do.

What I was doing: holding the work to its purpose. The page became a calculator that takes the visitor's own numbers.

It should not be opinionated.

What had happened: the AI invented two thresholds so a picture could show a verdict, and said so.

What I was doing: setting a principle. The tool reports figures. The person decides what they mean.

It says "none was made by AI". Some of the reference pictures were. All the paintings were painted by hand.

What had happened: my statement had been shortened into something that sounded better than it was.

What I was doing: correcting my own site so that it claims only what is true.

Not the feeling of the piece. The look and feel of the piece.

What had happened: the AI had smoothed my phrase into its own.

What I was doing: keeping my words mine. It renders what I mean. It does not get to decide it.

Right now the button says Pause. It needs to say Play at first.

What had happened: the logic was correct and the experience was backwards.

What I was doing: using the thing. No test catches what a person notices in two seconds.

Where the AI gets it wrong

It is fast, tireless and often right. These are the failures I watch for. The first three are from this month's work.

It builds the wrong thing, well

I said to make one page look "more like the other one". It picked the wrong one, restyled the page, tested it, published it and reported success. Everything it said was true. It was the wrong job. I found it by opening the live site.

It prefers the tidy version of the truth

Left alone, it will round a qualified statement into a clean one. On a site that makes claims, that is how a small inaccuracy gets published under my name.

Its tests can be wrong too

A check failed on a result that was correct, because the test was stricter than the method it was testing. The rule is to chase every disagreement to its cause before believing either side.

It will fill a gap if you let it

Asked for a number it does not have, an unprompted model supplies one. Mine is told to stop and say what it would need. That rule is there to stop invented detail at the source.

Technology should leave the person using it more capable, not more dependent.

The person decides. Software recommends, a named human makes the call. I build that into the tools, and it is how I work with the AI itself.

Show the working. A tool that gives an answer without its reasoning asks to be trusted. One that shows the sum can be checked, argued with and learned from.

People do the work. In every system I have worked on, the value came from the people running it and what they knew. Good software carries more of the load for them.

Credit honestly. I conceive, direct and decide. The AI writes and tests. It does not originate the ideas, and I do not claim to have typed every line. Both halves are stated on everything I publish.