frontend-architecture
Component architecture, design patterns, state management strategies, module systems, build tools, and scalable application structure
Discover databases architecture patterns skills, compare source repositories and read the instructions for each workflow.
Component architecture, design patterns, state management strategies, module systems, build tools, and scalable application structure
Comprehensive Spring Boot development skill covering auto-configuration, dependency injection, REST APIs, Spring Data, security, and enterprise Java applications
Common interface patterns, navigation patterns, form patterns, data display patterns, feedback patterns, and accessibility considerations
Complete guide for enterprise architecture patterns including domain-driven design, event sourcing, CQRS, saga patterns, API gateway, service mesh, and scalability
Comprehensive guide for Redis state management including caching strategies, session management, pub/sub patterns, distributed locks, and data structures
Refactor code to be simpler while maintaining identical functionality
Generate comprehensive implementation plans for features. Use when user requests "help me implement X", "create a plan for X", "break down feature X", "how should I build X", or asks for detailed implementation...
Colyseus multiplayer patterns for Starwards - @gameField decorators, state sync, JSON Pointer commands, room architecture, and avoiding common Colyseus pitfalls; state is source of truth, server authoritative
Personal AI Infrastructure (PAI) - PAI System Template MUST BE USED proactively for all user requests. USE PROACTIVELY to ensure complete context availability. === CORE IDENTITY (Always Active) === Your Name:...
Expert guidance on Swift Concurrency best practices, patterns, and implementation. Use when developers mention: (1) Swift Concurrency, async/await, actors, or tasks, (2) "use Swift Concurrency" or "modern concu...
Architectural design patterns, C4 diagram templates, component design guidelines, and anti-patterns for PACT Architect phase. Use when: designing system components, creating architecture diagrams, defining comp...
Analyze OpenShift must-gather diagnostic data including cluster operators, pods, nodes, and network components. Use this skill when the user asks about cluster health, operator status, pod issues, node conditio...
Impact-analysis-first modification workflow with backward compatibility assessment and breaking change detection. Auto-executes when user clearly wants to modify, change, update, adjust, enhance, extend, or alt...
Systematic compatibility analysis, migration guidance, and breaking change detection for dependency/framework upgrades. Auto-executes when user clearly wants to upgrade, update, migrate, or modernize software d...
Expert guidance for Dagster data orchestration including assets, resources, schedules, sensors, partitions, testing, and ETL patterns. Use when building or extending Dagster projects, writing assets, configurin...
Guide architectural decisions and PLAN.md updates using Flow framework. Use when user discusses "architecture", "how should we architect", "design patterns", "how should we structure", "how do we structure", "t...
Four-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions.
Each routine does one thing and does it well - extract when routines have multiple responsibilities
Class interfaces present one cohesive abstraction - don't mix domain logic with serialization, persistence, or unrelated concerns
Try 2-3 different approaches before implementing - don't settle for first design you think of
Hide implementation details behind interfaces - work at domain level (what), not implementation level (how)
Create detailed implementation plans with bite-sized tasks for engineers with zero codebase context
RED-GREEN-REFACTOR for process documentation - baseline without skill, write addressing failures, iterate closing loopholes
Use each variable for exactly one purpose - no hybrid coupling or hidden meanings
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.