clean-code

Enforce SRP, DRY, KISS, and YAGNI coding standards.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/raccioly/coach-gravity --skill clean-code-raccioly
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clean-code
Source: https://github.com/raccioly/coach-gravity/tree/main/content/starter-kit/skills/clean-code
Command: npx skills add https://github.com/raccioly/coach-gravity --skill clean-code-raccioly

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides pragmatic coding standards to help AI-generated or human-written code be concise, readable, and free from over-engineered patterns, reducing bugs and maintenance cost.

Core Features & Use Cases

  • Enforces Single Responsibility Principle (SRP) to keep functions and classes focused.
  • Promotes DRY, KISS, and YAGNI to avoid duplication and unnecessary complexity.
  • Identifies and avoids common anti-patterns, with guidance for naming, structure, and minimal comments.
  • Includes guardrails for safe, predictable code with early exits and clear error handling.

Quick Start

Apply these standards to a current coding task by making functions small, reuse-friendly, and clearly named to produce clean, maintainable output.

Frequently Asked Questions about clean-code

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

FAQPage Schema
How do I enforce coding standards like SRP and DRY in AI-generated code?

To enforce coding standards in AI-generated code, apply the Single Responsibility Principle and DRY to keep functions focused and avoid duplication, ensuring concise and maintainable software engineering outputs.

What is the best way to prevent over-engineering when writing maintainable code?

The best way to prevent over-engineering is to apply KISS and YAGNI principles, avoiding unnecessary complexity and anti-patterns to produce clean, reliable code with minimal comments and clear naming conventions.

How do I add guardrails to make functions safe and predictable during refactoring?

To add guardrails during refactoring, implement early exits, clear error handling, and robust validation in small, testable functions to ensure safe, predictable, and reliable code execution.

Does applying clean code standards help reduce bugs and maintenance costs?

Yes, applying clean code standards reduces bugs and maintenance costs by enforcing concise, readable patterns and anti-pattern avoidance, which minimizes over-engineering and improves overall code quality.

When should I avoid adding comments to maintain code quality?

You should avoid comments when your code quality relies on clear naming conventions and small functions, allowing the logic to remain self-documenting and reducing reading friction for human-written or AI-generated code.

Can I use these refactoring standards for any software engineering task?

Yes, you can apply these refactoring standards across software engineering tasks, as they guide structural improvements, naming, and validation universally to ensure concise and maintainable code quality.