clean-code

Enforce SRP, DRY, KISS, YAGNI, and naming conventions in code reviews.

Updated Aug 27, 2026

Search Tags:#refactoring #code-quality #coding-standards #naming-conventions #software-design #clean-code

Ready to run

npx skills add https://github.com/spike-land-ai/spike.land --skill clean-code-spike-land-ai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: clean-code
Source: https://github.com/spike-land-ai/spike.land/tree/main/.github/skills/clean-code
Command: npx skills add https://github.com/spike-land-ai/spike.land --skill clean-code-spike-land-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pragmatic coding standards cut through over-engineering, reduce noise, and make code easier to read, review, and maintain.

Core Features & Use Cases

Enforces SRP, DRY, KISS, YAGNI, and naming conventions to improve clarity.
Guides function design, guard clauses, and composition to produce small, testable units.
Use Case: a team refactors a legacy module to align with a consistent, maintainable style across services.

Quick Start

Begin by applying these standards during development and in code reviews to streamline 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 apply clean code standards during a legacy module refactoring?▼

To apply clean code standards during refactoring, enforce SRP, DRY, KISS, and YAGNI principles to reduce noise and over-engineering. This process guides function design and naming conventions, resulting in a consistent, maintainable style across your services.

What coding conventions help reduce over-engineering and improve code readability?▼

Coding conventions that reduce over-engineering and improve readability include applying KISS and YAGNI principles, establishing small functions, using guard clauses, and enforcing strict naming rules to create concise, testable code units.

Can I use these coding standards to establish a common baseline for team code reviews?▼

Yes, you can use these coding standards to establish a common baseline for team code reviews. Applying pragmatic rules during reviews and onboarding aligns individual projects and teams around a consistent, maintainable software design structure.

What is the best way to structure functions for maintainability and testability?▼

The best way to structure functions for maintainability and testability is to design small units using guard clauses and composition. Enforcing the Single Responsibility Principle ensures each function handles one task, producing clear, testable code.

Why should I use guard clauses when designing software for better code structure?▼

You should use guard clauses when designing software because they enforce clear code structure by handling edge cases early. This reduces nested conditions and aligns with pragmatic coding standards to improve overall readability and maintainability.