メニュー
Clean Code principles and practices reference based on Robert Martin's work. Use this skill when reviewing code quality, naming conventions, refactoring, or applying SOLID principles. Auto-activates for code smell detection, style improvements, and maintainability concerns.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | clean-code |
| description | Clean Code principles and practices reference based on Robert Martin's work. Use this skill when reviewing code quality, naming conventions, refactoring, or applying SOLID principles. Auto-activates for code smell detection, style improvements, and maintainability concerns. |
A comprehensive reference for writing clean, maintainable code based on Robert Martin's "Clean Code" and related works. This skill provides language-agnostic principles with examples that apply to any programming language.
This skill automatically activates when you:
| Principle | Summary | Violation Sign |
|---|---|---|
| Single Responsibility (SRP) | One reason to change | Class does too many things |
| Open/Closed (OCP) | Open for extension, closed for modification | Modifying existing code for new features |
| Liskov Substitution (LSP) | Subtypes must be substitutable | Subclass breaks parent behavior |
| Interface Segregation (ISP) | No forced dependencies on unused methods | Fat interfaces |
| Dependency Inversion (DIP) | Depend on abstractions, not concretions | High-level modules import low-level |
| Practice | Key Points |
|---|---|
| Meaningful Names | Intention-revealing, pronounceable, searchable |
| Functions | Small, do one thing, one level of abstraction |
| Comments | Code should be self-documenting; comments explain why, not what |
| Formatting | Consistent style, vertical density, horizontal alignment |
| Error Handling | Exceptions over error codes, fail fast, don't return null |
| Unit Testing | F.I.R.S.T. principles, one assert per test, test behavior |
| Code Smells | Recognition and refactoring of common problems |
| Boy Scout Rule | Leave code cleaner than you found it |
"Leave the campground cleaner than you found it."
Every time you touch code, make it a little better. Small, incremental improvements compound over time.
Before committing code, verify:
Examples use generic pseudocode. Adapt to your language:
class, function, ->, type hintsclass, arrow functions, .class, def, ., type hintsBased on concepts from "Clean Code: A Handbook of Agile Software Craftsmanship" by Robert C. Martin, 2008.
Unified router for 7 canonical software engineering knowledge bases. Routes queries to appropriate underlying skills: gof-patterns (23 design patterns), clrs-algorithms (40 data structures), clean-code (SOLID + practices), ddia (distributed systems), pragmatic-programmer (craftsmanship), ddd (domain modeling), sicp (CS fundamentals). Auto-activates for architecture decisions, pattern selection, algorithm choice, and system design.
Software craftsmanship principles from The Pragmatic Programmer. Use this skill when discussing best practices, debugging strategies, career development, or pragmatic approaches to software development. Auto-activates for DRY violations, debugging sessions, and development workflow improvements.
Data structures and algorithms reference based on CLRS. Use this skill when implementing, discussing, or choosing data structures or algorithms. Auto-activates for algorithm selection, complexity analysis, and performance optimization. Comprehensive coverage of fundamental and advanced data structures with pseudocode examples.