clean-code

Name: clean-code
Availability: InStock
Author: marablemarcel

Enforce pragmatic coding standards for concise, maintainable code.

Updated Jan 6, 2026

Search Tags:#refactoring #code-quality #coding-standards #naming #concise #srp #dry

Ready to run

npx skills add https://github.com/marablemarcel/Living-Lytics --skill clean-code-marablemarcel

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: clean-code
Source: https://github.com/marablemarcel/Living-Lytics/tree/main/living-lytics/.agent/skills/clean-code
Command: npx skills add https://github.com/marablemarcel/Living-Lytics --skill clean-code-marablemarcel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pragmatic coding standards help teams produce concise, direct, and maintainable code, reducing noise and over-engineering.

Core Features & Use Cases

SRP: Single Responsibility - each function/class does ONE thing
DRY: Don't Repeat Yourself - extract duplicates, reuse
KISS: Keep It Simple - simplest solution that works
YAGNI: You Aren't Gonna Need It - avoid unused features
Naming Rules: Variables, Functions, Booleans, Constants
Code Structure: Guard Clauses, Flat > Nested, Composition, Colocation
AI Coding Style: Direct feature, fix bugs, ask questions if unclear
Anti-Patterns (DON'T): Delete obvious comments, avoid deep nesting, inline trivial utilities

Quick Start

Start by applying SRP, DRY, KISS, and YAGNI to your code and perform a quick consistency check against naming, structure, and anti-patterns.

Frequently Asked Questions about clean-code

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

FAQPage Schema

How do I apply SRP and DRY principles to refactor existing code?▼

To refactor code using SRP and DRY, ensure each function or class handles a single responsibility and extract duplicated logic into reusable components. This approach reduces noise, simplifies maintenance, and prevents over-engineering.

What are the best coding standards for writing concise and maintainable code?▼

Pragmatic coding standards for maintainable code emphasize KISS for simplicity and YAGNI to avoid unused features. They also enforce naming consistency, guard clauses, and composition over deep nesting to produce direct, reliable modules.

How do I prevent over-engineering when structuring new software modules?▼

Prevent over-engineering by applying YAGNI to avoid building unused features and KISS to choose the simplest working solution. Structure code using flat logic over nesting and colocation to keep modules concise and maintainable.

What naming rules should I follow to improve code quality during reviews?▼

To improve code quality during reviews, enforce consistent naming rules for variables, functions, booleans, and constants. Clear naming reduces cognitive load, makes code structure more direct, and eliminates the need for obvious comments.

When should I use guard clauses instead of nested conditional structures?▼

Use guard clauses instead of nested structures to keep code flat and simple. Guard clauses prevent deep nesting, which is identified as an anti-pattern, ensuring your logic remains direct, readable, and easier to maintain.