vscode

Use when the user asks about Mocha test runner APIs and patterns for unit tests. Triggers on questions like "Mocha hooks", "before/after setup", "describe/it structure", "async tests in Mocha", "test timeouts", ".only/.skip", "how to run a specific test", or test organization.

Use when the user asks about Playwright APIs, selectors, assertions, or patterns for E2E or functional tests. Triggers on questions like "how to click a button in Playwright", "Playwright locator", "page.waitFor", "expect toBeVisible", "Playwright test fixtures", or E2E test patterns.

Use when E2E Playwright tests fail, CI reports test failures, the user mentions "triage", "test failed", "flaky test", or wants to debug Electron/Playwright test results. Also use when investigating trace.zip files, test screenshots, or Playwright HTML report archives from CI.

Reviews pull requests for this VS Code extension. Use when reviewing PRs, doing self-review before sharing with the team, or when user mentions "review PR", "review changes", "self-review", or "check my PR". Focuses on project-specific patterns and critical requirements.

Use when the user asks about Sinon stubbing, spying, mocking, or test double APIs for unit tests. Triggers on questions like "how do I stub this", "Sinon fake timers", "spy vs stub", "sandbox usage", "assert.calledWith", "stub.resolves", "sinon.match", or test double patterns.

Use when the user asks about VS Code API definitions, methods, interfaces, events, types, or wants to understand what VS Code APIs are available. Triggers on questions like "what does vscode.X do", "how to use VS Code API", "VS Code type definition", or checking API compatibility.