clean-code

Enforces coding standards for clear, maintainable code structure.

Updated Dec 28, 2025
One-click install
npx skills add https://github.com/oalansilva/crypto --skill clean-code-oalansilva
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clean-code
Source: https://github.com/oalansilva/crypto/tree/main/.agent/skills/clean-code
Command: npx skills add https://github.com/oalansilva/crypto --skill clean-code-oalansilva

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pragmatic coding standards reduce over-engineering and unnecessary commentary, helping AI-generated code stay concise and maintainable.

Core Features & Use Cases

  • Enforces Single Responsibility Principle, DRY, KISS, and YAGNI to keep code focused and avoids unnecessary complexity.
  • Provides clear naming, small functions, and minimal nesting to improve readability and ease of review.
  • Use Case: When starting a new AI-assisted coding task, apply these standards to ensure consistent style across modules and reviewers.

Quick Start

Adopt the core rules to write small, well-scoped functions with clear names and minimal comments to keep code concise and maintainable.

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 in AI-assisted development workflows?

To enforce clean code standards in AI-assisted workflows, apply rule-based guidelines for naming, function size, and module structure. This ensures consistent style across AI-generated code, keeping it concise and maintainable for reviewers.

What is the best way to reduce unnecessary comments and over-engineering in generated code?

The best way to reduce over-engineering and unnecessary comments is to apply pragmatic coding standards that enforce Single Responsibility, DRY, KISS, and YAGNI principles. This keeps code focused and avoids adding unnecessary complexity.

How do I write small, well-scoped functions with clear naming conventions?

To write small, well-scoped functions with clear naming conventions, adopt rule-based standards that mandate single responsibility, minimal nesting, and guard clauses. This improves readability and eases code review across modules.

Can I use guard clauses and minimal nesting to improve code readability?

Yes, you can use guard clauses and minimal nesting to improve code readability. Pragmatic coding standards enforce these structural rules to produce concise, maintainable code that satisfies functional requirements without unnecessary commentary.

When do I need pragmatic coding standards for a new software engineering project?

You need pragmatic coding standards when starting a new AI-assisted coding task to ensure consistent style across modules and reviewers. These standards guide naming, function size, and structure to prevent over-engineering from the outset.

Why does AI-generated code become complex and hard to maintain?

AI-generated code becomes complex and hard to maintain when it lacks enforced standards for naming, function size, and structure. Applying pragmatic rules like DRY, KISS, and YAGNI reduces unnecessary commentary and over-engineering.