A mobile dog groomer wants customers to check whether they cover their postcode before asking for an appointment. Try the checker below with a made-up business.
Try the postcode checker
This groomer covers BS5 and BS6. Try BS5, an area they cover, and BS8, an area they don’t. The demo checks the example on this page without sending or saving the postcode.
Codex helped build and test this checker. We checked a covered district, an uncovered district, a full example postcode and what happens if a customer mistypes it. The checker uses the starting part of the postcode as its area and runs on this page.
Give Claude the job in a few lines
Try this in Claude chat. This is a prompt you can use to draft your own brief.
I run a mobile dog grooming business. I cover BS5 and BS6. I need customers to check their area before asking for an appointment. Turn this into a short brief. Include what the page should say when I cover an area and when I don’t. Flag prices, availability and anything else I need to confirm.
Give Codex the version you’ve checked
Copy the brief into Codex or save it as a text file in the project you’ve opened. Check that it uses the service areas you supplied. Ask for a preview first, with examples you can test on your phone.
For this example, ask it to check BS5, BS8 and BS5 1AA and show a next step for a covered area. Use the preview prompt below for your own job.
Try the simplest route first
If you already use Codex, give it your notes and ask it to draft the brief before building anything. Use Claude as a second pair of eyes if you want it to spot missing details in a longer brief. For a real business, check the coverage yourself. Then send an enquiry from your phone and make sure you can reply.
Try it with AI
Build and test one website change locallyCodex or Claude Code
Read the approved brief and the project instructions. Work on a local preview of [one page or feature]. Before editing, tell me which files you expect to change and flag any missing business fact. Reuse the site’s existing styles. Then make the change and check a normal case, an invalid input and the main action at phone width. Report what you changed, what you actually checked and any check that still needs me. Keep all work local. Approved brief or file path: [paste]Browse all prompts
Leave a handover another tool can followCodex or Claude Code
Write a handover for the next tool or person working on this page. Give them the goal, the files you changed, two decisions and why they were made, the tests you ran with the actual results, and the first thing still to check. Use project-relative paths. Keep credentials, customer details and guesses out. Make clear whether the change is local, on staging or live. Save the note only if I give you the destination.Browse all prompts