Testing
Unit tests, integration tests, test automation
mcp-integration
by ShunsukeHayashi
MCP server integration and tool usage. Use when working with MCP tools, searching for tools, or configuring MCP servers. Triggers: mcp, tools, miyabi-mcp-bundle, 172 tools
Test-Driven Development (TDD) Workflow
by ShunsukeHayashi
Miyabi Plugins for Claude Code - 25+ Agents, 22 Skills, 50+ Commands
Cognitive-Lensing v1.0.0
by DNYoussef
Context Cascade - Nested Plugin Architecture for Claude Code Official Claude Code Plugin Version 3.1.0 Last updated: 2026-01-09 (see docs/COMPONENT-COUNTS.json for source counts) Context-saving nested architecture: Playbooks -> Skills -> Agents -> Commands. Load only what you need, saving 90%+ context space.
living-documentation
by PeterFile
Sync spec files with code changes. Triggers when modifying code that affects .kiro/specs//requirements.md or .kiro/specs//design.md. Use after implementing features, fixing bugs, or refactoring that changes behavior documented in specs.
sequential-orchestration
by PeterFile
"Execute spec tasks one at a time with tmux visibility. Python-based orchestrator with transparent serial execution. Triggers on: rate limit, overnight run, throttled execution, avoid quota exhaustion, sequential mode, slow execution, or user says 'Run sequential orchestration for <spec>'."
CI/CD Quality & Debugging Loop (Loop 3)
by DNYoussef
Context Cascade - Nested Plugin Architecture for Claude Code Official Claude Code Plugin Version 3.1.0 Last updated: 2026-01-09 (see docs/COMPONENT-COUNTS.json for source counts) Context-saving nested architecture: Playbooks -> Skills -> Agents -> Commands. Load only what you need, saving 90%+ context space.
🦀 Rust Development Workflow
by ShunsukeHayashi
Miyabi Plugins for Claude Code - 25+ Agents, 22 Skills, 50+ Commands
plg-ideas
by SkeneTechnologies
When the user wants PLG ideas, tactics, or inspiration -- a mega-reference of 100+ product-led growth strategies organized by category. Also use when the user says "growth ideas," "PLG playbook," "growth tactics," "what should we try," or "growth brainstorm." For PLG strategy, see plg-strategy. For experimentation, see growth-experimentation.
speakturbo-tts
by EmZod
Give your agent the ability to speak to you real-time. Talk to your Claude! Ultra-fast TTS, text-to-speech, voice synthesis, audio output with ~90ms latency. 8 built-in voices for instant voice responses. For voice cloning, use the speak skill.
usage-based-pricing
by SkeneTechnologies
When the user wants to design or implement usage-based, consumption, or metered pricing -- including credit systems, overage handling, or billing infrastructure. Also use when the user says "pay per use," "metered billing," "credit system," "usage pricing," or "consumption pricing." For broader pricing strategy, see pricing-strategy. For expansion, see expansion-revenue.
expansion-revenue
by SkeneTechnologies
When the user wants to grow revenue from existing customers -- including seat expansion, plan upgrades, usage upsells, or cross-sell strategies. Also use when the user says "NRR," "net revenue retention," "upsell," "expansion MRR," or "how to increase revenue from existing customers." For pricing, see pricing-strategy. For upgrade screens, see paywall-upgrade-cro.
git-workflow
by 0xlayerghost
"[AUTO-INVOKE] MUST be invoked BEFORE creating git commits, PRs, or code reviews. Covers Conventional Commits, PR templates, review requirements, and AI-assisted development rules. Trigger: any task involving git commit, git push, PR creation, or code review."
code-review
by alexanderguy
Perform a code review or pull request review on a branch
openclaw
by PaulRBerg
This skill should be used when the user mentions "openclaw", "OpenClaw CLI", asks to "send a message via openclaw", "manage openclaw agents", "configure openclaw gateway", "check openclaw status", "run openclaw agent", or asks about OpenClaw setup, channels, devices, or messaging automation.
vitest
by PaulRBerg
This skill should be used when the user asks to "write tests", "add tests", "test coverage", "run tests", "debug failing tests", "mock functions", or mentions Vitest, unit tests, component tests, test-driven development, or testing utilities. Provides comprehensive Vitest v4 guidance for TypeScript React/Next.js projects.
review-code
by mgiovani
Perform comprehensive multi-agent code review for PRs, commits, or entire
finishing-a-development-branch
by izyanrajwani
Git branch completion workflow. Use when implementation is complete, tests pass, and a feature branch needs to be integrated via merge, pull request, or cleanup.
test-suite
by mgiovani
"Generate comprehensive test suites with coverage analysis and parallel test writing. Automatically activates when users want to write tests, add test coverage, generate test cases, improve testing, or analyze coverage gaps. Supports pytest, vitest, jest, and all major test frameworks."
dev-workflow
by lodekeeper
Multi-agent development workflow for complex Lodestar features. Use for any task requiring architecture planning, implementation, and review. Covers spec design with gpt-advisor, implementation via Codex CLI or Claude CLI, review with sub-agents, and PR creation.
consensus-clients
by lodekeeper
Use when comparing Ethereum consensus client implementations, looking up how a specific client implements a spec feature, checking client activity (PRs, issues, releases), or understanding architectural differences between Lodestar, Lighthouse, Prysm, Teku, Nimbus, and Grandine.
implement-feature
by mgiovani
"Implement features using senior staff engineer best practices with parallel subagent orchestration. Automatically activates when users want to implement a new feature, add functionality, build a component, or create new capabilities. Follows SOLID, DRY, and YAGNI principles with automated project discovery and quality verification."
dispatching-parallel-agents
by izyanrajwani
Dispatches one subagent per independent domain to parallelize investigation/fixes. Use when you have 2+ unrelated failures (e.g., separate failing test files, subsystems, bugs) with no shared state or ordering dependencies.
test-driven-development
by izyanrajwani
Red-green-refactor development methodology requiring verified test coverage. Use for feature implementation, bugfixes, refactoring, or any behavior changes where tests must prove correctness.
playwright-cli
by arlenagreer
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, extract information from web pages, debug web apps, record browser sessions as video, mock or intercept API requests, manage browser cookies/localStorage, generate Playwright test code, capture execution traces, or run multiple browser sessions concurrently.