clean▌

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

Clean Architecture patterns for Android and KMP projects. Covers module boundaries, dependency inversion, UseCase/Repository patterns, and data layer design with Room, SQLDelight, and Ktor.

Guidelines by Alberto Basalo for developing clean NestJS APIs using TypeScript. These rules emphasize strong typing, clean code principles, and architectural best practices.

This skill is the authoritative clean code standard for this repository's shared skills. It defines stable rule IDs (CC-*), how to apply them in reviews, and how to extend them safely via language overlays and explicit exceptions.

A disciplined approach to writing code that communicates intent, minimizes surprises, and welcomes change. Apply these principles when writing new code, reviewing pull requests, refactoring legacy systems, or advising on code quality improvements.

Code review and refactoring guidance based on Robert C. Martin's Clean Code principles. \n \n Covers nine core areas: meaningful naming conventions, function design (size, single responsibility, argument limits), comment best practices, formatting standards, object and data structure patterns, error handling strategies, unit testing discipline, class design, and code smell identification \n Provides actionable guidance for writing new code, reviewing pull requests, refactoring legacy code, and e

$22

CRITICAL SKILL - Be concise, direct, and solution-focused.