Use when reviewing a pull request for bugs, CLAUDE.md compliance, Convex backend correctness, and Angular frontend best practices. Triggers on "review PR", "code review", or a PR number/URL.
Use when running E2E tests, checking if E2E tests pass, or validating changes with Playwright tests. Covers affected-only runs (preferred), full suite, parallel execution, and port isolation for concurrent runs.
Use when a PR needs finishing — CI is failing, code review comments are pending, or a PR opened by an autonomous agent needs human-quality polish before merge. Also use when user says "go-pr-finish" followed by a PR number or URL.
Use when a less powerful model (Sonnet, Haiku) needs to implement a feature or bugfix with safety rails — always works from an isolated worktree and new branch, submits a PR to develop instead of merging directly. Also use when user says "go-pr" followed by a task description.
Use when starting a feature, bugfix, or task that needs the full development cycle — brainstorm through landed commit on develop. Also use when user says "go" followed by a task description.
Use when starting a cross-layer feature touching frontend, backend, and tests simultaneously, or when user says "go team". Uses Agent Teams for parallel coordinated implementation instead of subagents.
Use when autonomously testing a running web app via Playwright MCP for extended unattended sessions using Agent Teams — exploratory QA, smoke tests, regression hunts, and filing bugs to Linear with maximum browser throughput
Use when working with color naming, color theory, color spaces, color definitions, or any task involving color knowledge - palettes, ramps, gradients, conversions, accessibility, perceptual matching, pigment mixing, print-vs-screen color, CSS color syntax, or historical color terminology. Use this skill whenever the user is choosing, comparing, generating, naming, converting, or explaining colors, even if they do not explicitly ask for "color theory."