Use this skill for PR preparation. Use when preparing PRs for submission, running quality gates, drafting PR descriptions and templates. Do not use when reviewing existing PRs - use pr-review instead. DO NOT use when: just generating commit messages - use commit-messages.

Use this skill to quickly understand "what changed and what matters". Use when resuming work after absence, preparing handoff documentation, reviewing sprint progress, analyzing git history for context. Do not use when doing detailed diff analysis - use diff-analysis instead. DO NOT use when: full code review needed - use review-core instead.

Quota tracking, threshold monitoring, and graceful degradation for rate-limited API services. quota, rate limiting, usage limits, thresholds.

Analyze individual skill complexity and get modularization recommendations. For ecosystem-wide evaluation, use /skills-eval instead.

Retrospective workflow evaluation and improvement of skills, agents, commands, and hooks. workflow improvement, retrospective, workflow efficiency Use when: workflow felt slow, confusing, or needs optimization DO NOT use when: simple one-off fixes - use fix-pr or do-issue instead.

Asynchronous event-based communication to decouple producers/consumers for scalability and resilience. Triggers: event-driven, message queue, pub/sub, asynchronous, decoupling Use when: real-time workloads or multiple subsystems react to same events DO NOT use when: selecting paradigms (use architecture-paradigms first), simple request-response.

Coarse-grained service architecture for deployment independence without microservices complexity. service-based, SOA, coarse-grained services, domain services Use when: teams need deployment independence without microservices complexity DO NOT use when: fine-grained scaling needed - use microservices.

Consult this skill when designing client-server systems or API architectures. Use when traditional web/mobile applications with centralized services, clear separation between client and server responsibilities needed. Do not use when selecting from multiple paradigms - use architecture-paradigms first. DO NOT use when: peer-to-peer dominates - consider dedicated P2P patterns.

Data-grid architecture for high-traffic stateful workloads with linear scalability. space-based, data grid, in-memory, linear scaling, high traffic Use when: traffic overwhelms database nodes or linear scalability needed DO NOT use when: data does not fit in memory or simpler caching suffices.

Functional Core, Imperative Shell: isolate deterministic logic from side effects for testability. Triggers: functional-core, imperative-shell, pure functions, side-effects, testability Use when: business logic is entangled with I/O or tests are brittle DO NOT use when: simple scripting without complex logic, or performance-critical hot paths where immutability overhead matters.

Serverless FaaS for event-driven workloads with minimal infrastructure management. serverless, FaaS, Lambda, event-driven, pay-per-use Use when: workloads are event-driven with bursty traffic DO NOT use when: long-running processes or stateful operations required.

Decouple domain logic from infrastructure using Hexagonal (Ports & Adapters) pattern. Triggers: hexagonal, ports-adapters, infrastructure-independence, domain-isolation, testability Use when: business logic separation, infrastructure changes needed, testability critical DO NOT use when: selecting paradigms (use architecture-paradigms first), simple CRUD.

Minimal core system with plugin-based feature extensibility for platform development. Triggers: microkernel, plugin-architecture, extensibility, platform-design Use when: platforms/IDEs/marketplaces, core stability critical, plugin isolation needed DO NOT use when: selecting paradigms (use architecture-paradigms first), no extensibility needed.

Consult this skill when designing data pipelines or transformation workflows. Use when data flows through fixed sequence of transformations, stages can be independently developed and tested, parallel processing of stages is beneficial. Do not use when selecting from multiple paradigms - use architecture-paradigms first. DO NOT use when: data flow is not sequential or predictable. DO NOT use when: complex branching/merging logic dominates.

Single deployable with enforced module boundaries for team autonomy without distributed complexity. Triggers: modular-monolith, module boundaries, single deployment, team autonomy Use when: teams need autonomy without distributed overhead DO NOT use when: already using microservices or system is small.

Consult this skill when cultivating and maintaining digital gardens. Use when managing note collections, creating link structures, maintaining knowledge bases, tending garden health and growth. Do not use when creating memory palace structures - use memory-palace-architect. DO NOT use when: evaluating new knowledge - use knowledge-intake.

Consult this skill when designing permanent memory palace structures. Use when creating new memory palace structures, organizing complex domains, designing spatial layouts for knowledge retention. Do not use when quick knowledge search - use knowledge-locator instead. DO NOT use when: session-specific context - use session-palace-builder.

Consult this skill when implementing layered patterns or enforcing layer boundaries. Use when building traditional applications with clear boundaries, working with moderate-sized teams, needing familiar and well-understood patterns, compliance requirements demand clear separation. Do not use when selecting from multiple paradigms - use architecture-paradigms first. DO NOT use when: high scalability needs independent component scaling. DO NOT use when: teams need independent deployment cycles - use microservices.

Cross-plugin testing quality metrics and standards. Referenced by pensive:test-review and parseltongue:python-testing. testing standards, quality metrics, coverage thresholds, anti-patterns Use when: test quality evaluation, coverage thresholds, quality standards DO NOT use when: simple scripts without quality requirements.

Consult this skill for session-scoped temporary knowledge structures. Use when working on complex multi-step projects, preserving context across interruptions, tracking session-specific state. Do not use when permanent knowledge structures needed - use memory-palace-architect. DO NOT use when: searching existing knowledge - use knowledge-locator.