claude-code-plugins

Use when automating browser tasks - clicking, filling forms, taking screenshots, debugging UI, or testing web flows. Requires chrome-devtools or playwright MCP.

Use when analyzing Claude Code raw session logs, parsing JSONL transcripts, investigating agent behavior, extracting metrics from session data, debugging subagent dispatches, or building session analysis tools. Triggers on session IDs, JSONL paths, ~/.claude/projects references, or requests to understand what happened in a CC session.

Optimize system prompts for Claude Code agents using proven prompt engineering patterns. Use when users request prompt improvement, optimization, or refinement for agent workflows, tool instructions, or system behaviors.

Use when writing or modifying frontend React/HTML components, creating interactive widgets, building forms, or implementing overlays/modals/dropdowns — ensures accessible output by default with correct ARIA, keyboard, focus, and screen reader support

(user)

Use when writing or reviewing Playwright E2E tests - locator strategies, Page Object Model, auto-waiting, network interception, and WordPress/WooCommerce test helpers.

Use when writing or reviewing Go tests - standard testing package, table-driven tests, subtests, test helpers, httptest, benchmarks, fuzz testing, and interface-based mocking.

Use when writing or reviewing JavaScript/TypeScript tests - Jest/Vitest assertions, React Testing Library queries, module mocking, async patterns, and snapshot discipline.

Use when writing or reviewing PHP tests - PHPUnit assertions, WordPress test utilities (WP_UnitTestCase, factories), WooCommerce test patterns, and Brain Monkey isolation.

Use when writing or reviewing Python tests - pytest fixtures, parametrize, conftest, mock/patch patterns, pytest-asyncio, hypothesis property-based testing, freezegun/time-machine, factory_boy, and coverage configuration.

Use when writing or reviewing Rust tests - built-in test framework, assert macros, Result-based tests, async test patterns, mockall, proptest, rstest, test-case, insta snapshots, criterion benchmarks, and serial_test isolation.

Use when facing tight coupling, rigid designs, unclear responsibilities, hard-to-test code, or choosing between design patterns — diagnoses code smells and routes to the right pattern from GoF, SOLID, hexagonal architecture, and composable designs

Core test quality principles - philosophy, smells, structure, mocking, and coverage. For language-specific patterns see php-testing-patterns, js-testing-patterns, e2e-testing-patterns.

Use when implementing UI from Figma designs, comparing implementations against Figma, performing design gap analysis, or planning Figma-based frontend work. Triggers on Figma URLs, node IDs, design-to-code tasks, requests to match a design, or Figma MCP setup and troubleshooting. Requires a working Figma MCP server.

Use when writing or reviewing WordPress plugin/theme PHP code, fixing PHPCS errors, resolving XSS/SQL injection/CSRF vulnerabilities, implementing i18n translations, or building AJAX/REST handlers - provides WPCS coding standards, security patterns, hooks API, database operations, and admin interface patterns.

Use when synchronizing text copy between Figma designs and implemented code. Triggers on requests to update copy from Figma, sync text with designs, check copy matches design, or align UI text with Figma. Requires a working Figma MCP server and browser MCP (chrome-devtools or playwright).

Use when creating GitHub pull requests - provides structured workflow for pre-flight checks, context gathering, content generation, user approval gate, and testing steps synthesis from related PRs.

Use before depending on or presenting the current date or time in any context — writing timestamps into files (Last updated headers, document metadata), stating the date or time in responses, calculating staleness or deadlines, or any reasoning where 'right now' is a fact you need. The system prompt date is a snapshot from conversation start and may be stale; always verify with `date`. Also use for time zone conversions, scheduling across regions, Unix timestamps, date arithmetic, and determining what day a date falls on.

Use when asked to work on, investigate, or fix a Linear issue by ID or URL, or when given a Linear issue ID like WOOPLUG-1234.

Use when needing to interact with WooCommerce in a browser - debugging UI issues, verifying changes, testing flows, taking screenshots, or exploring admin and frontend pages (shop, cart, checkout, my account). Requires a browser automation MCP server (chrome-devtools or playwright).

Core logic for dex knowledge capture: project discovery, document formats, CLAUDE.md budget management, and promotion flow. Referenced by all dex commands.

Use when creating presentation slides, converting markdown to PDF/PPTX/HTML, or asked about Marp, Beamer, or reveal.js. Triggers on mentions of slides, presentations, decks, or requests to generate visual presentations from content.

Analyze and improve Marp markdown presentations using SlideGauge. Use when working with Marp slides, presentation files ending in .md with marp frontmatter, or when user asks to check, analyze, improve, or validate slide quality. Requires slidegauge package (installed via uvx).