Code Quality Principles
Foundation skill governing code quality standards during autonomous development.
Iron Law
EVERY CHANGE MUST BE INTENTIONAL. If you can't explain why a line changed, revert it.
Always leave code better than you found it. Fix issues in files you are already modifying — but only changes that pass the proximity test.
Before You Write Code
Answer these questions first. If you can't, return to EXPLORE:
- What is the specific task/criterion this code serves?
[Description truncada. Veja o README completo no GitHub.]