anyplot

Run and monitor the bulk-generate / impl-* pipeline for one or more specs to full 15-library coverage — dispatch sequentially, poll with the bundled checked-in scripts (never hand-rolled loops), read completion from impl:{lib}:done labels + GCS spot-checks, apply the correct stall thresholds, and report progress proactively. Use when asked to babysit, run bulk-generate, regenerate specs, monitor the pipeline, or bring specs to full coverage.

Take a finished change from diff to an open, green, review-clean PR — run the matching verify skills and local CI gates first, then commit, push and open the PR via /pull_request, watch the pipeline AND the Copilot review, fix sensible findings, resolve the review threads, and watch any Cloud Build deploy after merge. Never merges unless the user explicitly authorizes it in this session. Use when asked to open or create a PR, ship a change, or finish up a change.

Mine past Claude Code session transcripts for recurring friction — problems the user had to find manually, corrections, repeated tool errors, hand-rolled loops — and turn the patterns into skill gotchas, memory entries, or CLAUDE.md rules. Use when asked to optimize the skills, run a retro, review past sessions, or find recurring problems.

Run and exercise the anyplot FastAPI backend — start the server, sweep the read endpoints with curl, check payload shapes against the live DB, and respect the shared-production-database discipline. Use when asked to run, start, test, or verify the API, a router, an endpoint, or a backend change.

Test and smoke-run the shared Python layer in core/ — run pytest the way CI does, run the ruff + mypy gates, and import-check core modules (palette, constants, repositories) directly without the running app. Use when asked to run, test, lint, or verify core/, the database layer, palette, constants, or shared utilities.

Run and visually verify the anyplot app after frontend changes — start the dev servers, click through ONLY the flows the change touches via a browser MCP (claude-in-chrome or the Playwright plugin locally, playwright-core probe in the cloud), watch console and network, and judge style and legibility at a desktop AND a mobile viewport in BOTH light and dark theme. Use when asked to run, start, screenshot, verify, test in the browser, or visually check the app or a frontend change.