Découvrez les skills devops architecture patterns, comparez leurs dépôts et consultez leurs instructions.
Use when clarifying fuzzy boundaries, defining quality criteria, teaching by counterexample, preventing common mistakes, setting design guardrails, disambiguating similar concepts, refining requirements through...
Use when designing or reviewing systems handling sensitive data (PII, PHI, financial, auth credentials), building features with security implications (auth, payments, file uploads, APIs), preparing for security...
Use when explaining concepts at different expertise levels, moving between abstract principles and concrete implementation, identifying edge cases by testing ideas against scenarios, designing layered documenta...
Use when problems involve interconnected components with feedback loops (reinforcing or balancing), delays, or emergent behavior where simple cause-effect thinking fails. Invoke when identifying leverage points...
This skill should be used whenever domain modeling is taking place. It provides specialized guidance for type-driven and data-driven design based on Rich Hickey and Scott Wlaschin's principles. The skill helps...
Documentation templates for ADRs, runbooks, and architecture docs. Use when creating architectural decision records, operational runbooks, or technical documentation.
Documentation templates for ADRs, runbooks, and architecture docs. Use when creating architectural decision records, operational runbooks, or technical documentation.
Expert at organizing and optimizing monorepos. Covers Turborepo, Nx, pnpm workspaces, task orchestration, caching, and dependency management. Knows how to scale codebases without scaling build times. Use when "...
Use when designing multi-tenant SaaS architectures, implementing tenant isolation, data partitioning strategies, or building billing/metering systems - covers pooled, siloed, and hybrid modelsUse when ", " ment...
Patterns for designing, building, and operating microservices architectures. Covers service decomposition, inter-service communication, resilience patterns, data consistency, and observability in distributed sy...
World-class backend engineering - distributed systems, database architecture, API design, and the battle scars from scaling systems that handle millions of requestsUse when "backend, api, database, postgres, my...
Patterns for building reliable background job processing systems. Covers message queues, worker pools, retries, dead letter handling, and async workflow orchestration. Use when ", " mentioned.
World-class design systems architecture - tokens, components, documentation, and governance. Design systems create the shared language between design and engineering that makes products feel cohesive at any sca...
Creates or refactors Business Logic into Service classes using MCP-Aware standards.
Guidelines for analyzing and optimizing application performance (N+1, caching, Computed properties).
Standardizes Model Observers for handling side-effects of model events.
Guidelines for creating Filament 4 Resources with strict Separation of Concerns (SoC) and UI standards.
Standardizes Events and Listeners for decoupled architecture.
Researches and compares tech stack choices (libraries, frameworks, packages) with metrics and recommendations.
Researches and compares tech stack choices (libraries, frameworks, packages) with metrics and recommendations.
Refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Use before writing code or implementation plans.
Use when setting up background jobs, caching, or WebSockets - SolidQueue, SolidCache, SolidCable (TEAM RULE
Use when designing Rails models - ActiveRecord patterns, validations, callbacks, scopes, associations, concerns, query objects, form objects
Use when deleting records from a Bknd entity via the SDK or REST API. Covers deleteOne, deleteMany, soft delete patterns, cascade considerations, response handling, and common patterns.
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.