Enforce SOLID design and clean decomposition for Kotlin functions and classes.
npx skills add https://github.com/Astrumon/Spovishun --skill code-decomposition
Please help me install this Agent Skill. Skill: code-decomposition Source: https://github.com/Astrumon/Spovishun/tree/main/skills/code-decomposition Command: npx skills add https://github.com/Astrumon/Spovishun --skill code-decomposition
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.
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.
High-intent search queries and answers about installing and using this skill.
Kotlin clean code decomposition enforces function hygiene by limiting function length, restricting arguments to a maximum of three, maintaining one level of abstraction per function, and prohibiting hidden side effects to make code easier to test and review.
Avoiding god classes and deep nesting in Kotlin requires applying single-responsibility rules to split services, reducing parameters to data classes, and running a self-review checklist before commits to catch tightly-coupled anti-patterns.
Yes, this clean code decomposition approach is designed for Kotlin and Ktor projects, guiding naming, function size, and abstraction levels when implementing commands, refactoring services, or adding new repositories.
Reduce Kotlin function arguments by grouping parameters into data classes and eliminate hidden side effects by ensuring functions maintain a single level of abstraction and clear responsibilities, making the code easier to test and review.
Use a self-review checklist for Kotlin SOLID design before committing refactored services or new repositories to verify function size limits, argument counts, naming clarity, and single-responsibility boundaries, preventing hard-to-maintain code.
tyk-labCreate an isolated git worktree for feature development with safety checks.
CloudToLocalLLM-onlineAnalyze pull requests for complexity, risk, and code quality issues.
bryonjacobConfigure a Java stack with Maven, JUnit 5, Spotless, SpotBugs, and JaCoCo.
usetheodevEvaluate DIP boundaries and module hygiene using SOLID, Hexagonal, and Clean Architecture references.
