coding-standards

Guide writing maintainable, consistent code with DRY, SOLID, and naming conventions.

2|Updated Dec 27, 2025
One-click install
npx skills add https://github.com/yzlin/supaviber --skill coding-standards-yzlin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coding-standards
Source: https://github.com/yzlin/supaviber/tree/main/skills/coding-standards
Command: npx skills add https://github.com/yzlin/supaviber --skill coding-standards-yzlin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured guide to writing clean, maintainable code across languages, enabling teams to adopt consistent standards and reduce technical debt.

Core Features & Use Cases

  • Principles: DRY, SOLID, SRP, composition over inheritance, KISS, YAGNI, and design patterns to guide code structure.
  • Guidance: Naming conventions, modular design, and documentation practices to improve readability and maintainability.
  • Use Case: A team refactors a codebase to apply consistent design principles, resulting in easier onboarding and fewer defects.

Quick Start

Read the coding-standards guide and start applying the principles to a sample module. Example: review a function that handles data processing and refactor for SRP.

Frequently Asked Questions about coding-standards

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

FAQPage Schema
What are clean code principles for writing maintainable software?

Clean code principles like DRY, SOLID, and SRP guide developers in writing maintainable software by enforcing modular design, clear naming conventions, and consistent structure to reduce technical debt across projects.

How do I refactor a codebase to apply SOLID and DRY standards?

To refactor a codebase using SOLID and DRY standards, review existing modules for single responsibility violations, extract duplicated logic, and apply composition over inheritance to improve testability and reduce defects.

Does this coding standards guide apply to multiple programming languages?

Yes, this coding standards guide provides language-specific tips and structured principles for clean code that apply across multiple programming languages, enabling development teams to enforce consistent maintainability standards.

What is the best way to enforce consistent naming conventions and documentation practices?

The best way to enforce naming conventions and documentation practices is by adopting a structured coding standards guide that defines modular design rules, ensuring team-wide readability and easier onboarding.

When should I use composition over inheritance in software design?

You should use composition over inheritance when designing modular systems to maintain flexibility, reduce tight coupling, and adhere to SOLID principles for clean, testable, and maintainable code.