Solid Principles
Apply the SOLID principles (Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, Dependency Inversion) by Robert C. Martin when designing classes, structuring inheritance hierarchies, defining interfaces, organizing dependencies, or reviewing object-oriented code. Includes intent, bad/good examples, common pitfalls, and when to relax each principle.
Install
/plugin marketplace add vnovakovits/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add vnovakovits/claude-skills --skill solid-principlesgit clone --depth 1 https://github.com/vnovakovits/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/plugins/engineering-practices/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 (Robert C. Martin) Apply SOLID when designing classes, choosing between inheritance and composition, defining interfaces, structuring dependencies, or reviewing object-oriented code. SOLID is a set of heuristics for making code easier to change. They are guidelines, not laws — apply them where the design tension they address is real. ## Core Philosophy **Software gets changed.** SOLID exists to make change cheap and safe. **The cost of bad design is paid at every change.** A small upfront investment in structure pays back many times over the system's life. **Apply only when the tension is real.** Premature abstraction in pursuit of SOLID purity creates more pain than it prevents. Wait until a second or third reason to change appears, then refactor. --- ## S — Single Responsibility Principle (SRP) > *A module should have one, and only one, reason to change.* The classical short form is "a class should do one thing." Martin's more precise modern formulation: **a module should be responsible to one and only one *actor*** — one source of business decisions that can demand change. ### Why it matters When a class serves two actors, a change requested by one can break behavior the other relies on. Code that should be independent ends up coupled through a single class. ### Bad
Details
- Skill name
solid-principles- Repository
- vnovakovits/claude-skills
- Path
plugins/engineering-practices/skills/solid-principles/SKILL.md- License
- MIT
- Repo updated
- 16 November 2026
FAQ
What does the Solid Principles skill do?
Apply the SOLID principles (Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, Dependency Inversion) by Robert C. Martin when designing classes, structuring inheritance hierarchies, defining interfaces, organizing dependencies, or reviewing object-oriented code. Includes intent, bad/good examples, common pitfalls, and when to relax each principle.
How do I install the Solid Principles skill?
Claude Code plugin: /plugin marketplace add vnovakovits/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 vnovakovits/claude-skills, which has 5 GitHub stars and 2 forks.
Related skills
Accidental Cio
5vnovakovits/claude-skills
Apply Scott Millett's "The Accidental CIO — A Lean and Agile Playbook for IT Leaders" (Wiley, 2024) when designing or reviewing how a technology organisation decides, funds, governs and delivers work. Covers the five components of an adaptive IT operating model (organised, work, govern, talent, lead) and its four themes (outcomes over output, intrinsic motivation, being not doing agile, manage flow not people); matching method and governance to context via Cynefin and Wardley evolution; governance as demand management + funding + measurement + decision rights, shifting from project funding to
Agent Retro
5vnovakovits/claude-skills
Run a retrospective on a coding-agent session and improve the agent's environment, not the code. Combines Derby & Larsen's five-stage retrospective, Shigeo Shingo's poka-yoke (turn a mechanical mistake into a check that makes it impossible), and Matt Pocock's retro categories — navigation, automated checks, coding standards, steering files, tool economy, information access. Covers mining the session transcript for corrections, wrong turns and slow searches; deciding where each fix belongs (analyzer, hook, CI, reviewer standards, CLAUDE.md pointer, skill, doc or memory); the no-op test for stee
API Design
5vnovakovits/claude-skills
Design APIs that are clear, evolvable, and idiomatic to their protocol — covering REST (Fielding, Richardson Maturity Model, Massé), GraphQL, gRPC/protobuf, versioning strategies, pagination, error responses (RFC 7807 Problem Details), idempotency, authentication, documentation (OpenAPI), and the pragmatic trade-offs between RESTful purity and developer ergonomics. Use when designing a new endpoint, choosing between REST/GraphQL/gRPC, defining versioning, structuring error responses, deciding pagination strategy, or evaluating an existing API's evolvability.
Data Metric Definition
5eshmith7/claude-skills-library
Turn a vague dashboard request into an unambiguous metric definition and build spec before anything gets built. Use for dashboard requests, defining a metric, or mismatched numbers.
Software Crypto Web3
8Freddy-CHEN-ux/00_claude_skills
Production-grade blockchain and Web3 development with Solidity (Ethereum/EVM), Rust (Solana), CosmWasm (Cosmos), including smart contract architecture, security patterns, gas optimization, testing strategies, DeFi protocols, and deployment workflows.
Finance Cash Flow Forecast
5eshmith7/claude-skills-library
Build a 13-week rolling cash forecast with three scenarios, dated shortfall warnings and ranked actions. Use for cash position, runway, collection planning or payroll cover.
Browse the most popular Claude skills, all finance & crypto skills, or write your own with the skills generator.