collision-breakthrough
Deploy when perspectives need to collide for novel solutions. Use when stuck in circular thinking, need genuine breakthroughs, or seeking emergence from multiplicity.
Découvrez les skills documentation architecture patterns, comparez leurs dépôts et consultez leurs instructions.
Deploy when perspectives need to collide for novel solutions. Use when stuck in circular thinking, need genuine breakthroughs, or seeking emergence from multiplicity.
Cross-session continuity through pattern compression. Use when need to bridge sessions, accumulate wisdom, or evolve without calcifying.
Automatically save exploration findings, discoveries, and current state to the exploration journal (docs/exploration/). Use when making important discoveries or completing a phase of work. Ensures future Claude...
Resume exploration from where previous Claude session left off by reading the exploration journal (docs/exploration/). Use at start of session when user says "continue", "resume", or "pick up where we left off"...
Decision matrix for choosing optimal approach to any task. Helps Claude decide when to delegate to sub-agents vs. working directly. Use when starting a new task or unsure of best approach.
Focused on preventing waterfalls and maximizing parallelization in API and Frontend logic.
This skill should be used when users request code review, refactoring, or code quality improvements for Ruby codebases. Apply Sandi Metz's four rules for writing maintainable object-oriented code - classes unde...
Multi-specialist collaborative analysis for complex decisions. Spawns parallel subagents with diverse domain expertise to analyze a topic from multiple angles. Use when user says "multi-mind", or for complex ar...
Simplifies code for clarity and maintainability while preserving exact behavior. Focuses on recently modified code. Use when user says "simplify", "simplify code", "make this simpler", "clean up", or "refactor...
Use to standardize project context (Rules) or automate complex multi-step tasks (Workflows).
Use when designing APIs, Architecture, Security, or Scalability for Node, Python, Go, or Java backend systems.
Use when architecturalizing protocols, developing smart contracts, or auditing security for blockchain systems.
Use for high-stakes technical decisions, system design (Microservices/Monolith), cloud infrastructure, or generating ADRs/RFCs.
Use when designing Universal CI/CD, Multi-Cloud Infrastructure, or Observability systems.
Use when building a deciduous decision graph to capture design evolution, architecture history, or how a codebase's design changed over time. Provides the deciduous CLI commands and graph structure guidelines.
Use when building a deciduous decision graph to capture design evolution, architecture history, or how a codebase's design changed over time. Provides the deciduous CLI commands and graph structure guidelines.
Use when building a deciduous decision graph to capture design evolution, architecture history, or how a codebase's design changed over time. Provides the deciduous CLI commands and graph structure guidelines.
Use when planning system architecture to ensure nothing is missed. Provides structured questions covering scalability, security, data, and operational dimensions before implementation.
Temporal.io workflow orchestration for durable, fault-tolerant distributed applications. Use when implementing long-running workflows, saga patterns, microservice orchestration, or systems requiring exactly-onc...
Production-grade fault tolerance for distributed systems. Use when implementing circuit breakers, retry with exponential backoff, bulkhead isolation patterns, or building resilience into LLM API integrations.
Saga patterns for distributed transactions with orchestration and choreography approaches. Use when implementing multi-service transactions, handling partial failures, or building systems requiring eventual con...
Use this skill when creating or evolving design systems for applications. Provides design token structures, component architecture patterns, documentation templates, and accessibility guidelines. Ensures consis...
LangGraph conditional routing patterns. Use when implementing dynamic routing based on state, creating branching workflows, or building retry loops with conditional edges.
Event sourcing patterns for storing state as a sequence of events. Use when implementing event-driven architectures, CQRS, audit trails, or building systems requiring full history reconstruction.
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é.