clean-code

Apply clean-code rules to reduce complexity and improve maintainability.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pragmatic coding standards that reduce ambiguity and prevent over-engineering, enabling teams to write clear, maintainable code quickly.

Core Features & Use Cases

  • Enforces key principles: SRP, DRY, KISS, YAGNI, and clean guard clauses to keep functions small and focused.
  • Establishes naming conventions, reduces code smells, and promotes flat, readable code structures.
  • Use Case: when onboarding new engineers or refactoring legacy modules, apply this guide to align code with best practices quickly.

Quick Start

Refactor a module by applying the core rules to extract responsibilities, clarify names, remove unnecessary comments, and simplify control flow.

Frequently Asked Questions about clean-code

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

FAQPage Schema
What are clean code principles and how do they reduce code complexity?

Clean code principles like SRP, DRY, KISS, and YAGNI reduce software complexity by keeping functions small and focused, establishing naming conventions, and preventing over-engineering for better maintainability.

How do I refactor a legacy module to follow clean coding standards?

Refactor legacy modules by applying clean code rules to extract responsibilities, clarify naming conventions, remove unnecessary comments, and simplify control flow using guard clauses to align with best practices quickly.

When should I use guard clauses to simplify control flow?

Guard clauses should be used to flatten code structures and reduce nesting, enabling teams to write clear, maintainable code quickly by handling edge conditions early and keeping functions focused.

Can these coding standards help with onboarding new engineers?

Yes, coding standards reduce ambiguity and provide pragmatic guardrails for automated improvements, making them highly effective for aligning new engineers with best practices during onboarding or legacy refactoring.

What is the best way to enforce function size limits and naming conventions?

The best way to enforce function size limits and naming conventions is applying SRP alongside small function constraints, targeting common coding scenarios across modules to promote flat, readable code structures.