Your First AI Project

Everyone tells you to learn to code first. You don't have to any more.

In about two evenings you will build Nova: your own AI assistant, with a personality you wrote, a memory, replies that stream in word by word, and a settings panel - live on the internet at a real address you can text to a friend. You will not type a single line of code, or a single terminal command, at any point.

Here is the honest version of what that means, because a vaguer version is currently being sold to you by people who have never shipped anything. You will see code - it'll be on your screen, in green and red, and this book teaches you to look at it the way a building inspector looks at a wall. You will finish able to say what every part of your app does. You will not finish able to write it from scratch, and Chapter 20 is a frank inventory of exactly where that line falls.

What you learn instead is the job that actually decides whether software is any good: saying precisely what you want, and checking whether you got it. It comes down to six named moves, and they are what this book is really selling. Get the AI to interview you instead of writing a prompt yourself - because you don't yet know which decisions exist. Correct the plan before anything is built, when being wrong is still free. Make it explain its work in plain English. Steer one specific, testable change at a time. Report symptoms rather than guessing at causes. And never, ever believe the word "done."

That last one has a chapter of its own. The tool you're working with will sometimes be wrong while sounding completely certain - it will describe features it never built and announce fixes that didn't fix anything, in exactly the same cheerful tone it uses when it's right. There is no tone change to listen for. So this book teaches you the four shapes that failure takes, the tell for each, and how to prove your builder wrong about your own app without reading a line of code.

Inside: one download and no setup night · the interview prompt that writes your spec for you · reading a change without reading code · breaking your app on purpose and repairing it · what it really costs, to the tenth of a cent, and a hard spending cap set before you build · character, memory, streaming, and a settings panel · testing like a client · save points that make you brave · deploy day and the classic failure everyone hits · first users, and what to watch instead of what to ask · plus a prompt pack of every reusable sentence in the book, and a symptom-to-sentence table for when your mind goes blank.

Requires a paid Claude plan and a few dollars of API credit - both explained plainly in Chapter 1 rather than sprung on you at Chapter 5. No experience of any kind assumed.

By the last chapter there's a URL on the internet with your project on it. Most people never cross that gap.