Ask for tests
Tests pin behavior so future edits don't silently break it.
Difficulty 2/5
Short
Plain English
Tests pin behavior so future edits don't silently break it. Picture it like this: Building inspectors checking each phase. In the apps you ship (Agentify, wedding portals, CRM), you will bump into this on almost every screen — name it clearly when you prompt your coding agent.
Analogy
Building inspectors checking each phase.
Go deeper
Tests pin behavior so future edits don't silently break it.
Common mistakes
- Letting the AI rename this concept three different ways in one PR.
- Building UI before you can say what is stored and who can change it.
AI-agent trap
Agents may invent jargon here. Ask them to explain the concept in plain English first, then map it to your schema and one real screen.
Summary
Tests pin behavior so future edits don't silently break it. Building inspectors checking each phase. Ask yourself: where does this live in the database, which function changes it, and which screen shows it?
Confidence: