Does this skill help with naming conventions?

No, naming conventions are handled by the separate naming-conventions skill; this skill specifically focuses on structural design and architectural patterns.

When should I use this skill?

You should use it whenever you are creating new modules, refactoring existing logic, fixing bugs, or if you suspect your code is becoming too complex.

How does it handle the DRY (Don't Repeat Yourself) principle?

It follows the 'Rule of Three,' suggesting duplication over coupling until a pattern clearly emerges across three or more use cases to avoid premature abstraction.

Can it help with object-oriented design?

Yes, it is specialized in SOLID principles for OOP, but it also applies pragmatic design concepts suitable for functional and modular programming styles.

Clean Code Standards

Name: Clean Code Standards
Author: marcioaltoe

bymarcioaltoe

•

開発者ツール

Applies SOLID principles and Clean Code patterns to ensure maintainable, simple, and pragmatic software architecture.

概要

This skill transforms Claude into an expert software architect, guiding the development of modular and maintainable codebases. It proactively enforces industry standards like SOLID, KISS, and YAGNI, helping developers avoid common anti-patterns such as premature abstraction and over-engineering. By prioritizing duplication over coupling and advocating for the 'Rule of Three' before DRYing code, it ensures that your project remains flexible and easy to refactor as requirements evolve. It is essential for any developer looking to maintain high code quality and architectural integrity during feature implementation or refactoring.

主な機能

Clean Code pattern implementation (KISS, YAGNI, DRY)
7 GitHub stars
Prevention of over-engineering and premature abstraction
Practical refactoring advice for reducing technical debt
Proactive SOLID principle enforcement (SRP, OCP, LSP, ISP, DIP)
Guidance on Modular Monolith architecture and context isolation

ユースケース

Designing new classes or modules with clear separation of concerns
Refactoring complex legacy code into simpler, more maintainable structures
Reviewing existing logic to identify and remove unnecessary abstractions

概要

主な機能

Clean Code pattern implementation (KISS, YAGNI, DRY)
7 GitHub stars
Prevention of over-engineering and premature abstraction
Practical refactoring advice for reducing technical debt
Proactive SOLID principle enforcement (SRP, OCP, LSP, ISP, DIP)
Guidance on Modular Monolith architecture and context isolation

ユースケース

Designing new classes or modules with clear separation of concerns
Refactoring complex legacy code into simpler, more maintainable structures
Reviewing existing logic to identify and remove unnecessary abstractions