clean-code

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

Updated Feb 6, 2026

Search Tags:#refactoring #maintainability #conciseness #coding-standards #code-review #clean-code

Ready to run

npx skills add https://github.com/rahlplx/elite-astro-workforce-template --skill clean-code-rahlplx

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: clean-code
Source: https://github.com/rahlplx/elite-astro-workforce-template/tree/main/.agent/skills/clean-code
Command: npx skills add https://github.com/rahlplx/elite-astro-workforce-template --skill clean-code-rahlplx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pragmatic coding standards reduce over-engineering and noisy, unclear code by enforcing clear rules and best practices.

Core Features & Use Cases

SRP (Single Responsibility): Each function/class has a single responsibility.
DRY / KISS: Avoid duplication and unnecessary complexity; promote readability.
Code Review Guidance: Provide concise, actionable criteria for reviewing code quickly.
Use Case: Onboarding new engineers and maintaining long-term code health.

Quick Start

Apply the clean-code guidelines to a sample file, then run a quick self-check to verify alignment with the standards.

Frequently Asked Questions about clean-code

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

FAQPage Schema

How do I enforce clean code standards to reduce over-engineering?▼

Enforce clean code standards by applying core rules like SRP, DRY, KISS, and YAGNI to reduce over-engineering. This approach minimizes unnecessary comments and complexity, guiding teams to write clear, maintainable code across languages and projects.

What coding standards should I check during a code review?▼

Coding standards for code reviews should check for Single Responsibility, duplication, and unnecessary complexity. Apply concise, actionable criteria to verify purposeful naming, minimal comments, and adherence to DRY and KISS principles for long-term code health.

How do I apply DRY and KISS principles for better code maintainability?▼

Apply DRY and KISS principles for maintainability by ensuring each function has a single responsibility and avoiding code duplication. This reduces unnecessary complexity, promotes readability, and provides actionable prompts to guide refactoring.

Can I use these refactoring guidelines for onboarding new engineers?▼

These refactoring guidelines are suitable for onboarding new engineers and maintaining long-term code health. They provide actionable prompts and examples that guide teams to write clear, maintainable code across various languages and projects.

When should I avoid adding comments to my code?▼

Avoid adding comments to your code when the code is already clear and maintainable through purposeful naming. The guidelines enforce minimal comments, preferring concise coding standards and clear logic over noisy, unnecessary explanations.