clean-code

Enforce pragmatic coding standards for concise, maintainable code.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/ntdev204/rai_ws --skill clean-code-ntdev204
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clean-code
Source: https://github.com/ntdev204/rai_ws/tree/main/.agent/skills/clean-code
Command: npx skills add https://github.com/ntdev204/rai_ws --skill clean-code-ntdev204

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill enforces pragmatic coding standards to ensure code is maintainable, efficient, and easy to understand, preventing over-engineering and unnecessary complexity.

Core Features & Use Cases

  • Coding Principles: Adheres to SRP, DRY, KISS, YAGNI, and Boy Scout Rule.
  • Naming Conventions: Enforces clear and intent-revealing names for variables, functions, and constants.
  • Code Structure: Promotes guard clauses, flat code, composition, and colocation.
  • AI Coding Style: Guides AI behavior for feature implementation, bug fixing, and requirement clarification.
  • Verification: Includes mandatory self-checks and script execution for quality assurance.

Quick Start

Apply the clean-code skill to refactor the provided code snippet for improved readability and maintainability.

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 to prevent over-engineering and improve code maintainability?

To enforce coding standards and prevent over-engineering, apply pragmatic principles like SRP, DRY, KISS, and YAGNI to ensure your code is concise, direct, and solution-focused. This approach emphasizes strict naming conventions and guard clauses for better readability.

What are the best coding principles for writing concise and direct code during feature implementation?

The best coding principles for concise and direct code include the Single Responsibility Principle (SRP), Don't Repeat Yourself (DRY), Keep It Simple, Stupid (KISS), and You Aren't Gonna Need It (YAGNI). These standards prevent unnecessary complexity and keep your codebase solution-focused.

How do I refactor code to improve readability and apply the Boy Scout Rule?

Refactoring code to improve readability involves applying the Boy Scout Rule to leave the code cleaner than you found it. This requires using guard clauses, flattening code structure, and enforcing intent-revealing naming conventions for variables and functions.

Does this clean code approach require specific frameworks or dependencies to function?

This clean code approach does not require specific frameworks or dependencies to function. It applies to all code development tasks as a set of pragmatic coding standards, utilizing self-checks and script verifications to ensure maintainability and efficiency without external constraints.

How do I verify code quality and maintainability before completing a development task?

To verify code quality and maintainability before task completion, execute mandatory self-checks and script verifications. This ensures your code adheres to strict function rules, structure patterns, and avoids unnecessary comments or over-engineering.