simplifier
Simplify code and workflows without behavior changes; reduce complexity and duplication; improve readability. Use when asked to refactor, reduce complexity, or simplify logic.
Simplify code and workflows without behavior changes; reduce complexity and duplication; improve readability. Use when asked to refactor, reduce complexity, or simplify logic.
SPEC document authoring guide - YAML metadata, EARS syntax (5 patterns with Unwanted Behaviors), validation checklist
Integrate the Blueprint multi-tenancy pattern into new features and modules. Use this skill when adding Blueprint-aware functionality, implementing BlueprintMember access control, handling Blueprint ownership (User vs Organization), enforcing resource isolation, and integrating with BlueprintEventBus. Ensures proper multi-tenant architecture where Blueprint defines permission boundaries and all resources respect Blueprint context.
Use when changes affect component organization, technology stack, or cross-container communication - triggered by new components, pattern changes, or needing to map external interfaces to internal components
プロジェクト全域の命名規則。ディレクトリ、ファイル、コード内の全ルールを網羅した唯一の正解(SSoT)。
Base instruction protocol for Senior Engineering and Agentic Systems.
Transaction 경계 전문가. TransactionManager(단일 Port persist), ReadManager(단일 Query Port findBy/get), CommandFacade(2+ Manager persist* 조합), QueryFacade(2+ ReadManager fetch* 조합). @Transactional 메서드 단위 필수. @Component 사용. @Service 금지.
Usa este skill cuando el usuario pida crear o modificar un servicio de negocio en la capa svc/. Define la arquitectura y convenciones de servicios backend.
This skill should be used when the user asks about "design patterns", "SOLID principles", "factory pattern", "strategy pattern", "observer pattern", "composition vs inheritance", "Pythonic design", "singleton alternatives", "anti-patterns", "dependency injection", or needs guidance on applying Gang of Four patterns idiomatically in Python.
Essential LINQ query syntax patterns and separation of concerns for data access. For detailed examples and advanced patterns, see references section.
Phase 3 of OSS contribution - Design and implement the solution following project standards and best practices. Writes code following conventions, adds/updates tests, handles edge cases. Use when issue analysis is complete and ready to write code.
Refactors complex code to be clearer and easier for developers to understand, following simplicity-first principles
RESTful API design patterns, error handling, and documentation
Regras de dependência entre core, shared e features.
Core engineering principles for quality, maintainable code.
Common architectural patterns and design best practices. Use when designing system architecture, choosing design patterns, or creating technical designs.
Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications. Use when implementing error handling, designing APIs, or improving application reliability.
WHEN: Spring Boot + Kotlin, Ktor backend review, coroutine-based server, WebFlux/R2DBC pattern checks WHAT: Spring Kotlin idioms + Coroutines integration + WebFlux patterns + Data class usage + Test strategies WHEN NOT: Android → kotlin-android-reviewer, KMP shared code → kotlin-multiplatform-reviewer
Create a minimal, step-based plan for implementing a feature across Clean Architecture layers without over-generation.
Use when working with Rails projects, ActiveRecord models, controllers, routes, or Rails-specific patterns. Covers naming conventions, models, migrations, service objects, and testing with RSpec.