clean-code

Enforce SRP, DRY, KISS, and naming conventions in coding reviews.

Updated Feb 12, 2026
One-click install
npx skills add https://github.com/AnvinX1/med-rag --skill clean-code-anvinx1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clean-code
Source: https://github.com/AnvinX1/med-rag/tree/main/medical_genai_app/.agent/skills/clean-code
Command: npx skills add https://github.com/AnvinX1/med-rag --skill clean-code-anvinx1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dev teams often struggle with bloated, hard-to-maintain code due to over-engineering. This skill promotes pragmatic, minimalistic coding practices that keep code clear, concise, and maintainable.

Core Features & Use Cases

  • Guardrails enforce SRP, DRY, KISS, and YAGNI; improve readability and maintainability.
  • Naming, structure, and style rules guide function design, guard clauses, and minimal nesting.
  • AI-assisted reviews and refactoring prompts to produce clean, production-ready code.

Quick Start

Refactor the provided function to meet SRP, DRY, and KISS while removing 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, DRY, and KISS coding standards in AI-assisted development?

To enforce SRP, DRY, and KISS coding standards in AI-assisted development, apply pragmatic guardrails that specify function design, guard clauses, and minimal nesting to keep code lean and maintainable.

What is the best way to refactor functions to reduce bloated and hard-to-maintain code?

The best way to refactor functions and reduce bloated code is to apply pragmatic minimalistic rules, enforcing guard clauses and minimal nesting while removing unnecessary comments to improve readability.

Can I use clean-code guidelines for team onboarding and coding reviews?

Yes, you can use clean-code guidelines for team onboarding and coding reviews to enforce naming conventions, avoid anti-patterns, and produce production-ready code through structured AI-assisted prompts.

How do naming conventions and guard clauses improve code quality during refactoring?

Naming conventions and guard clauses improve code quality during refactoring by reducing unnecessary nesting, enforcing single responsibility, and maintaining structured style guidance to prevent anti-patterns.

Why does over-engineering lead to hard-to-maintain code and how can I prevent it?

Over-engineering leads to hard-to-maintain code by introducing unnecessary complexity, which can be prevented by applying YAGNI principles and pragmatic minimalistic practices to keep code concise.