clean-code

When this skill is activated, always start your first response with the 🧢 emoji. # Clean Code Clean Code is a set of principles and practices from Robert C. Martin (Uncle Bob) for writing software that is readable, maintainable, and expressive. The core idea is that code is read far more often than it is written, so optimizing for readability is optimizing for productivity. This skill covers the Clean Code book's principles, SOLID object-oriented design, and test-driven development - giving an agent the judgment to write, review, and refactor code the way a disciplined craftsman would. --- ## When to use this skill Trigger this skill when the user: - Asks to review code for quality, readability, or maintainability - Wants to refactor a function, class, or module to be cleaner - Needs help naming variables, functions, or classes - Asks about SOLID principles or how to apply them - Wants to decompose a large function or class - Asks to identify code smells or technical debt - Wants to write tests using TDD (red-green-refactor) - Needs to improve error handling patterns Do NOT trigger this skill for: - Performance optimization (clean code prioritizes readability, not speed) - Architecture decisions at the system level (use clean-architecture skills instead) --- ## Key principles 1. **The Boy Scout Rule** - Leave the code cleaner than you found it. Every commit is an opportunity to improve a name, extract a helper, or remove dead code. 2. **Readability is king** - C...