clean-code-oop
New🧱 Claude Skill for clean OOP — full SOLID with one pragmatic carve-out (SRP = cohesion). Cohesive classes + layered architecture across 9 languages.
Summary
This skill enforces clean object-oriented programming by applying SOLID principles with a pragmatic focus on high cohesion (SRP as cohesion) and layered architecture.
- It helps developers write maintainable, testable code across 9 languages by automating refactoring, design pattern suggestions, and architecture reviews.
Install & Usage
mkdir -p .claude/skillsmkdir -p .claude/skills && curl -o .claude/skills/clean-code-oop.md https://raw.githubusercontent.com/bajelanmehran/clean-code-oop/main/SKILL.md/clean-code-oopUse Cases
Usage Examples
/clean-code-oop refactor UserManager.java into cohesive classes following SRP
Review my Python codebase for Open/Closed Principle violations and suggest fixes
Design a clean OOP architecture for a payment processing system in TypeScript with layered structure
Security Audits
Frequently Asked Questions
What is clean-code-oop?
This skill enforces clean object-oriented programming by applying SOLID principles with a pragmatic focus on high cohesion (SRP as cohesion) and layered architecture. It helps developers write maintainable, testable code across 9 languages by automating refactoring, design pattern suggestions, and architecture reviews.
How to install clean-code-oop?
To install clean-code-oop: create the skills directory (mkdir -p .claude/skills), then run: mkdir -p .claude/skills && curl -o .claude/skills/clean-code-oop.md https://raw.githubusercontent.com/bajelanmehran/clean-code-oop/main/SKILL.md. Finally, /clean-code-oop in Claude Code.
What is clean-code-oop best for?
clean-code-oop is a skill categorized under General. Created by bajelanmehran.
What can I use clean-code-oop for?
clean-code-oop is useful for: Refactor a monolithic class into cohesive single-responsibility classes with clear interfaces.; Review a codebase for SOLID violations and generate a report with specific fixes.; Design a layered architecture (e.g., controller-service-repository) for a new feature.; Suggest appropriate design patterns (e.g., Strategy, Factory, Observer) for a given problem.; Convert procedural code into clean OOP with dependency injection and polymorphism.; Enforce consistent naming and packaging conventions across a multi-language project..