system-architect
Expert system architecture design including scalability, reliability, and distributed systems
Expert system architecture design including scalability, reliability, and distributed systems
RabbitMQ pub/sub patterns for asynchronous processing of entity changes and system events.
GDL 90 protocol implementation for ADS-B receivers. Use when decoding traffic data from Stratux, ForeFlight Sentry, or other GDL 90 compatible devices. Includes message decoders, traffic simulators, and receiver client implementations.
Guides implementation of new MCP tools from specification to production-ready code, following the braiins-pool-mcp-server architecture patterns and best practices defined in ARCHITECTURE.md.
Domain-Driven Design and Clean Architecture implementation guide
Comprehensive guide to concurrency models, throughput optimization, worker pools, task queues, and scaling strategies for high-performance applications
Refactor loose state models (optional fields, parallel booleans) into strict sum types. Apply when a field's validity depends on another field's value.
Use ONLY when user mentions converting/using/writing in "logseq format" or similar (must mention "logseq")
Design systems for change. Trade-off analysis, ADR documentation, pattern selection. Architecture decisions must have documented rationale.
Use when restructuring code to improve quality without changing external behavior. Emphasizes safety through tests and incremental changes.
Guide for implementing immutable Value Objects with base classes (StringValue, UuidValue) and Doctrine custom types. Use when creating identity objects or domain-specific values.
Python async/await patterns and asyncio best practices
Reviews modules for depth vs shallowness. Use when designing APIs, reviewing class interfaces, or evaluating abstraction value.
Defining clear boundaries between systems, services, and modules to manage complexity and enable independent evolution.
Code complexity guidelines to keep cyclomatic complexity below 6 using strategy patterns or dispatch tables. Use when writing or refactoring functions with complex branching logic.
Foundational principles for all agents - load always. Defines how we work together.
Ask whether to proceed with refactoring after architecture mapping.
Domain-Driven Design - Modélisation métier et conception de domaines complexes. Utilise ce skill quand: (1) tu dois comprendre un domaine métier complexe, (2) tu veux identifier les bounded contexts d'un système, (3) tu dois créer un ubiquitous language partagé, (4) tu veux modéliser des entités et agrégats, (5) tu dois structurer du code selon Clean Architecture.
Protocols for the agent to autonomously detect failures, analyze root causes, and attempt recovery strategies before requesting user intervention.
Use during implementation when designing modules, functions, and components requiring SOLID principles for maintainable, flexible architecture.
Add retry, timeout, and circuit breaker patterns at the workflow level. Business functions stay clean.
各レビュアーエージェントが参照する詳細なレビュー観点(DB設計、セキュリティ、バックエンド、フロントエンド、インフラ)を定義
Spawn subagents with fresh context and bounded scope.