code-decomposition

What problem does it solve?

This Skill gives concrete rules and a checklist to prevent large, tightly-coupled, and hard-to-maintain Kotlin code by enforcing SOLID principles, small single-purpose functions, meaningful naming, and clear abstraction boundaries.

Core Features & Use Cases

• SOLID enforcement: Guidance for Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, and Dependency Inversion applied to Kotlin services, repositories, and command handlers.
• Function hygiene: Limits on function length, maximum argument count, single level of abstraction, and prohibition of hidden side effects to make code easier to test and review.
• Anti-pattern avoidance & checklist: Practical warnings (god classes, flag/output arguments, deep nesting) and a self-review checklist to run before commits, useful when implementing commands, refactoring services, or adding new repositories.

Quick Start

When refactoring or adding a Kotlin function, split responsibilities into small functions or services, reduce parameters to data classes, name things clearly, remove hidden side effects, and run the self-review checklist before committing.