unity-component-design
Use when designing new Unity components (MonoBehaviours, ScriptableObjects, systems). Ensures proper architecture before writing code.
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"
Evaluate and improve code modularization using the Balanced Coupling Model. Analyzes coupling strength, connascence types, and distance to identify refactoring opportunities and architectural improvements. Use when reviewing code architecture, refactoring modules, or designing new systems.
分层架构规范 / Architecture and layering rules (v0.3.1)。在设计新组件、修改导入、检查分层时使用。核心约束:cli → flows → data,core 向内不向外。Use when designing components, changing imports, or reviewing layering decisions. Enforces cli/flows/core/data separation.
container-workerがSubtask実装時に参照する詳細ルール(設計書参照、粒度、TDD、品質レビュー、出力形式)を定義
When writing new code, model state as sum types from the start. Apply when creating entities with distinct modes, phases, or lifecycle states.
Station Service SDK를 사용한 테스트 시퀀스 개발 가이드. SequenceBase 패턴, emit 메서드, manifest.yaml 작성법 제공. 사용자가 시퀀스 개발, SequenceBase 구현, 테스트 자동화 코드 작성, manifest.yaml 설정, emit 메서드 사용법을 문의할 때 활성화.
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".
Spot patterns appearing in 3+ domains to find universal principles
Core architecture principles (SSOT, DRY, Anti-Spaghetti) for maintainable code design. Use when planning features, implementing code, or reviewing architecture to prevent duplication and technical debt.
Génère des Commands, Queries et Handlers suivant le pattern CQRS (Command Query Responsibility Segregation). À utiliser lors de la création de use cases, commands, queries, handlers, read models, ou quand l'utilisateur mentionne "CQRS", "command", "query", "handler", "use case", "read model".
识别并消除知识重复,确保系统中每条知识有唯一权威表示。当需要重构代码、整理文档、优化配置、建立单一数据源时使用。覆盖代码重复、数据冗余、文档重复三大维度,提供具体消除策略和权衡建议。
analyzerアプリケーションのアーキテクチャレビュー。Port&Adapterアーキテクチャ(ヘキサゴナルアーキテクチャ)のルールに従っているかをチェックします。新しいPort/Adapter/Usecase/Model追加時、PRレビュー時、またはアーキテクチャ違反の検出が必要な時に使用します。Port層の関数型定義、依存関係の方向、New*関数パターン、レイヤー分離などを検証します。
Error handling patterns including exception hierarchies, error messages, and recovery strategies. Activated when designing exceptions or error handling.
Best practices when developing in Ruby codebases
CUI logging standards with CuiLogger, LogRecord patterns, and DSL-style LogMessages classes
This skill should be used when designing systems, architectures, databases, APIs, or making technical decisions. It provides comprehensive guidance on software architecture, design principles, coding standards, scaling strategies, security, and interview preparation based on 200+ interview experiences and real-world senior engineering knowledge.
SSOT blueprint for creating consistent services: folder structure, required endpoints, dependency conventions, interface contracts, docs/testing/security/observability requirements
Comprehensive guide to caching strategies, cache layers, invalidation patterns, and implementation for improving application performance
Build and deploy enterprise-grade microservices architectures with production-ready patterns, comprehensive observability, advanced security, and operational excellence. Use when: (1) designing multi-service architectures (FastAPI, Go, Node.js), (2) deploying to Kubernetes/Docker/Serverless, (3) implementing observability (logs, metrics, traces), (4) building event-driven systems, (5) securing services with mTLS/RBAC, or (6) operating production microservices. Includes framework-specific implementations, deployment patterns, monitoring setup, service mesh integration, and SRE practices.