convention-solid-isp
CommunitySplit interfaces, simplify client code.
Software Engineering#software design#api design#clean architecture#solid#principle#isp#interface segregation
AuthorsunLeee
Version1.0.0
Installs0
System Documentation
What problem does it solve?
ISP (Interface Segregation Principle) states that clients should not depend on interfaces they do not use. It helps prevent fat, monolithic interfaces by splitting large contracts into focused, cohesive ones tailored to specific clients or responsibilities. This reduces coupling and makes systems easier to maintain and evolve.
Core Features & Use Cases
- Split large interfaces into client-specific, cohesive interfaces to minimize unused methods.
- Improve testability, readability, and maintainability by reducing surface area and dependencies.
- Use Case: design an API with separate Reader, Writer, and Validator interfaces so clients only depend on the parts they actually use.
Quick Start
Refactor a monolithic interface into small, client-specific interfaces and ensure implementations depend only on the relevant contracts.
Dependency Matrix
Required Modules
None requiredComponents
Standard package💻 Claude Code Installation
Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.
Please help me install this Skill: Name: convention-solid-isp Download link: https://github.com/sunLeee/optimization/archive/main.zip#convention-solid-isp Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
Agent Skills Search Helper
Install a tiny helper to your Agent, search and equip skill from 471,000+ vetted skills library on demand.