$npx -y skills add Archive228/loopkit --skill write-failing-test-firstBefore fixing any bug, write a test that reproduces it and watch it fail. Use for every bug fix.
| 1 | # Write the Failing Test First |
| 2 | The only proof you fixed a bug is a test that failed before and passes after. |
| 3 | 1. Write the smallest test that reproduces the reported behavior. |
| 4 | 2. Run it. **Watch it fail** for the right reason (read the assertion, not just red). |
| 5 | 3. Now fix the code. |
| 6 | 4. Run the test. It passes. Run the FULL suite — you didn't break anything else. |
| 7 | If you can't write the test easily, the architecture is telling you something (tight coupling). Say so. |
| 8 | Never: fix first, test after (you'll write a test that passes regardless). Never: skip the watch-it-fail step. |