solid-principles
Skill15 starsChanged 5 months agoCC0-1.0View on GitHub
Audits code for adherence to the five SOLID principles and reports violations with concrete fixes. Use when reviewing class design, dependency structure, or object-oriented quality.
We split this skill into the rules it gives an agent
8 rules. 0 are common, 8 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
If no target path is given above, review the entire codebase.
- Distinctive: line 31
Check for if/else chains that could be strategy pattern
- Distinctive: line 34
Do derived classes properly extend base classes?
- Distinctive: line 39
Do clients depend on methods they don't use?
- Distinctive: line 44
Check for 'new' keyword usage vs injection
- Distinctive: line 60
Prefer minimal, drop-in fix snippets over prose.
- Distinctive: line 62
Do not invent files or functions that aren’t present.
- Distinctive: line 64
Write this into a markdown file and place it in the audits/ folder.
“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Target: $ARGUMENTS
If no target path is given above, review the entire codebase.
Evaluate this application and its adherence to SOLID principles:
Check each principle:
- SINGLE RESPONSIBILITY (SRP)
- Does each module have one reason to change?
- Identify modules violating SRP
- Example: UserController handling emails, payments, and auth
- OPEN/CLOSED PRINCIPLE
- Can we extend without modifying?
- Are there hardcoded switch statements that should be polymorphic?
- Check for if/else chains that could be strategy pattern
- LISKOV SUBSTITUTION
- Do derived classes properly extend base classes?
- Any violations of expected behavior?
- INTERFACE SEGREGATION
- Are interfaces too large?
- Do clients depend on methods they don't use?
- DEPENDENCY INVERSION
- Are we depending on abstractions or concretions?
- Is there proper dependency injection?
- Check for 'new' keyword usage vs injection
Rate SOLID compliance (1-10) with specific violations and fixes.
Provide:
A structured finding report
A scale of 1/10 on how important each finding is
Remediation: precise code-level fix or config change (snippets welcome) if possible
Constraints & style:
Be concrete and cite exact code locations and identifiers.
Prefer minimal, drop-in fix snippets over prose.
Do not invent files or functions that aren’t present; if context is missing, mark as Unable to verify and say what code would prove it.
Write this into a markdown file and place it in the audits/ folder.
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 11
- decebals/claude-code-java★ 763same name
- TheBeardedBearSAS/claude-craft★ 108same name
- robconery/kolea★ 7same name
- KhaledSaeed18/dotclaude★ 5same name
- nek1987/auto-agent-harness★ 4same name
- kayaman/skills★ 3same name
- kimtth/agent-skill-100-lines-or-less★ 2same name
- lucsedirae/agent_skill_library★ 2same name
- andr-ca/agentharness★ 1same name
- iCesofT/awesome-ai★ 1same name
1 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use design-patterns.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
ffsshhttiikkSkilldesign-patterns
Practical application and coding skills for Design Patterns
Also in 4 projects that use this
In this repository21 other files it gives its agents.
- api-and-infrastructureSkill
- authentication-flow-reviewSkill
- authorization-implementationSkill
- business-logic-vulnerabilitiesSkill
- code-duplication-detectionSkill
- code-quality-metrics-standardsSkill
- comprehensive-security-reportSkill
- database-securitySkill
- design-pattern-implementationSkill
- error-handling-resilienceSkill
- exception-flow-analysisSkill
- file-handling-business-logicSkill
- initial-security-analysisSkill
- initial-software-design-analysisSkill
- input-validationSkill
- logging-monitoringSkill
- readability-and-namingSkill
- resilience-fault-toleranceSkill
- secrets-management-auditSkill
- session-cookie-securitySkill
- testing-implementationSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.