react-state-management
Standards for managing local, global, and server state.
Standards for managing local, global, and server state.
WebSocket and SSE selection strategies and scaling.
Idiomatic TypeScript patterns for clean, maintainable code.
Controller/Service separation and Custom Decorators.
Functional error handling using Dartz and Either.
Module organization, Dependency Injection patterns, and Project Structure.
Multi-level caching, Invalidation patterns, and Stampede protection.
Secure, reusable data access patterns with DTOs and Taint checks.
gRPC, RabbitMQ standards and Monorepo contracts.
Cross-domain pattern analysis and strategic reflection for weekly review
Scalable project structure using Feature-Sliced Design (FSD).
Idiomatic JavaScript patterns and conventions for maintainable code.
Standards for organizing code by feature at the root level to improve scalability and maintainability.
Example skill demonstrating secure file reference resolution with supporting files
Example skill in category B demonstrating flat organization within nested structure
Example skill at the root of the nested structure demonstrating depth 1
Design robust error handling strategies including try-catch blocks, custom error classes, error boundaries, graceful degradation, and comprehensive logging. Use when implementing exception handling, creating custom error types, setting up error boundaries in React, designing error response formats for APIs, implementing retry logic, handling async errors and promise rejections, logging errors for monitoring, creating user-friendly error messages, or building fault-tolerant systems that fail gracefully.
Architect scalable backend services using layered architecture, dependency injection, middleware patterns, service classes, and separation of concerns. Use when building API services, implementing business logic layers, creating service classes, setting up middleware chains, implementing dependency injection, designing controller-service-repository patterns, handling cross-cutting concerns, creating domain models, implementing CQRS patterns, or establishing backend architecture standards.
Generate structured comparisons and decision matrices across analyzed frameworks. Use when (1) comparing multiple frameworks or approaches side-by-side, (2) making architectural decisions between alternatives, (3) creating best-of-breed selection documentation, (4) synthesizing findings from multiple analysis skills into actionable decisions, or (5) producing recommendation reports for technical stakeholders.
Pattern for aggregating insights across multiple tasks to enable data-driven evolution.
This skill should be used as the entry gate for build/create/implement requests. Triggers on "build X", "create Y", "implement Z", "add feature", "try both approaches", "not sure which approach". Offers brainstorm-together or omakase (chef's choice parallel exploration) options. Detects indecision during brainstorming to offer parallel exploration.
This skill should be used when the user asks to "generate architecture view", "show service dependency graph", "map request flows", "show event topology", "group services by domain", "visualize architecture", or mentions cross-repository architecture analysis, service mapping, or architectural visualization.
Decomposes requirements into executable tasks and coordinates domain orchestrators (frontend, backend, data, test, devops). Use when receiving PRDs, user requirements, or feature requests that span multiple domains. Acts as CEO of the AI development system.