Design

Construct temporary, session-specific memory palaces for complex projects and conversations. Triggers: session context, project memory, conversation state, temporary storage, session palace, context preservation, complex project, extended conversation 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 session-scoped temporary knowledge structures.

Gemini CLI delegation workflow implementing delegation-core for Google's Gemini models. Triggers: gemini cli, gemini delegation, google gemini, 1M context, large file analysis, gemini batch, gemini summarization, gemini extraction Use when: delegation-core selected Gemini, need Gemini's 1M+ token context window, batch processing or large document summarization required DO NOT use when: deciding which model to use - use delegation-core first. DO NOT use when: gemini CLI not installed or authenticated. Consult this skill when implementing Gemini-specific delegation workflows.

Systematically uncover and fix bugs using language-specific expertise and reproducible evidence. Triggers: bug hunting, defect detection, debugging, fix verification, bug fix, regression check, error investigation, defect documentation Use when: deep bug hunting needed, documenting defects, verifying fixes, systematic debugging required DO NOT use when: test coverage audit - use test-review instead. DO NOT use when: architecture issues - use architecture-review. Use this skill for systematic bug hunting with evidence trails.

Detect codebase bloat through progressive analysis: dead code, duplication, complexity, and documentation bloat. Triggers: bloat detection, dead code, code cleanup, duplication, redundancy, codebase health, technical debt, unused code Use when: preparing for refactoring, context usage is high, quarterly maintenance, pre-release cleanup DO NOT use when: actively developing new features, time-sensitive bug fixes. DO NOT use when: codebase is < 1000 lines (insufficient scale for bloat). Progressive 3-tier detection: quick scan → targeted analysis → deep audit.

Audit Makefiles for duplication, portability, and idiomatic GNU Make usage. Triggers: Makefile review, build system, GNU Make, portability, deduplication, pattern rules, automatic variables, dependency graph Use when: auditing Makefiles, reviewing build system, checking portability, eliminating recipe duplication DO NOT use when: creating new Makefiles - use abstract:make-dogfood. DO NOT use when: architecture review - use architecture-review. Use this skill for Makefile audit and optimization.

Evaluate and upgrade test suites with TDD/BDD rigor, coverage tracking, and quality assessment. Triggers: test audit, test coverage, test quality, TDD, BDD, test gaps, test improvement, coverage analysis, test remediation Use when: auditing test suites, analyzing coverage gaps, improving test quality, evaluating TDD/BDD compliance DO NOT use when: writing new tests - use parseltongue:python-testing. DO NOT use when: updating existing tests - use sanctum:test-updates. Use this skill for test suite evaluation and quality assessment.

Delegate tasks to external LLM services (Gemini, Qwen) with quota, logging, and error handling. Triggers: delegate task, external LLM, gemini, qwen, large context, offload Use when: tasks exceed context window or need cheaper processing DO NOT use when: task requires Claude's reasoning.

Consolidates ephemeral LLM-generated markdown files into permanent documentation. Triggers: consolidate docs, untracked reports, ephemeral files, git cleanup, report consolidation, knowledge extraction, REPORT.md files, ANALYSIS.md files Use when: you have untracked *_REPORT.md or *_ANALYSIS.md files, git status shows markdown artifacts that shouldn't be committed, preparing PR and need to clean up working artifacts, preserving insights from code reviews DO NOT use when: files are already in docs/ or skills/ locations. DO NOT use when: files are intentionally temporary scratch notes. DO NOT use when: source files have no extractable value. Merges valuable content into permanent documentation, then deletes source files.

Code design patterns: pure functions, immutability, composition, and async. Use when designing code or functions.

Consolidate README content using language-aware exemplars, internal doc linkage, and reproducible evidence. Triggers: README update, documentation refresh, readme structure, exemplar research, language-aware docs, readme modernization, project documentation Use when: README requires structural refresh, adding features to documentation, aligning readme with exemplar standards, improving project presentation DO NOT use when: updating inline docs - use doc-updates. DO NOT use when: consolidating ephemeral reports - use doc-consolidation. Run git-workspace-review first to capture repo context.

Scope-focused PR code review that validates against original requirements and routes out-of-scope findings to GitHub issues. Triggers: PR review, pull request review, scope validation, requirement compliance, backlog triage, code review, blocking issues Use when: reviewing PRs, validating against requirements, triaging findings to backlog, preventing overengineering DO NOT use when: preparing PRs - use pr-prep instead. DO NOT use when: deep code review - use pensive:unified-review. Use this skill for scope-focused PR reviews.

