Advanced patterns for Hono-based Electron IPC including CQRS, Zod validation, error handling, and reactive data with RxJS. Use when implementing complex IPC patterns or needing guidance on architecture decisions.
The official MAD-Logic reliability framework for high-stakes multi-step tasks. Uses MAKER principles (Maximal Agentic Decomposition, voting consensus, red-flagging) to achieve zero-error execution. Auto-triggers for complex workflows or critical operations (deployment, security, financial). Compliant with ASP v2.0 Standard.
Resumo da arquitetura e dos princípios globais do xcution.erp.web.
Elicits requirements and defines specifications using EARS (Easy Approach to Requirements Syntax).
マイクロサービス・モノレポ設計 - サービス分割、通信パターン、モノレポ構成
Expert IoT engineer specializing in connected device architectures, edge computing, and IoT platform development. Masters IoT protocols, device management, and data pipelines with focus on building scalable, secure, and reliable IoT solutions.
Expert Spring Boot developer specializing in microservices, security, and enterprise Java development. Masters Spring Security, data access, and building production-ready applications with Spring Boot 3.x.
Provides architecture knowledge for the dealflow-network project including tRPC router patterns, Drizzle ORM conventions, authentication flow, file organization, and collaborative contact system. Use when working on this codebase, adding features, or understanding existing patterns.
DDDアーキテクチャでFastAPIのバックエンドを新規実装または既存コードベースをリファクタリングする際のガイド。レイヤー構成（domain/application/infrastructure/controller）、依存方向、責務境界、pydantic/sqlalchemy(sqlmodel)/alembic/pytestの前提、セッション管理（Dependsで1リクエスト1セッション、必要時UoW）を含む。
Designs comprehensive software solution architectures including system components, technology stacks, integration patterns, scalability strategies, and deployment models. Produces architecture diagrams, technical specifications, and implementation roadmaps. Use when planning new software systems, modernizing legacy applications, designing microservices, evaluating technology choices, creating architecture documentation, or when users mention system design, architecture patterns, scalability planning, or technical architecture decisions.
Adapter Layer 전문가. CommandAdapter(persist만, JpaRepository 1:1), QueryAdapter(4개 메서드, QueryDslRepository 1:1), AdminQueryAdapter(Join 허용, DTO Projection), LockQueryAdapter(6개 Lock 메서드). 필드 2개만(Repository + Mapper). @Component 필수. @Transactional 절대 금지.
ARCHITECT PHASE: Architectural design patterns, component templates, and system design guidance. Provides proven architectural patterns including microservices, layered architecture, event-driven systems, C4 diagram templates, API contract formats, and design anti-patterns. Use when: designing system architecture, creating component diagrams, defining interfaces, planning component boundaries, choosing architectural patterns, organizing system modules, or when user mentions: architecture, components, system design, diagrams, C4, microservices, API contracts, service boundaries, architectural patterns. Use for: component design, interface definition, system boundaries, dependency management, architecture documentation, design patterns, integration patterns. DO NOT use for: code implementation details, specific framework syntax, database schema design, frontend-specific patterns, testing strategies, or security implementation (use dedicated skills).
Go library development patterns. Use when designing library APIs, implementing extensibility, or working on packages in pkg/ directories. Triggers: format extensibility, provider separation, capability composition, library scope, supplemental packages, public API design.
FAIL LOUDLY pattern for selection constraints. Trigger when: (1) correlated stocks selected together, (2) min_crypto_positions ignored, (3) constraints violated silently.
Supabase RLS パフォーマンス最適化。セキュリティ境界と最適化フィルタの区別、および堅牢な関数定義を規定。
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Bounded Context에 새로운 infrastructure 를 추가하거나 수정할 때 사용하세요.
Apply structured thinking before coding. Use when: starting new features, making architectural decisions, refactoring large components, or evaluating implementation approaches. Includes Musk's 5-step algorithm and ICE scoring framework.
Use when designing new Unity components (MonoBehaviours, ScriptableObjects, systems). Ensures proper architecture before writing code.
Expert microservices architecture including service decomposition, communication patterns, and resilience
Pattern for separating repository code from user data and notebooks. Trigger: organizing scientific pipelines, separating code from data
クリーンアーキテクチャ・DDD設計 - レイヤー設計、ドメインモデリング、依存関係管理
错误处理技能：提供系统化的错误处理工作流、分类体系和最佳实践。 Use when: 需要处理异常、实现重试逻辑、设计降级策略、编写错误消息。 Triggers: "错误", "异常", "重试", "降级", "fallback", "error", "exception", "retry"
