saffron-health

Interact with the running VSCode extension via Playwright. Use when automating, testing, or debugging the OpenCode webview UI.

Create a spec sheet for the given feature/fix request in specs/ directory. Use when planning a significant new feature or complex fix.

Implement a single phase of a spec. Use when given a spec file and a phase number to implement.

Browser automation CLI using Playwright. Use when automating browser workflows, filling forms, clicking elements, scraping pages, or debugging web issues.

Review a spec for under-specified areas, bugs, and adherence to the generate-spec skill. Use when asked to review, critique, or check a spec.

Update AGENTS.md files based on session learnings about a topic. Use when documenting patterns, commands, or conventions discovered during development.

Address PR review comments systematically. Use when responding to code review feedback on a pull request.

Stage all changes and commit with appropriate message, showing changed files and edits. Use when you need to create a git commit.

Browser automation CLI for building, maintaining, and running browser automation workflows by inspecting live pages and prototyping interactions.

Read-only Libretto workflow for diagnosing live browser state without clicks, typing, navigation, or mutation requests.

Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.

Automate user-installed Electron desktop apps (Slack, Discord, VS Code, Notion, Figma, Spotify, etc.) via CDP using this repo's Libretto CLI. Use when the task is to control a local desktop app on the user's machine, not this repo's own Electron app. Triggers: "desktop Slack app", "connect to Electron app", "remote-debugging-port", "CDP desktop app", "automate VS Code desktop app".

Create a spec sheet for the given feature/fix request in specs/ directory. Use when planning a significant new feature or complex fix.

Stage ALL changes in the repository (not just session changes), commit, and push. Use when you need to commit all pending changes.

Commit and push changes, creating or updating a PR as needed. Use for standard push workflow.

Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries. Use when user: configures tasks/workflows/pipelines, creates packages, sets up monorepo, shares code between apps, runs changed/affected packages, debugs cache, or has apps/packages directories.