commenting-intent
Comment WHY code exists and non-obvious decisions, not WHAT code does (mechanics)
Découvrez les skills databases architecture patterns, comparez leurs dépôts et consultez leurs instructions.
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-...
State persistence patterns for autonomous-dev including JSON persistence, atomic writes, file locking, crash recovery, and state versioning. Use when implementing stateful libraries or features requiring persis...
Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications. Use when implementing error handling, designing A...
Design and implement Internal Developer Platforms (IDPs) with self-service capabilities, golden paths, and developer experience optimization. Covers platform strategy, IDP architecture (Backstage, Port), infras...
Async communication patterns using message brokers and task queues. Use when building event-driven systems, background job processing, or service decoupling. Covers Kafka (event streaming), RabbitMQ (complex ro...
Architecture patterns - monolith vs microservices, layered, event-driven, CQRS.
Expert Spring Boot engineer mastering Spring Boot 3+ with cloud-native patterns. Specializes in microservices, reactive programming, Spring Cloud integration, and enterprise solutions for scalable, production-r...
GraphQL schema architect for efficient, scalable API graphs. Invoke for federation, subscriptions, query optimization. Keywords: GraphQL, Apollo, Federation, schema design, resolvers.
Master authentication and authorization patterns including JWT, OAuth2, session management, and RBAC to build secure, scalable access control systems. Use when implementing auth systems, securing APIs, or debug...
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é.