무료GitHub에 공개

solid

Apply SOLID principles to write flexible, maintainable, and testable code. Use when designing classes, interfaces, and module boundaries. Covers Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, and Dependency Inversion with practical TypeScript examples and detection heuristics.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

fellipeutaka/denji

설치 방법 보기

포함된 파일(2)

SKILL.md4.2 KB
references/PRINCIPLES.md11.5 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

SOLID Principles

Five principles for building software that is easy to understand, extend, and maintain. They reduce coupling, increase cohesion, and make code testable.

When to Apply

Reference these principles when:

Designing new classes, modules, or interfaces
Refactoring code with too many responsibilities
Reviewing PRs for architectural concerns
Breaking apart god objects or fat interfaces
Deciding where to draw module boundaries
Making code more testable

Quick Reference

Principle	One-Liner	Red Flag
SRP	One reason to change	"This class handles X and Y and Z"
OCP	Add, don't modify	Growing `if/else` or `switch` chains for types
LSP	Subtypes are substitutable	Type-checking or special-casing in calling code
ISP	Small, focused interfaces	Empty method implementations or `throw new Error("Not implemented")`
DIP	Depend on abstractions	`new ConcreteClass()` inside business logic

See references/PRINCIPLES.md for detailed explanations and TypeScript examples.

Detection Checklist

Ask these questions for every class and module:

Question	Violated Principle
Does this class have multiple reasons to change?	SRP
Do I need to modify existing code to add a new variant?	OCP
Does calling code need type-checks or special cases for subtypes?	LSP
Are implementors forced to stub out unused methods?	ISP
Does high-level logic directly instantiate infrastructure?	DIP

Applying SOLID at Different Scales

Scale	SRP	OCP	LSP	ISP	DIP
Function	Does one thing	—	—	—	Takes abstractions as params
Class	One reason to change	Extend via composition	Subtypes honor contracts	Implements only what it uses	Constructor injection
Module	One bounded context	Plugin architecture	Interchangeable implementations	Thin public API	Depends inward
Service	Single domain	New features = new services	API contract stability	Minimal API surface	Abstractions at boundaries

Relationships Between Principles

SRP + ISP: Splitting responsibilities often means splitting interfaces too
OCP + DIP: Depending on abstractions is what makes extension without modification possible
LSP + OCP: If subtypes are substitutable, you can extend behavior by adding new subtypes
DIP + ISP: Small focused interfaces make dependency inversion practical

Common Anti-Patterns

Anti-Pattern	Violated Principles	Fix
God class doing everything	SRP	Extract focused classes
`switch` on type across codebase	OCP, LSP	Replace with polymorphism
Subclass that throws "not supported"	LSP, ISP	Redesign hierarchy, split interface
Fat interface with 20 methods	ISP	Split into role-based interfaces
Business logic importing DB driver	DIP	Inject repository interface
Service creating its own dependencies	DIP	Constructor injection

Best Practices

DO

Start with SRP — it's the foundation for all others
Use interfaces to define boundaries between components
Let violations emerge from real problems, then fix them
Prefer composition over inheritance for extending behavior
Keep interfaces small and role-specific
Inject dependencies through constructors

DON'T

Apply SOLID dogmatically to trivial code (a 5-line utility doesn't need an interface)
Create abstractions before you have at least two implementations
Confuse SRP with "single method" — it's about reasons to change, not size
Force Liskov compliance on classes that shouldn't be in the same hierarchy
Over-segregate interfaces into single-method fragments when a cohesive group makes sense

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

같은 저장소의 스킬

agent-browser

무료

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

fellipeutaka/denji62026년 8월 3일 업데이트

ai-repo-setup

무료

Set up and optimize repositories for AI coding agents. Creates minimal AGENTS.md, CLAUDE.md symlink, docs/REQUIREMENTS.md, docs/BUSINESS-RULES.md, feedback loops, and deterministic enforcement (Claude Code hooks, OpenCode plugins). Use when user wants to make a repo AI-friendly, set up AGENTS.md/CLAUDE.md, document requirements/business rules for AI, add pre-commit hooks for AI workflows, or optimize codebase structure for coding agents.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

fellipeutaka/denji62026년 8월 3일 업데이트

bun

무료

Bun runtime, package manager, bundler, and test runner. Use when running scripts with bun, managing packages, serving HTTP with Bun.serve, querying databases with Bun.sql/bun:sqlite/Bun.redis, shell scripting with $, using S3/file I/O, writing tests with bun:test, bundling or compiling to executable, or using any Bun-specific API (spawn, glob, semver, FFI, workers, plugins, HTMLRewriter).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

fellipeutaka/denji62026년 8월 3일 업데이트

clean-code

무료

Write clean, readable, and maintainable code following principles from Robert C. Martin's "Clean Code" and Object Calisthenics. Use when writing, reviewing, or refactoring code to improve naming, function design, formatting, error handling, and class structure. Includes code smell detection and refactoring guidance.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

fellipeutaka/denji62026년 8월 3일 업데이트

commit-work

무료

Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

fellipeutaka/denji62026년 8월 3일 업데이트

denji

무료

Manage SVG icons as framework components using Denji CLI. Use when the user needs to add, remove, list, export, import, or manage SVG icons in React, Preact, Solid, Qwik, Vue, or Svelte projects. Triggers include requests to "add an icon", "set up icons", "manage SVG icons", "remove an icon", "list icons", "export icons", "import icons", "dry-run icon add", or any task involving Iconify icons as framework components.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

fellipeutaka/denji62026년 8월 3일 업데이트

fellipeutaka의 스킬 모두 보기

이 스킬의 문제 신고

설치

명령으로 설치

npx skills add https://github.com/fellipeutaka/denji --skill solid

터미널에 붙여 넣고 실행합니다(Node.js 필요). Claude Code, Codex 등 설치할 에이전트를 고를 수 있습니다.

에이전트에게 부탁하기

다음 Agent Skill을 설치해 주세요.
https://github.com/fellipeutaka/denji/tree/main/.agents/skills/solid

먼저 SKILL.md와 첨부 파일의 내용을 확인해 수상한 처리(외부 전송, 인증 정보 읽기 등)가 없는지 확인한 뒤 Claude Code는 ~/.claude/skills/solid/, Codex는 ~/.agents/skills/solid/ 에 배치해 주세요.

이 문장을 그대로 Claude Code나 Codex에 보내면 내용을 확인한 뒤 설치해 줍니다.

GitHub에서 소스 보기

저장소: fellipeutaka/denji
스타: 6
포크: 0
카테고리: 디자인
라이선스: MIT
원문 언어: 영어
최종 업데이트: 2026년 8월 3일

스킬은 에이전트를 위한 지시와 스크립트의 묶음입니다. cccskills는 내용의 안전성을 보증하지 않습니다. 설치하기 전에 내용을 확인하세요.