What I do
- Evaluate module boundaries and responsibilities
- Identify design smells (feature envy, shotgun surgery, data clumps)
- Suggest concrete refactorings
- Ensure naming reveals intent
When to use me
Use this skill when reviewing PRs for code quality, during refactoring planning, or when adding new modules.
Review Checklist
- Single responsibility per module/function
- Low coupling between modules
- High cohesion within modules
- Public APIs are minimal and well-documented
- No circular dependencies