Ask what could break this before you trust it

Right after a tool starts working, I ask Claude Code one more question: what could break this. A missing field, a duplicate entry, two people using it at once. I want the weak spots named out loud.

Owners tend to stop as soon as something runs correctly one time, which feels like success but isn't the same as reliable. Asking about failure points while the coding tool still has the whole build in mind catches problems you'd otherwise only find later, usually while a client is watching. It's a small habit that turns a working demo into a tool you can actually depend on.

Try this today: once your tool passes its first real test, ask directly what could break it, then test the two most likely answers yourself before calling it finished.