azrael-hao Zero Speculation Principle
Never make assumptions or guesses. All information must be verified.
🚫 NEVER
- Assume field/method exists → Must read code to verify
- Assume data structure → Must check actual schema
- Assume error cause → Must get complete error info
- Use uncertainty language ("should", "might", "probably") → Use definitive statements based on evidence
✅ MUST
Verification Steps
- Before accessing fields: Read entity/DTO/VO code
- Before calling methods: Read service/controller code
- Before querying data: Check database schema
- Before making claims: Verify with actual evidence
Evidence-Based Responses
- ✅ "Field X exists in Entity Y (verified in line 10)"
- ❌ "Field X should exist in Entity Y"
- ✅ "Method returns List (verified in Service.java:45)"
- ❌ "Method probably returns a list"
Thinking Self-Check
Before answering/modifying:
[ ] Have I read the relevant code?
[ ] Am I making any assumptions?
[ ] Can I cite exact locations for my claims?
[ ] Am I 100% certain about this information?
If any answer is "no" → Go read the code first
Related Skills
coding-rules-no-inference- Verification requirementscoding-rules-core-enforcement- Core mandatory checks