Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →decebals/solid-principles
SOLID principles checklist with Java examples.
Passed 22 of 22 test cases with the skill, and 21 of 22 without it.
1 fixed21 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
A test case the skill fixed. Same model, same prompt, with and without the skill.
We are inspecting a legacy Java codebase to spot classes violating the Single Responsibility Principle. What structural traits or code smells in a class indicate that it likely carries too many responsibilities?
| Checked | Without skill | With skill |
|---|---|---|
| Identify classes that have imports from multiple distinct domain packages | Passed | Passed |
| Identify class names containing conjunctions like 'And' | Missed | Passed |
The instructions your model reads when the skill loads.
Review and apply SOLID principles in Java code.
| Letter | Principle | One-liner |
|---|---|---|
| S | Single Responsibility | One class = one reason to change |
| O | Open/Closed | Open for extension, closed for modification |
| L | Liskov Substitution | Subtypes must be substitutable for base types |
| I | Interface Segregation | Many specific interfaces > one general interface |
| D | Dependency Inversion | Depend on abstractions, not concretions |
"A class should have only one reason to change."
// ❌ BAD: UserService does too much
public class UserService {
public User createUser(String name, String email) {
// validation logic
if (email == null || !email.contains("@")) {
throw new IllegalArgumentException("Invalid email");
}
test cases passed, vs 21 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.