systematic-debugging
Four-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions.
Découvrez les skills devops architecture patterns, comparez leurs dépôts et consultez leurs instructions.
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
Comment WHY code exists and non-obvious decisions, not WHAT code does (mechanics)
Managing complexity is software's primary technical imperative - all other goals are secondary
Design in pseudocode first, iterate approaches, then translate to code
Software surgery: contract → invariants → creative search → inevitable incision; minimal diff, compositional core, proof signal.
Review+fix protocol with safety guardrails (unsoundness, invariants, footguns, incidental complexity); requires a validation signal.
Algebra-Driven Design (ADD): model domains via minimal algebra + laws; encode in types; test laws.
Law-driven abstraction protocol: evidence first, seam test, minimal algebra, executable law check.
Lateral-thinking playbook for options and trade-offs; always deliver a five-tier strategy portfolio.
Mine Codex sessions to synthesize your top software design heuristics (no quotes, no evidence).
Use when querying, fetching, or subscribing to game entities in dojo.js. Triggers: entity query, fetch entities, useModel, useEntityQuery, ToriiQueryBuilder, subscribe entities, getEntities, entity subscription...
Distributed systems architect specializing in microservices design patterns. Invoke for service boundaries, domain-driven design, saga patterns, event sourcing, service mesh, distributed tracing. Keywords: micr...
Premium/yaratıcı UI tasarım. ⚠️ Distinctive, memorable interface için kullan. Temel UI için → design-patterns.
Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing microservices.
Repository pattern, transactions, caching ve query optimization.
Instruction set for enabling and operating the Spring Cache abstraction in Spring Boot when implementing application-level caching for performance-sensitive workloads.
Structure systems around asynchronous, event-based communication to decouple producers and consumers for improved scalability and resilience. Use when building loosely coupled systems with asynchronous message-...
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é.