element-relationship-analyzer
プラグイン要素間の依存関係や呼び出し順序を分析する。プラグイン整合性確認時、依存関係検証時、またはユーザーが要素間依存、呼び出し順序、循環依存、アーキテクチャ検証に言及した際に使用する。
プラグイン要素間の依存関係や呼び出し順序を分析する。プラグイン整合性確認時、依存関係検証時、またはユーザーが要素間依存、呼び出し順序、循環依存、アーキテクチャ検証に言及した際に使用する。
Swift Concurrency支援。async/await、Actor、Sendable、データ競合防止。 使用タイミング: (1) 並行処理コードの実装時、(2) Swift 6 Strict Concurrency対応時、 (3) データ競合の診断・修正時、(4) MainActorとバックグラウンド処理の設計時
Implement features following Domain-Driven Design (DDD) and CQRS patterns with event-driven architecture, Kafka, and BullMQ
Guides the selection and documentation of architectural decisions using ADR patterns.
Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing microservices.
Complete guide for creating, publishing, and consuming events in the DeLoNET home network's 33GOD agentic developer pipeline. Built on RabbitMQ with strict type safety via Pydantic, async Python (aio-pika), FastAPI, and Redis-backed correlation tracking. This skill is REQUIRED for any work involving the home network event bus.
Resilient command execution with automatic fallbacks and error recovery
TRUST 4 principles - Test First, Readable, Unified, Secured
Legacy .NET Framework expert specializing in .NET Framework 4.8, WCF services, ASP.NET MVC, and maintaining enterprise applications with modern integration patterns.
Obsidian LiveSync プロジェクトのコードレビューを実施します。DDD アーキテクチャの遵守、レイヤー間の依存方向、セキュリティ(認証情報、入力検証)、パフォーマンス(非同期処理、タイムアウト)、Rust 固有のベストプラクティス(所有権、エラーハンドリング)をチェックします。PR レビュー、コード品質確認、実装の妥当性検証を依頼されたときに使用してください。
Assist with DDD architecture design and compliance checking. Triggers: DDD, 架構, architecture, 領域設計, domain design.
Comprehensive guide for developing Temporal.io workflows and activities in the A4C-AppSuite. Covers Workflow-First architecture, deterministic workflow design, event-driven activities, saga compensation patterns, CQRS integration, and testing strategies for durable workflow orchestration in healthcare compliance contexts (HIPAA audit trails).
Analyze, review, and provide recommendations for distributed system designs. Use when: (1) Reviewing existing system architectures for gaps or improvements, (2) Analyzing system designs for scalability, reliability, or performance issues, (3) Providing recommendations on load balancing, caching, databases, sharding, replication, messaging, rate limiting, authentication, resilience, or monitoring, (4) Assessing trade-offs in system design decisions, (5) Creating system design review documents with gaps and recommendations. Triggers: "review my system design", "analyze this architecture", "what are the gaps", "system design recommendations", "scalability review", "reliability analysis".
Create domain entities following DDD principles. Use when the user wants to create a new entity, add a domain model, implement domain logic, or mentions "entity", "domain", "model", "aggregate".
Designs comprehensive backend systems including RESTful APIs, microservices, database architecture, authentication/authorization, caching strategies, message queues, and scalability patterns. Produces API specifications, database schemas, architecture diagrams, and implementation guides. Use when designing backend services, APIs, data models, distributed systems, authentication flows, or when users mention backend architecture, API design, database design, microservices, or server-side development.
Modern CSS styling methodology prioritizing CSS Grid over Flexbox. Covers Grid layout patterns, Subgrid, Container Queries, Design Tokens, and maintainable CSS architecture. Reference for implementing scalable, responsive layouts with predictable behavior.
Design Swift app architecture with MVVM, Clean Architecture, dependency injection, and repository patterns. Use when structuring iOS/macOS projects, creating ViewModels, implementing DI, or organizing code layers.
Human Made engineering principles and code quality standards. Apply when writing code, reviewing code, planning implementations, or discussing architecture. Covers code quality priorities, simplicity over complexity, and avoiding over-engineering.
REST and GraphQL API design patterns. Use when designing APIs, reviewing API changes, or implementing endpoints.
Encapsulates CollectionView in Service Layer to maintain MVVM principles in WPF. Use when implementing filtering, sorting, or grouping while keeping ViewModels free of WPF dependencies.
DDD Aggregate Root 설계, Law of Demeter 적용, Tell Don't Ask 패턴 강제. /kb-domain 명령 시 자동 활성화.
スキルの適切な粒度を定義(1スキル1目的、分割基準、結合基準)する。スキル設計時、粒度判断時、またはユーザーがスキル粒度、1スキル1目的、分割基準、結合基準、スキル設計原則に言及した際に使用する。