software-architecture

Quality-focused software architecture guidance based on Clean Architecture and Domain-Driven Design principles. This skill provides guidance for quality focused software development and architecture. It is based on Clean Architecture and Domain Driven Design principles. This skill is applicable to execute the workflow or actions described in the overview. - Emphasizes library-first approach: search for existing npm packages, SaaS solutions, and third-party APIs before writing custom code; reserve custom code for domain-specific logic, performance-critical paths, and security-sensitive implementations - Enforces code style rules including early returns over nested conditions, arrow functions, component decomposition at 80+ lines, and file splitting at 200+ lines - Promotes domain-driven design with clear separation of concerns: keep business logic independent of frameworks, avoid mixing UI with business logic, and use domain-specific naming instead of generic terms like utils or helpers - Identifies anti-patterns to avoid: NIH syndrome, poor architectural choices, generic naming conventions, and treating custom code as a liability requiring maintenance and testing - Early return pattern : Always use early returns when possible, over nested conditions for better readability - Avoid code duplication through creation of reusable functions and modules - Decompose long (more than 80...