GitHub
defense-in-depth
Use when invalid data causes failures deep in execution, requiring validation at multiple system layers - validates at every layer data passes through to make bugs structurally impossible
Skills IA devops architecture patterns
Découvrez les skills devops architecture patterns, comparez leurs dépôts et consultez leurs instructions.
Catégories: devops architecture patterns
devops architecture patterns Effacer les filtres
Explorer
GitHub
api-design
Use this skill when designing or reviewing APIs - REST, GraphQL, gRPC, or any programmatic interface. Applies API design thinking focused on contracts, ergonomics, and evolution to specifications, designs, and...
GitHub
parallel-agents
Multi-agent orchestration patterns. Use when multiple independent tasks can run with different domain expertise or when comprehensive analysis requires multiple perspectives.
GitHub
architecture-design
Design scalable, maintainable system and integration architectures for pilot projects. Use when defining components, data pipelines, tool integrations, and guardrails to ensure robustness, performance, and exte...
GitHub
microservices
Microservices architecture pattern for distributed, independently deployable services
GitHub
error-handling
Guide for building resilient applications with robust error handling strategies. Use when designing APIs, debugging issues, or implementing resilience patterns like retries and circuit breakers.
GitHub
cross-domain-collider
Iteration 8 of Multiplicity Cascade - Collides unrelated domains for emergence
GitHub
production-pipelines
strategies for building automated CI/CD pipelines for agents. Use this to implement "shift left" testing, staged validation, and evaluation-gated deployments.
GitHub
tdd-workflow
Test-Driven Development workflow principles. RED-GREEN-REFACTOR cycle.
GitHub
meta-pattern-spawner
Iteration 5 of Multiplicity Cascade - Spawns meta-patterns from patterns
GitHub
data-engineering
Use this skill when designing or reviewing data pipelines, ETL processes, data warehouses, streaming systems, or any system where data movement, transformation, and quality are primary concerns. Applies data en...
GitHub
multi-tenant
Multi-tenant architecture patterns. Preload for agents working with org/team/user scoping.
GitHub
service-pattern-standardization
Standardizes service patterns: constructor injection, error handling, logging with developer.log(), service-to-service communication. Use when creating new services or refactoring existing services.
GitHub
data-mapping
Data mapping patterns for transforming API responses to internal types
GitHub
dispatching-parallel-agents
当面对 2+ 个独立任务，可以在没有共享状态或顺序依赖的情况下工作时使用
GitHub
legacy-modernization
Expert modernisation de systèmes legacy - Strangler Fig, refactoring progressif, migration. Utilise ce skill quand: (1) moderniser une application legacy, (2) migration progressive, (3) refactoring à grande éch...
GitHub
producer-implementation
Producer implementation patterns for API operations and business logic
GitHub
occams-razor
Complexity Pruning and Simplification using the Subtraction Method. Use when refactoring, reducing boilerplate, or challenging over-engineered solutions.
GitHub
ui-design-system
Advanced UI design patterns, animations, and premium component library for next-level mobile experiences
GitHub
feature-dev
Feature development workflow from spec to delivery
GitHub
orchestration
This skill should be used when orchestrating complex tasks, decomposing work into atomic units, dispatching to subagents, verifying outputs, or when discussing task verification and deviation tracking patterns.
GitHub
resume-work
Resume work from previous session with full context restoration
GitHub
mcp-routing-troubleshooting
Resolve MCP tool routing conflicts and naming collisions. Use when the user mentions MCP conflicts, routing issues, or tool collisions.
GitHub
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality.
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é.