skills.rest
sunLeee
sunLeeeCOMMUNITY
Explore all skills by this author →
GitHub

convention-design

Summarize SRP, KISS, DRY, YAGNI, and SoC for class and module organization.

Updated Mar 19, 2026
Search Tags:#yagni#design-principles#srp#kiss#dry#soc
One-click install
npx skills add https://github.com/sunLeee/optimization --skill convention-design
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: convention-design
Source: https://github.com/sunLeee/optimization/tree/main/.claude/skills/quality/style/design
Command: npx skills add https://github.com/sunLeee/optimization --skill convention-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers often struggle to decide how to apply design principles to organize code. This quick-reference guide provides core principles to shape sensible class and function boundaries.

Core Features & Use Cases

  • Quick-reference summaries of SRP, KISS, DRY, YAGNI, and SoC.
  • Practical guidance on when to split responsibilities and how to avoid god classes.
  • Use Case: when a module feels large or violates single-responsibility, consult this guide to identify refactoring opportunities.

Quick Start

Ask for a concise interpretation of each principle and concrete steps to apply them to a sample code block.

Frequently Asked Questions about convention-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What are the core software design principles for organizing classes and modules?▼

Core software design principles for organizing classes and modules include SRP, KISS, DRY, YAGNI, and SoC. They provide a quick-reference guide to shape sensible boundaries and deliver clear summaries for clean code structure.

How do I refactor a god class that violates the single responsibility principle?▼

To refactor a god class violating the single responsibility principle, consult a quick-reference guide to identify split responsibilities. Apply SRP to separate concerns and establish sensible class boundaries within your codebase.

When should I apply the YAGNI principle in software engineering?▼

Apply the YAGNI principle in software engineering when deciding class and function boundaries to avoid over-engineering. It delivers clear summaries and practical application tips to prevent unnecessary features in both small and large codebases.

How do I get concrete steps to apply DRY and KISS to a sample code block?▼

To get concrete steps to apply DRY and KISS to a sample code block, ask for a concise interpretation of each principle. The guide provides practical application tips for avoiding duplication and keeping code simple.

Does this design principles guide work for both small and large codebases?▼

Yes, this design principles guide works for both small and large codebases. It applies to class and module organization tasks, helping developers decide how to apply design principles to establish sensible function boundaries.

Related Skills

Explore More Design & Creative Skills→
AJV009AJV009
1

refactor

Detect god classes and fat controllers in Drupal custom code.

Community
Advanced
OlegHQOlegHQ

go-clean-architecture

Organize Go code into layered handler, service, and repository boundaries.

Community
Advanced
shanevshanev
76

unslopify

Detect sloppy code patterns across TypeScript/JavaScript, Go, and Rust.

Community
Basic
Bbeierle12Bbeierle12
8

software-architecture

Guide software architecture design with SOLID principles and Clean Architecture layers.

Community
Basic