← LibraryBuilder · B5
Tests as verification
Build-along · ~10 min at your own keyboard
Anything with rules, a handout sorter, an exit-ticket formatter, a pacing table that reads dates off the district calendar. 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 pacing table that is off because a break was typed from memory is a unit that ends on the wrong week with your name on it.
Do this
0/4Share what happened
Paste your 3 hand-written cases and the pass/fail results across both runs.