Evaluate codebase architecture against ADRs, coupling rules, and team guardrails. Triggers: architecture review, ADR audit, coupling analysis, design review, principle checks, Law of Demeter, architecture assessment Use when: reviewing architecture decisions, auditing ADR compliance, analyzing coupling, validating design principles DO NOT use when: selecting architecture paradigms - use archetypes skills. DO NOT use when: API surface review - use api-review. Use this skill for architecture assessment and compliance.

Methodology for categorizing changes, assessing risks, and creating summaries from any changeset. Triggers: diff analysis, changeset review, risk assessment, change categorization, semantic analysis, release preparation, change summary, git diff Use when: analyzing specific changesets, assessing risk of changes, preparing release notes, categorizing changes by type and impact DO NOT use when: quick context catchup - use catchup instead. DO NOT use when: full PR review - use review-core with pensive skills. Use this skill for systematic change analysis with risk scoring.

detailed hook evaluation framework for Claude Code and Agent SDK hooks. Triggers: hook audit, hook security, hook performance, hook compliance, SDK hooks, hook evaluation, hook benchmarking, hook vulnerability Use when: auditing existing hooks for security vulnerabilities, benchmarking hook performance, implementing hooks using Python SDK, understanding hook callback signatures, validating hooks against compliance standards DO NOT use when: deciding hook placement - use hook-scope-guide instead. DO NOT use when: writing hook rules from scratch - use hookify instead. DO NOT use when: validating plugin structure - use validate-plugin instead. Use this skill BEFORE deploying hooks to production.

Update documentation with writing guideline enforcement, consolidation detection, and accuracy verification. Triggers: documentation update, docs update, ADR, docstrings, writing guidelines, readme update, debloat docs Use when: updating documentation after code changes, enforcing writing guidelines, maintaining ADRs DO NOT use when: README-specific updates - use update-readme instead. DO NOT use when: complex multi-file consolidation - use doc-consolidation. Use this skill for general documentation updates with built-in quality gates.

Complete guide for writing Claude Code and SDK hooks with security-first design. Triggers: hook creation, hook writing, PreToolUse, PostToolUse, UserPromptSubmit, tool validation, logging hooks, context injection, workflow automation Use when: creating new hooks for tool validation, logging operations for audit, injecting context before prompts, enforcing project-specific workflows, preventing dangerous operations in production DO NOT use when: logic belongs in core skill - use Skills instead. DO NOT use when: complex multi-step workflows needed - use Agents instead. DO NOT use when: behavior better suited for custom tool. Use this skill BEFORE writing any hook. Check even if unsure.

Methodology for summarizing changes, extracting insights, and identifying follow-up actions. Triggers: catchup, what changed, summarize changes, context acquisition, handoff, progress review, recent changes, git log analysis, sprint summary 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. Use this skill to quickly understand "what changed and what matters".

Guide to effective Claude Code skill authoring using TDD methodology and persuasion principles. Triggers: skill authoring, skill writing, new skill, TDD skills, skill creation, skill best practices, skill validation, skill deployment, skill compliance Use when: creating new skills from scratch, improving existing skills with low compliance rates, learning skill authoring best practices, validating skill quality before deployment, understanding what makes skills effective DO NOT use when: evaluating existing skills - use skills-eval instead. DO NOT use when: analyzing skill architecture - use modular-skills instead. DO NOT use when: writing general documentation for humans. YOU MUST write a failing test before writing any skill. This is the Iron Law.

Interactive selector and implementation planner for architecture paradigms. Triggers: architecture selection, pattern comparison, system design, ADR creation, architecture decision, paradigm evaluation, new system architecture, architecture planning, which architecture, compare architectures 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. DO NOT use when: reviewing existing architecture - use architecture-review instead. Use this skill BEFORE making architecture decisions. Check even if unsure about needs.

Workflow for capturing evidence and citations to create reproducible analyses and audit trails. Triggers: evidence capture, citations, reproducible analysis, audit trail, documentation, evidence logging, findings documentation Use when: conducting any review that needs evidence trails, creating audit documentation, ensuring reproducibility of analyses DO NOT use when: quick informal checks without documentation needs. DO NOT use when: structured output is the focus - use structured-output. Use this skill as foundation for all evidence-based review workflows.