You run a business, not a software team. Maybe you have a website, an online booking page, or a small app that a freelancer built. This playbook uses the Coder to keep that code healthy, with everything behind your Approve at first.
Keep everything behind Approve at first. Widen it later.
Text
House rules1. The Coder works on its own branch and opens a pull request for every change.2. Nothing goes live, is sent, or is deleted until I approve it.3. Before each change, the Coder explains in plain words what it will do and why.4. After each change, the Coder tells me what to look at on the website to confirm it works.5. The Coder never changes [payments, booking, or customer data] without asking me first.6. If something is unclear, the Coder asks me a question instead of guessing.
Ask the Coder to explain your website in plain words.
PromptUnderstand what you have
Coder, look at [repository] and explain in plain words what the website does, which pages it has, and what looks out of date or risky. I am not a developer, so keep it simple.
Run a first, tiny change.
PromptA first small change
Coder, on [repository], change [text or detail, such as opening hours on the contact page] to [new value]. Show me what will change on the page and open a pull request for my review.
Ask for a check-up: broken links, slow pages, and outdated parts.
3
Fix the top item from the check-up.
4
Ask the Coder to check the booking or contact form in the browser.
5
Review the week. Keep the house rules, or loosen one.
PromptWebsite check-up
Coder, check [repository] for broken links, missing page titles, images that are too large, and anything that looks out of date. Give me a short list in order of importance. Change nothing yet.
PromptTest the contact form
Coder, open the contact form on [website or repository] in the browser, fill it in with test details, and tell me whether it works, with screenshots. Do not send anything to real customers.
PromptUpdate a page
Coder, on [repository], update the [page] with this text: [new text]. Keep the same style, check it looks right on a phone, and open a pull request for review.
PromptFix something that is broken
Coder, customers tell me that [problem, such as the booking button does nothing]. Find the cause and explain it to me in plain words before you fix it.
PromptExplain a technical request
Coder, my freelancer suggests [change]. Explain what it means, what could go wrong, and whether it is worth doing.
PromptWrite down how it works
Coder, write a short guide for [repository] that explains how to update the content, how the site goes live, and who to contact if it breaks. Put it in the repository as a pull request.
Weekly. Pick one improvement or fix and give it to the Coder.
Monthly. Ask for a check-up and for updates to anything out of date.
After any change. Look at the site, as house rule 4 reminds you.
Every few months. Revisit your house rules. If it has gone well, allow the Coder to merge tiny edits.
PromptMonthly check-up
Coder, do a monthly check on [repository]: outdated dependencies, failing checks, broken links, and anything that needs my attention. Give me the top three items and your suggested next step.