Before you start
A coding or chat assistant; a fictional service brief with sample details is provided below.
Why this lesson exists
The original project turned a local service into a trust-first website, with defined services, starting prices with honest qualifiers and a short contact path. This lab practices tracing every claim to the brief before launch.
Practice material
Fictional. Use it for every step below, or swap in your own later.
Brightside Appliance Repair (fictional business; technician notes, every detail is a sample) Washer repair: includes diagnosis, drain pump, door seal and drum bearing fixes. Excludes commercial machines. Dryer repair: includes heating element, drive belt and blocked-vent checks. Excludes gas-line work. Fridge repair: includes thermostat, fan and door-seal fixes. Excludes refrigerant (sealed-system) work. Starting prices (sample): diagnosis visit $79, credited to the repair if you go ahead; most repairs $120–$260 plus parts; the final price is quoted before work starts. Process: 1. Call or email with the model number and the problem. 2. We confirm a two-hour arrival window. 3. The technician diagnoses, quotes, and repairs only after you approve. Service area (sample): Riverside and Eastgate. Contact (sample): 555-0142, hello@example.com, Monday to Friday 8 am–5 pm. Unverified, leave out unless confirmed: “fully licensed and insured”, “10 years’ experience”, “best prices in town”, “same-day service guaranteed”.
Do the exercise
Set your boundary
List what is included, what is excluded, the service area and the next step. Keep sample testimonials and invented credentials out.
Define every service
List every service and define what is included and what is not.
Show honest starting prices
Publish starting prices with honest qualifiers.
Describe the process
Describe the process in three plain steps. Use only photos you took or have permission to use, and label any placeholder.
Add sample contact details
Add phone, email, hours and service area, labeled as sample. Leave licenses out unless the brief verifies them.
Test every claim
Test every claim and placeholder before launch: each one traces to the brief or is removed.
Next sessions, not today
- Quote form Build a short quote form with the minimum useful fields. Until it has a working delivery backend, label it as a prototype or use a contact link instead.
A prompt to adapt
Replace the bracketed parts with your own details.
Help me build a one-page website for [fictional service business] in a new practice folder. First version only: what is included, what is excluded, the service area and one next step, using only my brief or clearly labeled samples. No testimonials, invented credentials or quote form yet. List any setup commands before changing files. If you can’t create files, give me one self-contained index.html instead, and tell me how to save it, open it in my browser and preview it at phone width. Then work in five checkpoints and, after each, tell me how to check it on a phone: 1. Every service, with what is included and what is not. 2. Starting prices with honest qualifiers. 3. The process in three plain steps, with any placeholder photo labeled. 4. Phone, email, hours and service area, labeled as sample; no licenses unless the brief verifies them. 5. Every claim traced to the brief, and anything unverified removed. Write it from these notes: [paste the practice material or your own fictional technician notes].
When your first version is done, paste it and ask:
Audit this local-service website for trust. Flag unsupported claims, fake-looking statistics, unclear prices, weak service boundaries, missing contact information and anything that could mislead a customer. Return fixes ranked by risk.
Run this experiment
Trace every factual claim to the brief. Use a phone preview to find contact details, inspect price qualifiers and test the quote or contact destination.
Check your result
Use evidence from your output. A confident explanation from the AI is not enough.
If it isn’t working
If a form has no delivery backend, label it as a prototype or replace it with a working contact link. A success animation is not proof a message was delivered.
Optional. Progress stays in this browser.
Where this came from
Public project repository ↗. The practice lesson is an adaptation, not a verbatim transcript. About the sources.
Prepared September 2026. Tools and interfaces change; use current official setup instructions. Session lengths are estimates.
patrickz