Combine media assets (GIFs, videos) into composite tutorials with vertical/horizontal layouts.

Create clear, testable specifications with user stories and acceptance criteria. spec writing, feature specification, requirements, user stories Use when: creating new specifications or writing acceptance criteria DO NOT use when: converting specs to tasks - use task-planning.

Use this skill for API surface evaluation and design review. Use when reviewing API design, auditing consistency, governing documentation, researching API exemplars. Do not use when architecture review - use architecture-review. DO NOT use when: implementation bugs - use bug-review.

Use this skill BEFORE resource-intensive operations. Establish baselines proactively. location: plugin token_budget: 400. Use when session starts (auto-load with token-conservation), planning builds or training that could pin CPUs/GPUs for >1 minute, retrying failed resource-heavy commands. Do not use when simple operations with no resource impact. DO NOT use when: quick single-file operations.

Multi-LLM deliberation for strategic decisions via expert pressure-testing and consensus building. Use for critical, irreversible, or high-stakes architecture choices and conflicts. Skip for trivial or reversible decisions.

Configure three-layer pre-commit system with linting, type checking, and testing hooks. Use for quality gate setup and code standards. Skip if pre-commit is optimally configured.

Generate terminal recordings using VHS tape files, produces GIF outputs.

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.

Use this skill for scope-focused PR reviews. 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 systematic change analysis with risk scoring. 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 BEFORE starting complex tasks. Check context levels proactively. Use when context usage approaches 50% of window, tasks need decomposition, complex multi-step operations planned, context pressure is high. Do not use when simple single-step tasks with low context usage. DO NOT use when: already using mcp-code-execution for tool chains.

hype, and unnecessary framing. Includes termination and directness guidelines.

Workflow orchestrator for Spec Driven Development. Coordinates skills and tracks progress. speckit workflow, spec driven development, speckit commands.

Use this skill at the BEGINNING of any detailed review for consistent structure. Use when starting any detailed review workflow, needing consistent structure for capturing context and findings, ensuring comparable review outputs. Do not use when quick catchup without formal review - use catchup. DO NOT use when: diff-focused analysis - use diff-analysis.

Create markdown-based behavioral rules preventing unwanted actions. create hookify rule, behavioral rule, prevent behavior, block command Use when: preventing dangerous commands, blocking debug commits, enforcing conventions DO NOT use when: hook scope (abstract:hook-scope-guide), SDK hooks (abstract:hook-authoring), evaluating hooks (abstract:hooks-eval).

Detect and flag AI-generated content markers in documentation and prose. Use when reviewing documentation for AI markers, cleaning up LLM-generated content, or auditing prose quality. Do not use when generating new content (use doc-generator) or learning writing styles (use style-learner).

Use this skill for systematic bug hunting with evidence trails. 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.

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

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.

Use this skill for general documentation updates with built-in quality gates. 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.