How do I build a small AI-assisted tool I can actually test?

Prove one local input-to-output path. A CRM connection adds permissions and failure states to a tool you have not tested yet.

Try missing dates, long task text and keyboard navigation. Record what actually happens against the acceptance check.

Keep the source files, usage notes and the last passing version before making the next change.

# Vibe Coding: Specify and Test One Useful Tool

Current companion, prepared November 8, 2026, for the April 8, 2026 class. The exercises are editorial practice; no particular attendee outcome is claimed. No verified recording was located.

Define one user and one job, write the acceptance checks, then build a thin input-to-output slice. Try empty, invalid and ordinary inputs before calling the result useful. Keep the source and a recovery note; publication is a separate decision.

## Choose one job

Write a one-sentence brief for fictional agent Jordan Lee: prepare an open-house checklist from an event date, start time and three tasks. Name the features you will leave out.

Check: No CRM, payment, lead capture, or sending features sneaked into scope.

My input:
Observed result:
Correction and next action:

## Specify states

Describe what the tool should show for ordinary, empty, invalid and saved inputs. Explain how it should help someone correct a missing date without losing the tasks they typed.

Check: Blank date and no tasks produce an understandable correction; no fabricated default date.

My input:
Observed result:
Correction and next action:

## Define tests first

Write the expected result for each input state before asking for code. Include a normal example, a missing value and an invalid value.

Check: Test expectations describe visible behavior, not merely “it works.”

My input:
Observed result:
Correction and next action:

## Build one slice

Ask AI to build one local path from input to checklist preview to printing. Use fictional inputs and inspect the generated files before running them.

Check: Inspect changed files; no secrets, external requests, or unrequested tracking.

My input:
Observed result:
Correction and next action:

## Try the user path

Try the draft with a keyboard, a narrow screen, long task text and an invalid date. Record what you observe beside each expected result.

Check: Text remains readable; validation is actionable; output preserves entered facts.

My input:
Observed result:
Correction and next action:

## Repair and own it

Choose one failed check and request a specific repair. Rerun that check, then keep the working source files, usage notes and known limits.

Check: Keep a working copy and recovery instructions; public deployment is a separate reviewed action.

My input:
Observed result:
Correction and next action:

## Save the working record
Source, owner and date:
Exact version:
What passed:
What failed or remains unknown:
Permission needed before external use:
Next review date:

Help me specify a local open-house preparation checklist for fictional agent Jordan Lee. Inputs are an event date, start time and three preparation tasks. First ask for missing requirements. Define ordinary, empty, invalid and saved states and observable acceptance checks. Then propose one input-to-preview-to-print slice. Use fictional data, preserve entered facts and keep secrets, network calls, tracking, payment, CRM and sending out of scope. Explain how I can inspect and test the generated files. Do not publish.

You can start with a clear specification. You still need to inspect and test the result, and obtain technical help when the work exceeds your understanding.

Choose a small local tool with fictional inputs, such as the preparation checklist below. Keep CRM connections, payments and sending out of the first exercise.

No. Compare its actual behavior with the acceptance checks, record failures and make one specific correction.

No. A tested local draft is a useful learning result. Review hosting, data handling and the exact artifact before any public release.

No verified recording or original deck was recovered for this occurrence. This is a current practice companion to the associated class, not a recreation of what appeared on screen.