clean▌

Comprehensive software craftsmanship guide based on Robert C. Martin's "Clean Code: A Handbook of Agile Software Craftsmanship", updated with modern corrections where the original 2008 advice has been superseded. Contains 48 rules across 10 categories, prioritized by impact to guide code reviews, refactoring decisions, and new development. Examples are primarily in Java but principles are language-agnostic.

Language-agnostic reference for SOLID principles, design patterns, DRY, KISS, and clean code fundamentals. \n \n Covers seven rule categories prioritized by impact: SOLID principles, core principles (DRY, KISS, YAGNI), design patterns, code organization, naming, functions, and documentation \n Includes 23 rules across SOLID (5), core principles (8), and design patterns (8), with 4 additional categories planned \n Provides quick reference tables, TypeScript code examples, and an audit output form

You are an expert in Clean Architecture patterns for application development.

Clean messy data in the active sheet or a specified range.

Clean code reads like well-written prose. Every name reveals intent. Every function tells a story. Every class has a single purpose. The goal isn't just working code—it's code that others can understand quickly, modify safely, and extend confidently.

A disciplined approach to structuring software so that business rules remain independent of frameworks, databases, and delivery mechanisms. Apply these principles when designing system architecture, reviewing module boundaries, or advising on dependency management.

You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its quality, maintainability, and performance.

This skill provides comprehensive guidance for implementing Clean Architecture, Hexagonal Architecture (Ports & Adapters), and Domain-Driven Design tactical patterns in Java 21+ Spring Boot 3.5+ applications. It ensures clear separation of concerns, framework-independent domain logic, and highly testable codebases through proper layering and dependency management.

Code refactoring expert applying clean code principles, SOLID patterns, and best practices to improve maintainability. \n \n Analyzes code smells, dependencies, and risky hotspots to identify refactoring priorities \n Proposes incremental refactor plans with small, reviewable slices that preserve existing behavior \n Covers duplication reduction, complexity simplification, testability improvements, and design consistency \n Includes test updates and regression verification to ensure safe, non-br

Pragmatic coding standards emphasizing conciseness, single responsibility, and direct solutions. \n \n Covers five core principles: Single Responsibility, DRY, KISS, YAGNI, and the Boy Scout rule for incremental code improvement \n Provides naming conventions for variables, functions, booleans, and constants designed to self-document intent without excessive comments \n Enforces function discipline: max 20 lines, one level of abstraction, minimal arguments, and no unexpected side effects \n Incl