Beginner7 min readShare
Was this chapter helpful?
Share
A day in the life of an AI coder. The simple loop you'll repeat to add features, fix bugs, and ship without breaking things.
You want to add a newsletter signup box to the bottom of your homepage. Instead of asking AI to do it all at once, you break it into three small prompts: build the box, wire up the form, then style it. After each step you check the browser and save with Git.
Build this with AI
"On my homepage, add a newsletter signup section just above the footer. It should have a heading that says 'Stay in the loop', a short subtitle, an email input, and a 'Subscribe' button next to it. Match the purple gradient style I'm already using, and make it stack vertically on mobile. Don't connect it to anything yet — just the visual layout for now."
Every AI coder follows the same five-step loop. Master this and everything else gets easier.
Pick one small change
Describe it clearly to AI
Open the browser, test it
Commit it with Git
Move to the next small change
The golden rule: never skip the "Check" or "Save" steps. They feel slow but they save you hours when something breaks. A 30-second commit is cheaper than rebuilding two hours of work.
Here's what a typical building session looks like — start to finish.
Morning
Open your AI tool, pull the latest version of your project, and pick ONE thing to add today. Write it down. 'Add a dark mode toggle' is a great Monday goal — concrete and small.
First session
Run your first small prompt. Open the browser. Click around to make sure nothing else broke. If it works, save with Git. If it doesn't, undo and try a different prompt.
Mid-day
Keep looping. Each commit is a tiny step forward. By lunch you'll have 5–10 small wins, all saved. If AI starts going in circles, take a break or start a fresh chat.
Afternoon
Pick a bug from your list. Click around in the browser until you can make it happen on purpose, then copy the exact error message and tell AI which page it's on. Once it's fixed, check the rest of the site to make sure nothing else broke.
End of day
Make sure everything is committed. Push to GitHub so it's backed up. Write down what you'll work on tomorrow. Close the laptop. Future-you will thank present-you.
Big features are just lots of small ones. Break them down before you prompt.
Before opening AI, write down: 'Users should be able to bookmark articles and see them on a Saved page.' If you can't say it in one sentence, it's not ready yet.
List the steps: (1) bookmark icon on each article, (2) remember it when clicked, (3) show the saved ones on a Saved page, (4) show a friendly message when nothing is saved. That's 4 prompts, not 1.
On the article cards, add a bookmark icon button in the top-right corner. When I hover over it, it should turn purple. Don't make it actually save anything yet — just the icon and the hover effect.
Open your project in the browser, scroll through the article list, and hover over the new icons. Then click around the rest of the page to make sure nothing else broke.
Commit with a clear message: 'Add bookmark button to article cards'. Now the next prompt has a safe starting point.
Now ask: 'When someone clicks the bookmark button, remember which article they saved so it shows up later, even if they close the tab.' Then check it works and save again. Keep going until the whole feature is done.
Bug fixes follow a different rhythm than features. Reproduce first, then prompt.
The bug-fix prompt template
"On the [which page or section], the [which thing] is doing [what's wrong]. It should be doing [what you expected]. Here's the error message I'm seeing: [paste error]. Please make the smallest change you can to fix it."
Beyond features and bugs, here's the daily housekeeping that keeps a project healthy.
Change a headline, swap an image, tweak a button label. Tell AI the exact text and the file or section it lives in.
Increase spacing, fix a hover state, adjust a color. Small visual tweaks compound — your site looks more polished every day.
When the same thing keeps appearing in lots of places, ask AI to tidy it up so it lives in one spot. Then check that everything still looks and works the same.
Keep a simple notes file with bugs you've spotted. Each session, pick one or two and fix them before adding new features.
Even if you didn't finish a feature, push what you have. GitHub is your backup — never trust just your laptop.
If you're working with anyone else, grab their latest changes before you start. Otherwise you'll spend the day untangling who changed what.
Some sessions feel cursed. Here's how to recover instead of rage-quitting.
Start a fresh chat. The old conversation has too many wrong attempts in its memory — it's confusing AI more than helping.
Stop. Undo to your last working commit. Take a 5-minute break. Try a smaller, more specific prompt.
Don't accept changes you can't read. Ask: 'Explain what you just changed in plain English.' Read it before moving on.
Walk away. Come back tomorrow. A fresh brain solves problems faster than a tired one staring at the same screen.
Real prompts you'll use every day. Swap the words in brackets for your own details — describe things the way you'd describe them to a friend.
Add a small thing
"On my [which page], add a [what you want, e.g. 'small contact button in the top right corner']. Match the style of the rest of the page. Please don't change anything else, and tell me in plain English what you did."
Fix something that's broken
"On my [which page], the [which thing, e.g. 'sign-up form'] is doing [what's wrong]. It should be doing [what you expected]. Here's the error message I'm seeing: [paste error]. Please make the smallest change you can to fix it."
Tweak the design
"On my [which page], please give the [which section] a bit more breathing room, make the heading bigger, and add a subtle effect when I hover over the cards. Keep the same colors and the same overall layout."
Tidy things up
"My project is getting a bit messy. Without changing how anything looks or behaves, can you reorganize things so they're cleaner and easier to work with? Tell me in plain English what you changed."
Explain what just changed
"Before I keep going, can you explain in plain English what you just changed and why? Keep it short — three or four bullet points, no jargon."
Undo and try again
"That last change broke [what broke]. Please undo it. Then try a different way to [what you originally wanted] that doesn't touch [the thing that broke]."
End-of-day save
"I'm wrapping up for the day. Please save all my changes with a short message that describes what I worked on today. Keep it simple — one clear sentence."
Plan tomorrow's session
"Look at where my project is right now and suggest the next three small things I could work on tomorrow. For each one, give me a short description in plain English. Put the easiest one first."
