ai-architecture
AI application architecture - gateway, orchestration, model routing, observability, deployment patterns. Use when designing AI systems, scaling applications, or building production infrastructure.
AI application architecture - gateway, orchestration, model routing, observability, deployment patterns. Use when designing AI systems, scaling applications, or building production infrastructure.
Principal Engineer focused on maintainability, SOLID principles, and clean code.
Bootstrap DDD 4-layer domain structure. Use when (1) starting new domain implementation, (2) during v0.1.x PROJECT phase, (3) need to create repositories/api-clients/hooks/components with __tests__ and index.ts exports.
Master ABP Framework patterns including repository pattern, unit of work, domain services, application services, authorization, multi-tenancy, background jobs, and distributed events. Use when: (1) building ABP-based applications with DDD architecture, (2) creating CRUD services with Entity, AppService, DTOs, validators, (3) handling authorization/permissions, (4) generating ABP module code.
2300+ lines of state management mastery - all patterns (Provider, Riverpod, BLoC, GetX), dependency injection, persistence, testing with production-ready code examples.
Current best practices for Model Context Protocol server design, implementation, and integration. Updated patterns for 2026 MCP ecosystem including multi-server orchestration, security, and performance.
Distributed evolutionary memory system using Merkle-DAG branching timelines, holographic erasure coding, and stake-weighted consensus to maintain coherent collective history across thousands of agents despite forking narratives and temporal relativity.
Applies SOLID principles and clean code practices. Required for all code implementations. Covers single responsibility, open-closed, and dependency injection principles.
Use this skill when working on rpg-api codebase - provides layered architecture patterns, outside-in development, and integration with rpg-toolkit
12 Factor App methodology for web applications and microservices.
Build mechanisms to debounce and deduplicate redundant data fetching requests.
Store and recall sequential memory patterns and state transitions.
Master Poka-Yoke error-proofing from Toyota Production System. Design systems that prevent mistakes through structure, not vigilance.
Master Kotlin syntax, OOP principles, SOLID practices, functional programming, and data structures.
WebSocket, real-time communication, and event-driven architectures
Use .NET Aspire MCP server to monitor, debug, and manage distributed application resources including services, databases, containers, logs, traces, and integrations
Domain, Data, and Presentation layer separation with dependency inversion and use case patterns
Implement graceful shutdown with signal handling and broadcast channels. Use when building long-running services or daemons.
Create specialized agents for Claude Code that handle specific tasks autonomously. Generate agent definitions with proper configuration and best practices. Use when: creating agents, generating sub-agents, setting up autonomous workflows. Activates for: "create agent", "generate agent", "new agent", "sub-agent", "make agent"
Ensure features are developed according to specifications by validating implementation against API docs, database schemas, and acceptance criteria. Use before starting implementation, during code review, or when verifying feature completeness.
Create custom slash commands for Claude Code with proper markdown structure and YAML frontmatter. Use when: creating commands, generating slash commands, making workflow automations. Activates for: "create command", "generate command", "new command", "slash command", "make command"
Use when implementing validation or safety checks. Multi-layer validation approach prevents bugs through redundant safeguards. Makes bugs structurally impossible.
Scaffolds complete CQRS command or query with handler, validator, and DTO following Merge project patterns