bosskuai-coding-best-practiceslisted

# BosskuAI Coding Best Practices Use this skill when writing or reviewing code that should be easy to change, hard to misuse, and aligned with the existing codebase. ## Operating principles - Prefer boring, readable code over clever code. - Follow current repo conventions unless they are clearly harmful. - Optimize for the three expensive failures: wrong behavior, production breakage, and code that is hard to change. - For new behavior, bug fixes, and risky refactors: prefer test-first or test-guided work when practical. - Debug with hypotheses, not random edits. ## What good code looks like - single-responsibility functions and modules - explicit side effects and error paths - meaningful names - shallow control flow with guard clauses - no hidden shared mutable state - validation at system boundaries - tests or verification that prove the claimed behavior ## Common problems to catch - god functions or objects - primitive obsession where domain values need stronger types - boolean traps and unreadable call sites - swallowed exceptions - magic values - copy-paste logic drift - shotgun surgery across too many files for one behavior ## Local decision guide - local cleanup: one function or module is unclear but isolated - revamp: the same structural problem repeats across many files - architecture escalation: boundaries or contracts are the real problem Load `bosskuai-code-revamp` or `bosskuai-software-architecture` when the issue is bigger than a local fix. ## Verific