inbox-zero

Guidelines for testing the application with Vitest, including unit tests, integration tests (emulator), AI tests, and eval suites for LLM features

Cursor Cloud VM setup and service startup instructions for local development

Guidelines for implementing LLM (Language Model) functionality in the application

Simplify and refine recently modified code for clarity, consistency, and maintainability while preserving exact behavior. Use when asked to simplify, polish, refactor lightly, or clean up current-session changes before review or PR.

Commit changes and open a pull request with safe metadata

Review prompt and tool-description changes in a branch or PR. Use when asked to audit system prompts, prompt builders, tool descriptions, prompt inputs, or nearby evals/tests; summarize what changed; identify guidance that feels eval-shaped or too heavy for product use; and find repeated instructions between the main prompt and tool descriptions.

Add a new changelog entry to docs/changelog-entries/

Update workspace packages while respecting the repo's pinned package list in .ncurc.cjs. Use when the user asks to update dependencies or refresh package versions.

Label a PR as ready for QA so the QA server picks it up automatically

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.

Run browser QA flows and write a JSON report

Guidelines for writing tests for LLM-related functionality

Use the Inbox Zero API CLI to inspect the live API schema, list and manage automation rules, and read inbox analytics through the public API. Use this when a task involves Inbox Zero rules, stats, or API-driven automation and can be solved through the CLI instead of browser interaction.

Start a background loop that monitors PR for new review comments and addresses them.

End-to-end feature testing — browser QA, API verification, eval tests, or any combination. Covers browser interactions (via agent-browser CLI), Google Workspace operations (gws CLI), API calls, and LLM eval tests. Can also persist tests as reusable QA flows or eval files.

Review, commit, create PR, then auto-address review comments in a loop.

Review code changes, auto-fix safe issues, and report bugs

Run and debug E2E flow tests. Use when triggering E2E tests, checking test status, debugging failures with Axiom logs, or setting up local E2E testing.

Complete fullstack workflow combining GET API routes, server actions, SWR data fetching, and form handling. Use when building features that need both data fetching and mutations from API to UI.

How to use Prisma

Project structure and file organization guidelines

Write focused unit tests for backend and utility logic

Resolve active pull request comments and prepare replies

Explain recent changes and provide a structured summary with security checks

Create a new browser QA flow file from the template

Pause execution for a user-specified duration

Add environment variable

How to do backend logging

UI component and styling guidelines using Shadcn UI, Radix UI, and Tailwind