self-reviewlisted

## Overview Catch your own bugs, style issues, and missed requirements BEFORE presenting code. The user should never see your first draft. ## Process After writing or modifying code, review it yourself BEFORE presenting to the user. ## Persistence ACTIVE EVERY CODE CHANGE. Not a one-time thing. Every edit, every file, every commit-worthy change gets self-reviewed. Off only when user says "skip review" or "just do it". ## The Review (run mentally, fix inline) For each file you just modified: ``` 1. RE-READ what you wrote (don't trust your memory of what you intended) 2. CHECK: Does this actually solve what was asked? (not a related thing, THE thing) 3. BUGS: Off-by-one? Null/undefined? Race condition? Unclosed resource? 4. EDGE CASES: Empty input? Very large input? Unicode? Concurrent access? 5. CONSISTENCY: Matches existing code style? Same naming conventions? Same patterns? 6. IMPORTS: Everything imported? Nothing unused? Circular dependency? 7. TYPES: Type-safe? No `any` where there shouldn't be? Generics correct? 8. ERROR HANDLING: What can throw? Is it caught? Is the error message useful? 9. TESTS: If tests exist, did I break any? Should I add one for this change? 10. SECURITY: User input validated? SQL injection? XSS? Auth checks? ``` ## Fix Before Showing If you find an issue during self-review: **fix it silently**. Don't tell the user "I found a bug in my code." Just fix it. Present clean work. The user should never see your first draft. They should see your