best-practices

Standardize software engineering best practices across codebases with explicit rules and workflows.

Updated Feb 2, 2026

Search Tags:#code-quality #best-practices #design-principles #solid #software-engineering #defensive-programming

Ready to run

npx skills add https://github.com/raultorres2603/ComplAI --skill best-practices-raultorres2603

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: best-practices
Source: https://github.com/raultorres2603/ComplAI/tree/main/.opencode/skills/best-practices
Command: npx skills add https://github.com/raultorres2603/ComplAI --skill best-practices-raultorres2603

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Enforce software engineering best practices across codebases to improve quality, maintainability, and team discipline.

Core Features & Use Cases

Principle library: SRP, OCP, LSP, ISP, DIP, KISS, DRY, YAGNI, SoC, and composition over inheritance as a unified quality language.
Workflow guidance: checklists for planning, reviews, refactoring, and architecture decisions.
Educational references: links to deeper explanations in the included references for solid, kiss, dry, yagni.

Quick Start

Audit your current project against the defined principles and begin a targeted improvement plan.

Frequently Asked Questions about best-practices

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

FAQPage Schema

What are the core software engineering best practices for improving code quality?▼

Core software engineering best practices include SOLID principles (SRP, OCP, LSP, ISP, DIP), KISS, DRY, YAGNI, Separation of Concerns, and composition over inheritance to standardize design and maintainability.

How do I apply SOLID principles and design rules during code reviews?▼

Apply SOLID principles and design rules during code reviews using structured checklists to guide planning, refactoring, and architecture decisions, ensuring teams enforce universal quality standards consistently across languages.

Can I use these software engineering principles across different programming languages?▼

Yes, these software engineering principles are language-agnostic. They apply universally across codebases to standardize team discipline, architecture discussions, and defensive programming regardless of the specific programming language.

What's the best way to audit an existing codebase against design principles like DRY and YAGNI?▼

The best way to audit an existing codebase against DRY and YAGNI is to evaluate current modules against a defined principle library, then begin a targeted improvement plan using the provided refactoring checklists.

When should I not use composition over inheritance in software architecture?▼

While composition over inheritance is a standard best practice for flexible architectures, you should review specific architecture constraints and project scale, as strict application of any design principle without context can introduce unnecessary complexity.