Software architecture patterns and design principles. Use when designing systems, making architectural decisions, reviewing code structure, or creating design documents. Provides SOLID, DDD, Clean Architecture, and API design guidance.
Layer work avoidance checks from existence to content to semantic comparison. Each technique catches different skip scenarios for maximum automation efficiency.
Core development philosophy including development cycles, naming conventions, architectural decisions, and multi-agent workflows. Use when establishing project foundations or making architectural decisions.
Design and review backend APIs using Routes→Handlers→Services→Repositories with clear Domain Model vs DTO boundaries. Use PROACTIVELY when creating/refactoring endpoints, moving logic out of handlers, defining service use-cases, or implementing repositories. Triggers: DDD, domain-driven design, layered architecture, clean architecture, hexagonal, ports and adapters, repository pattern, service layer, handler, endpoint, API design, refactor backend, business logic, use-case, aggregate, entity, value object, DTO
Chaos experiment design methodology. Hypothesis formation, success criteria definition, blast radius control, validation patterns, and SLI monitoring for effective chaos engineering.
Implement robust error handling with user-friendly messages, fail-fast validation, specific exception types, and proper resource cleanup across the application. Use this skill when writing try-catch blocks, throwing or catching exceptions, implementing error boundaries, handling API errors, or managing error states in any part of the codebase. Apply this skill when validating inputs early (fail fast), providing clear actionable error messages to users without exposing security details, using specific exception types rather than generic errors, implementing centralized error handling at appropriate boundaries, designing for graceful degradation, implementing retry logic with exponential backoff, or ensuring resources are cleaned up in finally blocks. This skill ensures errors are caught and handled appropriately, user experience remains positive even when errors occur, security is maintained by not leaking sensitive information, and systems continue operating or degrade gracefully when non-critical services fa
Implements error boundaries, crash reporting, graceful failure handling, and system observability for high-availability applications
Systematic process for reproducing, identifying root causes, and implementing minimal, intelligent bug fixes.
Martin Fowler's refactoring catalog with incremental change patterns and test-driven refactoring discipline
