clean-code

Enforce pragmatic coding standards for concise, maintainable code.

34|29|Updated Jul 14, 2025
One-click install
npx skills add https://github.com/adelpro/open-tarteel --skill clean-code-adelpro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clean-code
Source: https://github.com/adelpro/open-tarteel/tree/main/.agent/skills/clean-code
Command: npx skills add https://github.com/adelpro/open-tarteel --skill clean-code-adelpro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pragmatic coding standards - concise, direct, no over-engineering, no unnecessary comments. They reduce cognitive load and maintenance costs by enforcing simple, predictable rules and discouraging unnecessary boilerplate.

Core Features & Use Cases

  • SRP (Single Responsibility) and DRY (Don't Repeat Yourself) guide function/class design to stay focused and reusable.
  • KISS (Keep It Simple) and YAGNI (You Aren't Gonna Need It) principles to avoid over-engineering and feature creep.
  • Naming & style rules to improve readability, including clear variable/function names and consistent boolean predicates.
  • Code structure expectations, guard clauses, and avoidance of deep nesting to improve maintainability.
  • Self-checks and guardrails for code quality, including pre-edit thinking and mandatory checks before completing tasks.

Quick Start

Start a new module by writing a small, focused function that adheres to SRP, then refactor to remove duplication and unnecessary comments.

Frequently Asked Questions about clean-code

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

FAQPage Schema
How do I enforce SRP and DRY principles during code refactoring?

The Skill enforces SRP and DRY by applying pragmatic coding standards that guide function and class design to stay focused and reusable, reducing duplication and unnecessary boilerplate during refactoring and module creation.

What is the best way to avoid over-engineering and feature creep in software development?

The best way to avoid over-engineering is to apply KISS and YAGNI principles, which keep code simple and discourage building features that are not yet needed, thereby reducing cognitive load and maintenance costs.

How do I improve code readability and maintainability with naming rules and structured error handling?

You improve code readability by applying naming and style rules, using clear variable names and consistent boolean predicates, alongside structured error handling and guard clauses to avoid deep nesting and reduce unnecessary comments.

Can I use clean coding standards for both module creation and code reviews?

Yes, you can use these coding standards for both module creation and code reviews. The guidelines satisfy readability and maintainability requirements, providing self-checks and pre-edit guardrails to ensure concise, direct code without over-engineering.

Why does my code have high maintenance costs and cognitive load even after refactoring?

High maintenance costs often persist when refactoring ignores KISS and YAGNI principles, leaving unnecessary boilerplate and deep nesting. Enforcing simple, predictable rules and removing unused features reduces cognitive load and improves maintainability.