clean▌

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.

42 Clean Architecture rules organized by priority for designing maintainable, testable software systems. \n \n Covers 8 rule categories from dependency direction and entity design (critical) through testing architecture (low-medium), each with specific guidance and code examples \n Dependency rules enforce inward-pointing dependencies, interface ownership, and acyclic component graphs to prevent architectural decay \n Entity and use case rules isolate business logic from frameworks, persistence,

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.