master-coordinator ๅ review-coordinator ๅ ฑไบซ็้็จๆจกๅผ๏ผๅ ๆฌ Phase ้ช่ฏใ้่ฏฏๅค็ใTodoWrite ็ฎก็ๅ็ถๆ่ฏดๆใๆๆ coordinator agents ๅบๅผ็จๆญค skill ไปฅไฟๆไธ่ดๆงใ
Chaos engineering and fault injection patterns for testing system resilience, failure recovery, and graceful degradation
Use when context is growing large, switching tasks, or needing previous session context - covers thresholds, session tools, and workflow patterns
Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes
ABP Framework domain layer patterns including entities, aggregates, repositories, domain services, and data seeding. Use when: (1) creating entities with proper base classes, (2) implementing custom repositories, (3) writing domain services, (4) seeding data.
Model complex UI flows using finite state machines to ensure deterministic behavior.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
The complete Arcanean Design System - cosmic visual language, academy themes, component patterns, and design tokens for magical interfaces
Kotlin/Spring Boot 3.x patterns - use for backend services, REST APIs, dependency injection, controllers, and service layers
Kotlin coroutines - structured concurrency, Flows, exception handling
Apply when implementing real-time features: live updates, presence, broadcast messages, or database change subscriptions.
Repository ่จญ่จๆๅฐๆ่ฝ๏ผๅๅฉ้็ผ่ ๆ นๆๆฅญๅ้ๆฑ้ธๆๆๅ้ฉ็ Repository ่จญ่จ็ญ็ฅ๏ผ่ณๆ่กจๅฐๅ vs ้ๆฑๅฐๅ vs ๆททๅๆจกๅผ๏ผใ
Ensure code follows DDD architecture and DAL separation principles. Triggers: DDD, arch, ๆถๆง, ๆฐๅ่ฝ, ๆฐๆจก็ต, new feature, scaffold, ้ชจๆถ, domain.
Enforces JU-DO-KON! architectural boundaries, module responsibilities, and design intent. Use when designing, refactoring, or reviewing core game logic.
Implement domain-driven design (DDD) and clean architecture patterns in ASP.NET Core Web APIs. Use this skill when building or refactoring backend services that need strategic domain modeling, tactical DDD patterns (entities, value objects, aggregates, domain events, repositories), and clean architecture layers (domain, application, infrastructure, presentation). Follows principles from Eric Evans' "Domain-Driven Design" and Robert C. Martin's "Clean Architecture".
Establish scalable architecture using modular boundaries, domain-driven design, and consistent data access patterns.
Protocol-based workflow enforcement with validation dependencies and anti-bypass protection
Coding guidance for hexagonal architecture projects following strict layered design patterns (Domain/Application/Infrastructure/Presentation/Bootstrap). Use when implementing features, refactoring code, or fixing bugs in hexagonal architecture codebases. Includes Plan Mode for task decomposition and Execution Mode for layer-specific implementation.
kotlinx.serialization - JSON, Protobuf, custom serializers
Enterprise scaling patterns for microservices, event-driven architecture, and distributed systems
Principles for writing simple, maintainable Laravel/Livewire code. Use when writing Livewire components, tests, or Blade views. Focuses on avoiding over-engineering.
Adapter (Wrapper) Pattern pattern for C development
