resume

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. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.

BDD-first testing with bun:test in this repository — scenario-oriented examples, describe/it layout rules, library-integration testing, and no Cucumber. Use when writing or changing tests, adding fixtures, mocking libraries, or when the user mentions BDD, TDD, bun:test, or Vitest.

How to check a web page in a real browser in this repository, using only agent-browser. Use when verifying UI changes, looking at a page or component, taking screenshots, comparing against a baseline, testing a viewport or dark mode, or serving a production build over HTTPS to try it.

Repository conventions for this Bun starter — Bun-only tooling, workspace layout, quality gates, Lefthook hooks, Conventional Commits, Tailwind CSS, SvelteKit, type checking with `bun check`, and reference repositories in repos/. Use when starting work in this repository, choosing tools, running checks, committing, or when AGENTS.md / CLAUDE.md point here.

Svelte 5 and SvelteKit 3 in this repository — looking up the official documentation, checking components with the official autofixer and svelte-check, the runes conventions the code follows, and how components are tested. Use when writing or changing .svelte files, routes, vite.config.ts, hooks or the prerender setup, or when a Svelte or SvelteKit API is in doubt.