task-decomposer
複雑な作業を単一目的の小さなタスクに分解する。タスク分解時、作業細分化時、スキル設計時、またはユーザーがタスク分解、作業分割、細分化、単一目的、タスク粒度に言及した際に使用する。
複雑な作業を単一目的の小さなタスクに分解する。タスク分解時、作業細分化時、スキル設計時、またはユーザーがタスク分解、作業分割、細分化、単一目的、タスク粒度に言及した際に使用する。
Migrating Angular 16 to 20 with DDD architecture and SignalStore patterns. Use when converting components, structuring features, or following One-UI migration standards.
Resilience and error recovery patterns including circuit breaker, retry strategies, and graceful degradation
Orchestrate parallel debugging agents with root-cause tracing for multi-failure scenarios
Best practices and rules for architecting scalable, maintainable systems.
Comprehensive guide to gRPC for high-performance microservices communication with Protocol Buffers.
Guide for quality focused software architecture. This skill should be used when users want to write code, design architecture, analyze code, in any case that relates to software development.
Java Developer Agent. Java/Spring Boot 기반 백엔드 개발을 담당합니다. Spring, JPA, Hibernate, Maven, Gradle 전문.
Modern TypeScript patterns, best practices, and advanced type system features for writing type-safe, maintainable code
Conducts comprehensive architecture design reviews including system design validation, architecture pattern assessment, quality attributes evaluation, technology stack review, and scalability analysis. Produces detailed review reports with findings, recommendations, and risk assessments. Use when reviewing software architecture designs, validating architecture decisions, assessing system scalability, evaluating technology choices, or when users mention architecture review, design assessment, technical review, or architecture validation.
Local mirror of Microsoft AL Guidelines (alguidelines.dev) for searching agentic coding rules, vibe-coding standards, AL best practices, and community resources. Use when: (1) Writing or reviewing AL code and need naming conventions, code style, or formatting rules, (2) Implementing event subscribers, error handling, or performance patterns, (3) Setting up AI-assisted development with Claude/Copilot/Cursor agent configurations, (4) Looking for MCP server integrations (AL-ObjID, BC-Code-Intel, NAB), (5) Understanding classic NAV/BC patterns like Document, Journal, Hooks, or Master Data. Content includes: vibe-coding-rules/ (7 AL-specific rule files), BestPractices/ (~27 topics), patterns/ (facade, template-method, event-bridge), NAVPatterns/ (~50+ classic patterns), and CommunityResources/ (agent configs, MCP tools).
PCE (Process-Context Engine) のスコープ管理スキル。入れ子プロセス間のコンテキスト継承を設計し、親子間のハンドオフを最適化する。 トリガー条件: - タスクを子タスクに分解する時 - サブエージェントに作業を委譲する時(Task tool使用時) - 並列タスクを起動する時 - 「このタスクを分割して」 - 「サブタスクのコンテキストを設計して」
比较多个架构方案(单体/微服务等),从SOLID原则、成本、复杂度等维度评分,生成对比表和推荐方案。当需要向客户解释架构选择或ADR决策时使用。
This skill should be used when Ethereum developers are building smart contracts on pod network. It explains pod's coordination-free, blockless execution model, teaches order-independent programming with CRDTs, identifies Ethereum patterns that break on pod, and shows when to use external sequencing for order-dependent applications.
Best practices for writing clear, actionable error messages in code.
REQUIRED before implementing any game feature, scoring logic, state transition, or decision-making. ALL business logic lives in PostgreSQL - frontend is presentation only. Load this to understand where code belongs: database function vs component. Covers RPC patterns, SECURITY DEFINER, and anti-patterns.
Ultimate RabbitMQ expertise skill for production-grade message broker architecture, implementation, and operations. Top 0.01% knowledge covering: (1) Advanced messaging patterns - Dead Letter Exchanges, Delayed Messages, Priority Queues, Consistent Hash Exchange, Sharding, (2) High Availability - Clustering, Quorum Queues, Stream Queues, Federation, Shovel, (3) Performance Engineering - prefetch tuning, connection pooling, batch publishing, memory optimization, flow control, (4) Security - TLS/mTLS, OAuth2, LDAP, certificate rotation, (5) Monitoring - Prometheus metrics, custom health checks, anomaly detection, (6) Troubleshooting - memory alarms, network partitions, queue backlogs, consumer starvation, (7) Multi-tenancy - vhost design, resource limits, isolation patterns, (8) Event-driven architectures - CQRS, Event Sourcing, Saga patterns with RabbitMQ. Use when: building messaging systems, debugging RabbitMQ issues, optimizing performance, designing HA architectures, implementing advanced patterns, product
Initializes a bounded context skeleton under runtime/contexts/<context>.
Martin Fowlerのリファクタリング方法論に基づいた体系的なコード改善スキル。 コードスメルの検出から安全なリファクタリングの実施まで、テストを安全網として 段階的に品質を向上させます。「2つの帽子」を意識し、機能追加と分離して実施。
Distributed systems expert specializing in service decomposition, orchestration, and microservices architecture patterns. Use when designing microservices, defining service boundaries, implementing service mesh, or handling distributed system challenges. Triggers include "microservices", "service mesh", "service decomposition", "distributed systems", "API gateway", "event-driven".
Use for deterministic changes, evidence-first delivery, or assembling proof kits with clear safety justification.
Safely inject new code into legacy codebases with risk containment. Use for feature flags, gradual rollouts, A/B testing new logic, or refactoring critical paths. Implements try-catch fallbacks, feature toggle architecture, and surgical separation of old/new code.