code-design-principles

Provide structured code design principles for software design reviews.

Updated Nov 2, 2025
One-click install
npx skills add https://github.com/SelrahcD/claude-marketplace --skill code-design-principles
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-design-principles
Source: https://github.com/SelrahcD/claude-marketplace/tree/main/selrahcd-dot-claude/skills/code-design-principles
Command: npx skills add https://github.com/SelrahcD/claude-marketplace --skill code-design-principles

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This knowledge base provides structured guidance on core code design principles to support consistent architectures and maintainable code.

Core Features & Use Cases

  • Documented principles such as Command Query Separation (CQS), Hexagonal Architecture, DDD, Identity management, Naming conventions, and OOP discipline to serve as a reference for code design reviews.
  • Use during code design reviews to evaluate conformity, generate improvement recommendations, and align teams on a common language.
  • Real-world scenarios include ensuring domain invariants, clean boundaries, and proper aggregation and value object usage.

Quick Start

Review a given codebase and annotate how it aligns with CQS, Hexagonal Architecture, DDD, identity management, naming conventions, and OOP discipline.

Frequently Asked Questions about code-design-principles

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

FAQPage Schema
What core principles guide maintainable software architecture?

Maintainable software architecture principles include Command Query Separation, Hexagonal Architecture, Domain-Driven Design, identity management, naming conventions, and OOP discipline to ensure clean boundaries and consistent code.

How do I apply DDD and Hexagonal Architecture during a code review?

Apply DDD and Hexagonal Architecture during code design reviews by annotating a given codebase to evaluate conformity, check domain invariants, verify clean boundaries, and generate improvement recommendations.

When do I need to check Command Query Separation in my codebase?

You need to check Command Query Separation when evaluating code design conformity to ensure methods either change state or return data, aligning teams on a common language and maintainable boundaries.

Can I use this reference for aligning team naming conventions and OOP discipline?

Yes, you can use this structured reference to align teams on naming conventions and OOP discipline, serving as an educational baseline for consistent architectures across software projects.

What is the best way to document domain invariants and proper aggregation usage?

The best way to document domain invariants and proper aggregation is by applying structured design principles like DDD to generate improvement recommendations and ensure clean boundaries in real-world scenarios.