Solid Principles
SOLID principles (Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, Dependency Inversion) for object-oriented design.
Install
/plugin marketplace add sethdford/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add sethdford/claude-skills --skill solid-principlesgit clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/engineer/code-quality/skills/solid-principles ~/.claude/skills/solid-principlesPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# SOLID Principles Five foundational principles for maintainable, extensible object-oriented design. ## Context You are helping the engineer apply SOLID principles to their codebase. If code is provided, assess which principles are violated and suggest refactorings. Reference Robert C. Martin's work. ## Domain Context - **Single Responsibility**: A class should have only one reason to change - **Open/Closed**: Open for extension, closed for modification (use polymorphism) - **Liskov Substitution**: Derived classes must be substitutable for base classes - **Interface Segregation**: Many narrow interfaces better than one fat interface - **Dependency Inversion**: Depend on abstractions, not concrete implementations ## Instructions 1. **Identify Responsibilities**: Does the class have more than one reason to change? If yes, extract to separate class 2. **Check Inheritance**: Can a subclass substitute for its parent without breaking callers? If not, refactor hierarchy 3. **Review Interfaces**: Are clients forced to depend on methods they don't use? If yes, split the interface 4. **Examine Dependencies**: Does the class directly instantiate its dependencies? If yes, inject them instead 5. **Look for Extensions**: Can you add new behavior without modifying existing classes? If not, apply Open/Closed 6. **Validate Contracts**: Do subclasses strengthen preconditions or weaken postconditions? (Liskov violation)
Details
- Skill name
solid-principles- Repository
- sethdford/claude-skills
- Path
engineer/code-quality/skills/solid-principles/SKILL.md- License
- MIT
- Repo updated
- 11 March 2026
FAQ
What does the Solid Principles skill do?
SOLID principles (Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, Dependency Inversion) for object-oriented design.
How do I install the Solid Principles skill?
Claude Code plugin: /plugin marketplace add sethdford/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Solid Principles popular?
It lives in sethdford/claude-skills, which has 48 GitHub stars and 10 forks.
Related skills
A B Test Design
48sethdford/claude-skills
Design rigorous A/B tests with hypotheses, variants, metrics, and sample size calculations.
A B Test Design Pm
48sethdford/claude-skills
Analytics and experimentation skill for product managers.
Abuse Case Design
48sethdford/claude-skills
Design abuse cases (negative use cases) showing how attackers misuse system features. Use when identifying attacks that exploit intended functionality or business logic flaws.
Spacing System
48sethdford/claude-skills
Create a consistent spacing system based on a base unit with contextual application rules.
Session Management
48sethdford/claude-skills
Implement secure session handling with proper token generation, storage, expiry, CSRF protection, and session invalidation.
Strategic Narrative
48sethdford/claude-skills
Build a compelling narrative that connects vision, strategy, and market positioning.
Browse the most popular Claude skills, all other skills, or write your own with the skills generator.