← LibraryBuilder · B5
Tests as verification
Build-along · ~10 min at your own keyboard
Anything with rules - a markup calculator, a quantity takeoff, a payment-schedule tool - can carry its own tests: 'given these 3 inputs, the output must be exactly this.' Have Claude write the checks alongside the work, and every future change gets caught the moment it breaks something. A schedule of values that is off by the wrong markup is a hard conversation at draw time.
Do this
0/4Share what happened
Paste your 3 hand-written cases and the pass/fail results across both runs.