skills.rest
jnPiyush
jnPiyushCOMMUNITY
Explore all skills by this author →
GitHub

core-principles

Documents software design principles (SOC, TOC, SOC, COC, LOC, DOC, LOC, VOC, YOCNI, etc. wait, let's be accurate: SRP, OCP, LSP, ISP, DIP, DRY, KISS, YAGNI and common design patterns for C# development workflows and code reviews.

Updated Jan 23, 2026
Search Tags:#csharp#refactoring#solid#design-patterns#kiss#dry
One-click install
npx skills add https://github.com/jnPiyush/AI-Squad --skill core-principles-jnpiyush
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: core-principles
Source: https://github.com/jnPiyush/AI-Squad/tree/main/ai_squad/skills/core-principles
Command: npx skills add https://github.com/jnPiyush/AI-Squad --skill core-principles-jnpiyush

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers apply fundamental software design principles to write maintainable, scalable, and robust code across projects.

Core Features & Use Cases

  • Clear guidance on SOLID, DRY, and KISS with practical C# examples.
  • Design pattern coverage including Repository, Factory, and Strategy to structure code.
  • Best practices & refactoring principles to improve testability and readability in real-world projects.

Quick Start

Refactor a monolithic C# class by applying SRP to split responsibilities into separate classes, then demonstrate OCP with an interface-based extension, and illustrate DRY by extracting shared logic into a base component. Then run a quick code review emphasizing KISS and YAGNI.

Frequently Asked Questions about core-principles

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

FAQPage Schema
How do I refactor a monolithic C# class using SOLID principles?▼

To refactor a monolithic C# class with SOLID principles, apply the Single Responsibility Principle to split responsibilities into separate classes, then use interface-based extensions for the Open/Closed Principle. This reduces complexity and improves maintainability.

What are the best ways to apply DRY and KISS in standard C# workflows?▼

Apply DRY and KISS in standard C# workflows by extracting shared logic into base components and emphasizing simplicity during code reviews. This improves testability and readability in real-world projects.

When do I need design patterns like Repository, Factory, and Strategy in C#?▼

You need design patterns like Repository, Factory, and Strategy in C# when structuring code to reduce complexity and improve maintainability. These patterns guide daily coding practices by providing clear architectural boundaries.

How does YAGNI help with C# code reviews and refactoring?▼

YAGNI helps with C# code reviews and refactoring by preventing unnecessary features, complementing KISS to reduce complexity. This ensures maintainable and scalable code across projects.

Can I use these core coding principles for improving testability in real-world projects?▼

Yes, you can use core coding principles to improve testability in real-world projects. Organizing code around SOLID, DRY, and KISS refactors logic into separate, testable components and base elements.

Related Skills

Explore More Software Engineering Skills→
Junior-Frontend-devJunior-Frontend-dev

clean-code

Enforce SOLID, DRY, and KISS principles with pre-commit lint and type checks.

Community
Intermediate
DoubleslashSEDoubleslashSE
4

clean-code

Apply DRY, KISS, and YAGNI principles to write and review C# code.

Community
Basic
nsalvacaonsalvacao

Tech Stack Detection

Identify repository tech stacks and generate structured JSON reports.

Community
Advanced
sandeshbagmaresandeshbagmare

architecture-patterns

Provide architectural guidance for backend systems using Clean Architecture, Hexagonal Architecture, and Domain-Driven Design.

Community
Advanced