CQRS and Event Sourcing for auditability, read/write separation, and temporal queries. Triggers: CQRS, event-sourcing, audit-trail, temporal queries, distributed-systems Use when: read/write scaling differs or audit trail required DO NOT use when: selecting paradigms (use architecture-paradigms first), simple CRUD without audit needs.
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 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.
Interactive selector and router for architecture paradigms. Use when selecting architecture patterns for new systems, comparing paradigm trade-offs, creating architecture decision records, evaluating architecture fit for team size and domain complexity, planning implementation roadmaps. Do not use when implementing a specific known paradigm - use the specific architecture-paradigm-* skill (hexagonal, layered, microservices, etc.) instead. reviewing existing architecture - use architecture-review instead. Use this skill BEFORE making architecture decisions. Check even if unsure about needs.
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.
Consult this skill for Python performance profiling and optimization. Use when debugging slow code, identifying bottlenecks, optimizing memory, benchmarking performance, production profiling. Do not use when async concurrency - use python-async instead. DO NOT use when: CPU/GPU system monitoring - use conservation:cpu-gpu-performance.
Consult this skill when searching or navigating stored knowledge. Use when searching for stored knowledge, cross-referencing concepts, discovering connections, retrieving from palaces, finding past PR decisions. Do not use when creating new palace structures - use memory-palace-architect. DO NOT use when: processing new external resources - use knowledge-intake.
Outputs markdown digests and CSV exports for GitHub issues and PRs. Use when creating status reports, weekly updates, stakeholder briefings, generating GitHub comment digests, tracking initiative health. Do not use when release gates/readiness - use release-health-gates. DO NOT use when: project planning - use spec-kit:speckit-orchestrator.
NEVER escalate without investigation first. This is the Iron Law. Use when evaluating whether to escalate models, facing genuine complexity requiring deeper reasoning, novel patterns with no existing solutions, high-stakes decisions requiring capability investment. Do not use when thrashing without investigation - investigate root cause first. DO NOT use when: time pressure alone - urgency doesn't change task complexity. DO NOT use when: "just to be safe" - assess actual complexity instead.
Authentication patterns for external services: API keys, OAuth, token management, verification. authentication, API keys, OAuth, token management, credentials.
Architecture-aware project initialization combining online research with archetype selection. project initialization, new project, architecture decision, project setup, which architecture, choose architecture, project architecture Use when: initializing a new project and need to select an appropriate architecture based on project type, team size, domain complexity, and current best practices DO NOT use when: architecture is already decided - use project-init instead.
Guidelines from the NASA Power of 10 rules for writing robust, verifiable code. Adapted for general software development with context-appropriate rigor. Use when writing critical code paths, reviewing for robustness, improving code quality. Do not use as rigid requirements for all code - match rigor to consequence.
Use this skill at the START of every session. This is MANDATORY for quota management. location: plugin token_budget: 300. Use when session starts (mandatory), prompt sizes spike, tool calls increase, before long-running analyses or massive context loads. Do not use when context-optimization already handles the scenario. DO NOT use when: simple queries with minimal context.
Workflow orchestrator for Spec Driven Development. Coordinates skills and tracks progress. speckit workflow, spec driven development, speckit commands.
Process external resources into actionable knowledge with evaluation, storage, and application decisions. knowledge intake, article evaluation, paper review, external resource Use when: user shares links to articles, papers, or external resources DO NOT use when: searching existing knowledge - use knowledge-locator.
hype, and unnecessary framing. Includes termination and directness guidelines.
Consult this skill when designing storage and documentation systems. Use when organizing knowledge storage, managing configuration lifecycle, creating structured documentation, establishing naming conventions. Do not use when simple storage without lifecycle or structure needs.
Consult this skill when building evaluation or scoring systems. Use when implementing evaluation systems, creating quality gates, designing scoring rubrics, building decision frameworks. Do not use when simple pass/fail without scoring needs.
Use this skill as foundation for git workflows. Use when verifying workspace state before other git operations, checking staged changes, preflight checks before commits or PRs. Do not use when full commit workflow - use commit-messages instead. DO NOT use when: full PR preparation - use pr-prep.
Prevents sycophantic reasoning through checklist-based analysis, categorical integrity, and evidence-following to uncomfortable conclusions. Red Flags: "I agree that", "You are right", "Great point", "Absolutely", "That is a fair point", "I can see why", agreement without validation, softening conclusions, hedging without evidence, retracting under pressure. Use when analyzing conflicts, evaluating ethical claims, or noticing sycophantic thought patterns. Do not use for routine implementation or simple factual questions. CRITICAL: This skill overrides conversational tendencies toward politeness. Agreement requires validity and accuracy.