skills.rest
y-kitamu
y-kitamuCOMMUNITY
Explore all skills by this author →
GitHub

design-and-coding-principles

Apply KISS, YAGNI, DRY, SOLID, and Separation of Concerns principles to code.

Updated Aug 27, 2026
Search Tags:#software design#DRY#KISS#clean code#SOLID#coding principles
One-click install
npx skills add https://github.com/y-kitamu/dotfiles --skill design-and-coding-principles
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design-and-coding-principles
Source: https://github.com/y-kitamu/dotfiles/tree/main/.copilot/skills/design-and-coding-principles
Command: npx skills add https://github.com/y-kitamu/dotfiles --skill design-and-coding-principles

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a comprehensive guide to fundamental software design and coding principles, ensuring that generated code is maintainable, readable, and efficient.

Core Features & Use Cases

  • Fundamental Principles: Covers KISS, YAGNI, DRY, SOLID, and Separation of Concerns.
  • Coding Best Practices: Includes rules for clean code, refactoring, and error handling.
  • Use Case: When asked to implement a new feature, use this Skill to ensure the code adheres to best practices like SRP and OCP, leading to a more robust and scalable solution.

Quick Start

Refer to the design-and-coding-principles skill for guidance on applying the KISS principle to a new feature.

Frequently Asked Questions about design-and-coding-principles

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

FAQPage Schema
What are the fundamental software design principles for writing maintainable code?▼

To apply clean code practices, follow rules for refactoring, error handling, and maintaining readability. These practices ensure generated code adheres to best development standards and architectural integrity.

How do I apply SOLID principles when implementing a new feature?▼

To apply SOLID principles when implementing a new feature, adhere to the Single Responsibility Principle (SRP) and Open/Closed Principle (OCP). This structured approach leads to more robust, scalable, and maintainable software solutions.

What is the best way to follow the DRY principle in software engineering?▼

The best way to follow the DRY (Don't Repeat Yourself) principle is by enforcing strict separation of concerns and utilizing refactoring rules. This eliminates redundancy, ensuring your code remains efficient and easy to maintain.

How do you handle errors according to clean code practices?▼

Handling errors according to clean code practices involves applying structured coding rules for error management alongside core design philosophies like KISS. This approach guarantees robust error resolution without compromising architectural integrity.

When should I use the YAGNI principle in software design?▼

You should use the YAGNI (You Aren't Gonna Need It) principle in software design when implementing new features to prevent over-engineering. It aligns with KISS to ensure you only build necessary, maintainable functionalities.

Related Skills

Explore More Software Engineering Skills→
ArvorCoArvorCo
96

constitution

Create or update a project constitution defining coding principles and governance rules.

Community
Advanced
dd-xiaozhidd-xiaozhi
2

fitness-run

Execute structural fitness functions to validate layer boundaries and OpenAPI contracts.

Community
Advanced
noundernounder
3

effect-testing

Test Effect.ts success and failure paths with deterministic concurrency handling.

Community
Intermediate
ianyimiianyimi
1

Global Conventions

Enforce global coding conventions across codebases during linting, formatting, and reviews.

Community
Basic