{"owner":"JimmyLv","repo":"BibiGPT-v1","hasSkills":true,"totalSkillsCount":98,"totalTokensCount":76524,"categories":["anthropic-skill","root-instruction"],"hasMcp":false,"mcpConfig":null,"found":[".agents/skills/agent-browser/SKILL.md",".agents/skills/agent-browser/references/authentication.md",".agents/skills/agent-browser/references/commands.md",".agents/skills/agent-browser/references/profiling.md",".agents/skills/agent-browser/references/proxy-support.md",".agents/skills/agent-browser/references/session-management.md",".agents/skills/agent-browser/references/snapshot-refs.md",".agents/skills/agent-browser/references/video-recording.md",".agents/skills/ai-sdk/SKILL.md",".agents/skills/ai-sdk/references/ai-gateway.md",".agents/skills/ai-sdk/references/common-errors.md",".agents/skills/ai-sdk/references/devtools.md",".agents/skills/ai-sdk/references/type-safe-agents.md",".agents/skills/bibi/SKILL.md",".agents/skills/find-skills/SKILL.md",".agents/skills/next-best-practices/SKILL.md",".agents/skills/next-best-practices/async-patterns.md",".agents/skills/next-best-practices/bundling.md",".agents/skills/next-best-practices/data-patterns.md",".agents/skills/next-best-practices/debug-tricks.md",".agents/skills/next-best-practices/directives.md",".agents/skills/next-best-practices/error-handling.md",".agents/skills/next-best-practices/file-conventions.md",".agents/skills/next-best-practices/font.md",".agents/skills/next-best-practices/functions.md",".agents/skills/next-best-practices/hydration-error.md",".agents/skills/next-best-practices/image.md",".agents/skills/next-best-practices/metadata.md",".agents/skills/next-best-practices/parallel-routes.md",".agents/skills/next-best-practices/route-handlers.md",".agents/skills/next-best-practices/rsc-boundaries.md",".agents/skills/next-best-practices/runtime-selection.md",".agents/skills/next-best-practices/scripts.md",".agents/skills/next-best-practices/self-hosting.md",".agents/skills/next-best-practices/suspense-boundaries.md",".agents/skills/vercel-react-best-practices/AGENTS.md",".agents/skills/vercel-react-best-practices/README.md",".agents/skills/vercel-react-best-practices/SKILL.md",".agents/skills/vercel-react-best-practices/rules/advanced-event-handler-refs.md",".agents/skills/vercel-react-best-practices/rules/advanced-init-once.md",".agents/skills/vercel-react-best-practices/rules/advanced-use-latest.md",".agents/skills/vercel-react-best-practices/rules/async-api-routes.md",".agents/skills/vercel-react-best-practices/rules/async-defer-await.md",".agents/skills/vercel-react-best-practices/rules/async-dependencies.md",".agents/skills/vercel-react-best-practices/rules/async-parallel.md",".agents/skills/vercel-react-best-practices/rules/async-suspense-boundaries.md",".agents/skills/vercel-react-best-practices/rules/bundle-barrel-imports.md",".agents/skills/vercel-react-best-practices/rules/bundle-conditional.md",".agents/skills/vercel-react-best-practices/rules/bundle-defer-third-party.md",".agents/skills/vercel-react-best-practices/rules/bundle-dynamic-imports.md",".agents/skills/vercel-react-best-practices/rules/bundle-preload.md",".agents/skills/vercel-react-best-practices/rules/client-event-listeners.md",".agents/skills/vercel-react-best-practices/rules/client-localstorage-schema.md",".agents/skills/vercel-react-best-practices/rules/client-passive-event-listeners.md",".agents/skills/vercel-react-best-practices/rules/client-swr-dedup.md",".agents/skills/vercel-react-best-practices/rules/js-batch-dom-css.md",".agents/skills/vercel-react-best-practices/rules/js-cache-function-results.md",".agents/skills/vercel-react-best-practices/rules/js-cache-property-access.md",".agents/skills/vercel-react-best-practices/rules/js-cache-storage.md",".agents/skills/vercel-react-best-practices/rules/js-combine-iterations.md",".agents/skills/vercel-react-best-practices/rules/js-early-exit.md",".agents/skills/vercel-react-best-practices/rules/js-hoist-regexp.md",".agents/skills/vercel-react-best-practices/rules/js-index-maps.md",".agents/skills/vercel-react-best-practices/rules/js-length-check-first.md",".agents/skills/vercel-react-best-practices/rules/js-min-max-loop.md",".agents/skills/vercel-react-best-practices/rules/js-set-map-lookups.md",".agents/skills/vercel-react-best-practices/rules/js-tosorted-immutable.md",".agents/skills/vercel-react-best-practices/rules/rendering-activity.md",".agents/skills/vercel-react-best-practices/rules/rendering-animate-svg-wrapper.md",".agents/skills/vercel-react-best-practices/rules/rendering-conditional-render.md",".agents/skills/vercel-react-best-practices/rules/rendering-content-visibility.md",".agents/skills/vercel-react-best-practices/rules/rendering-hoist-jsx.md",".agents/skills/vercel-react-best-practices/rules/rendering-hydration-no-flicker.md",".agents/skills/vercel-react-best-practices/rules/rendering-hydration-suppress-warning.md",".agents/skills/vercel-react-best-practices/rules/rendering-svg-precision.md",".agents/skills/vercel-react-best-practices/rules/rendering-usetransition-loading.md",".agents/skills/vercel-react-best-practices/rules/rerender-defer-reads.md",".agents/skills/vercel-react-best-practices/rules/rerender-dependencies.md",".agents/skills/vercel-react-best-practices/rules/rerender-derived-state-no-effect.md",".agents/skills/vercel-react-best-practices/rules/rerender-derived-state.md",".agents/skills/vercel-react-best-practices/rules/rerender-functional-setstate.md",".agents/skills/vercel-react-best-practices/rules/rerender-lazy-state-init.md",".agents/skills/vercel-react-best-practices/rules/rerender-memo-with-default-value.md",".agents/skills/vercel-react-best-practices/rules/rerender-memo.md",".agents/skills/vercel-react-best-practices/rules/rerender-move-effect-to-event.md",".agents/skills/vercel-react-best-practices/rules/rerender-simple-expression-in-memo.md",".agents/skills/vercel-react-best-practices/rules/rerender-transitions.md",".agents/skills/vercel-react-best-practices/rules/rerender-use-ref-transient-values.md",".agents/skills/vercel-react-best-practices/rules/server-after-nonblocking.md",".agents/skills/vercel-react-best-practices/rules/server-auth-actions.md",".agents/skills/vercel-react-best-practices/rules/server-cache-lru.md",".agents/skills/vercel-react-best-practices/rules/server-cache-react.md",".agents/skills/vercel-react-best-practices/rules/server-dedup-props.md",".agents/skills/vercel-react-best-practices/rules/server-hoist-static-io.md",".agents/skills/vercel-react-best-practices/rules/server-parallel-fetching.md",".agents/skills/vercel-react-best-practices/rules/server-serialization.md",".agents/skills/web-design-guidelines/SKILL.md","AGENTS.md"],"skills":{".agents/skills/agent-browser/SKILL.md":"---\nname: agent-browser\ndescription: 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.\nallowed-tools: Bash(npx agent-browser:*), Bash(agent-browser:*)\n---\n\n# Browser Automation with agent-browser\n\n## Core Workflow\n\nEvery browser automation follows this pattern:\n\n1. **Navigate**: `agent-browser open `\n2. **Snapshot**: `agent-browser snapshot -i` (get element refs like `@e1`, `@e2`)\n3. **Interact**: Use refs to click, fill, select\n4. **Re-snapshot**: After navigation or DOM changes, get fresh refs\n\n```bash\nagent-browser open https://example.com/form\nagent-browser snapshot -i\n# Output: @e1 [input type=\"email\"], @e2 [input type=\"password\"], @e3 [button] \"Submit\"\n\nagent-browser fill @e1 \"user@example.com\"\nagent-browser fill @e2 \"password123\"\nagent-browser click @e3\nagent-browser wait --load networkidle\nagent-browser snapshot -i # Check result\n```\n\n## Command Chaining\n\nCommands can be chained with `&&` in a single shell invocation. The browser persists between commands via a background daemon, so chaining is safe and more efficient than separate calls.\n\n```bash\n# Chain open + wait + snapshot in one call\nagent-browser open https://example.com && agent-browser wait --load networkidle && agent-browser snapshot -i\n\n# Chain multiple interactions\nagent-browser fill @e1 \"user@example.com\" && agent-browser fill @e2 \"password123\" && agent-browser click @e3\n\n# Navigate and capture\nagent-browser open https://example.com && agent-browser wait --load networkidle && agent-browser screenshot page.png\n```\n\n**When to chain:** Use `&&` when you don't need to read the output of an intermediate command before proceeding (e.g., open + wait + screenshot). Run commands separately when you need to parse the output first (e.g., snapshot to discover refs, then interact using those refs).\n\n## Essential Commands\n\n```bash\n# Navigation\nagent-browser open # Navigate (aliases: goto, navigate)\nagent-browser close # Close browser\n\n# Snapshot\nagent-browser snapshot -i # Interactive elements with refs (recommended)\nagent-browser snapshot -i -C # Include cursor-interactive elements (divs with onclick, cursor:pointer)\nagent-browser snapshot -s \"#selector\" # Scope to CSS selector\n\n# Interaction (use @refs from snapshot)\nagent-browser click @e1 # Click element\nagent-browser click @e1 --new-tab # Click and open in new tab\nagent-browser fill @e2 \"text\" # Clear and type text\nagent-browser type @e2 \"text\" # Type without clearing\nagent-browser select @e1 \"option\" # Select dropdown option\nagent-browser check @e1 # Check checkbox\nagent-browser press Enter # Press key\nagent-browser keyboard type \"text\" # Type at current focus (no selector)\nagent-browser keyboard inserttext \"text\" # Insert without key events\nagent-browser scroll down 500 # Scroll page\nagent-browser scroll down 500 --selector \"div.content\" # Scroll within a specific container\n\n# Get information\nagent-browser get text @e1 # Get element text\nagent-browser get url # Get current URL\nagent-browser get title # Get page title\n\n# Wait\nagent-browser wait @e1 # Wait for element\nagent-browser wait --load networkidle # Wait for network idle\nagent-browser wait --url \"**/page\" # Wait for URL pattern\nagent-browser wait 2000 # Wait milliseconds\n\n# Downloads\nagent-browser download @e1 ./file.pdf # Click element to trigger download\nagent-browser wait --download ./output.zip # Wait for any download to complete\nagent-browser --download-path ./downloads open # Set default download directory\n\n# Capture\nagent-browser screenshot # Screenshot to temp dir\nagent-browser screenshot --full # Full page screenshot\nagent-browser screenshot --annotate # Annotated screenshot with numbered element labels\nagent-browser pdf output.pdf # Save as PDF\n\n# Diff (compare page states)\nagent-browser diff snapshot # Compare current vs last snapshot\nagent-browser diff snapshot --baseline before.txt # Compare current vs saved file\nagent-browser diff screenshot --baseline before.png # Visual pixel diff\nagent-browser diff url # Compare two pages\nagent-browser diff url --wait-until networkidle # Custom wait strategy\nagent-browser diff url --selector \"#main\" # Scope to element\n```\n\n## Common Patterns\n\n### Form Submission\n\n```bash\nagent-browser open https://example.com/signup\nagent-browser snapshot -i\nagent-browser fill @e1 \"Jane Doe\"\nagent-browser fill @e2 \"jane@example.com\"\nagent-browser select @e3 \"California\"\nagent-browser check @e4\nagent-browser click @e5\nagent-browser wait --load networkidle\n```\n\n### Authentication with Auth Vault (Recommended)\n\n```bash\n# Save credentials once (encrypted with AGENT_BROWSER_ENCRYPTION_KEY)\n# Recommended: pipe password via stdin to avoid shell history exposure\necho \"pass\" | agent-browser auth save github --url https://github.com/login --username user --password-stdin\n\n# Login using saved profile (LLM never sees password)\nagent-browser auth login github\n\n# List/show/delete profiles\nagent-browser auth list\nagent-browser auth show github\nagent-browser auth delete github\n```\n\n### Authentication with State Persistence\n\n```bash\n# Login once and save state\nagent-browser open https://app.example.com/login\nagent-browser snapshot -i\nagent-browser fill @e1 \"$USERNAME\"\nagent-browser fill @e2 \"$PASSWORD\"\nagent-browser click @e3\nagent-browser wait --url \"**/dashboard\"\nagent-browser state save auth.json\n\n# Reuse in future sessions\nagent-browser state load auth.json\nagent-browser open https://app.example.com/dashboard\n```\n\n### Session Persistence\n\n```bash\n# Auto-save/restore cookies and localStorage across browser restarts\nagent-browser --session-name myapp open https://app.example.com/login\n# ... login flow ...\nagent-browser close # State auto-saved to ~/.agent-browser/sessions/\n\n# Next time, state is auto-loaded\nagent-browser --session-name myapp open https://app.example.com/dashboard\n\n# Encrypt state at rest\nexport AGENT_BROWSER_ENCRYPTION_KEY=$(openssl rand -hex 32)\nagent-browser --session-name secure open https://app.example.com\n\n# Manage saved states\nagent-browser state list\nagent-browser state show myapp-default.json\nagent-browser state clear myapp\nagent-browser state clean --older-than 7\n```\n\n### Data Extraction\n\n```bash\nagent-browser open https://example.com/products\nagent-browser snapshot -i\nagent-browser get text @e5 # Get specific element text\nagent-browser get text body > page.txt # Get all page text\n\n# JSON output for parsing\nagent-browser snapshot -i --json\nagent-browser get text @e1 --json\n```\n\n### Parallel Sessions\n\n```bash\nagent-browser --session site1 open https://site-a.com\nagent-browser --session site2 open https://site-b.com\n\nagent-browser --session site1 snapshot -i\nagent-browser --session site2 snapshot -i\n\nagent-browser session list\n```\n\n### Connect to Existing Chrome\n\n```bash\n# Auto-discover running Chrome with remote debugging enabled\nagent-browser --auto-connect open https://example.com\nagent-browser --auto-connect snapshot\n\n# Or with explicit CDP port\nagent-browser --cdp 9222 snapshot\n```\n\n### Color Scheme (Dark Mode)\n\n```bash\n# Persistent dark mode via flag (applies to all pages and new tabs)\nagent-browser --color-scheme dark open https://example.com\n\n# Or via environment variable\nAGENT_BROWSER_COLOR_SCHEME=dark agent-browser open https://example.com\n\n# Or set during session (persists for subsequent commands)\nagent-browser set media dark\n```\n\n### Visual Browser (Debugging)\n\n```bash\nagent-browser --headed open https://example.com\nagent-browser highlight @e1 # Highlight element\nagent-browser record start demo.webm # Record session\nagent-browser profiler start # Start Chrome DevTools profiling\nagent-browser profiler stop trace.json # Stop and save profile (path optional)\n```\n\nUse `AGENT_BROWSER_HEADED=1` to enable headed mode via environment variable. Browser extensions work in both headed and headless mode.\n\n### Local Files (PDFs, HTML)\n\n```bash\n# Open local files with file:// URLs\nagent-browser --allow-file-access open file:///path/to/document.pdf\nagent-browser --allow-file-access open file:///path/to/page.html\nagent-browser screenshot output.png\n```\n\n### iOS Simulator (Mobile Safari)\n\n```bash\n# List available iOS simulators\nagent-browser device list\n\n# Launch Safari on a specific device\nagent-browser -p ios --device \"iPhone 16 Pro\" open https://example.com\n\n# Same workflow as desktop - snapshot, interact, re-snapshot\nagent-browser -p ios snapshot -i\nagent-browser -p ios tap @e1 # Tap (alias for click)\nagent-browser -p ios fill @e2 \"text\"\nagent-browser -p ios swipe up # Mobile-specific gesture\n\n# Take screenshot\nagent-browser -p ios screenshot mobile.png\n\n# Close session (shuts down simulator)\nagent-browser -p ios close\n```\n\n**Requirements:** macOS with Xcode, Appium (`npm install -g appium && appium driver install xcuitest`)\n\n**Real devices:** Works with physical iOS devices if pre-configured. Use `--device \"\"` where UDID is from `xcrun xctrace list devices`.\n\n## Security\n\nAll security features are opt-in. By default, agent-browser imposes no restrictions on navigation, actions, or output.\n\n### Content Boundaries (Recommended for AI Agents)\n\nEnable `--content-boundaries` to wrap page-sourced output in markers that help LLMs distinguish tool output from untrusted page content:\n\n```bash\nexport AGENT_BROWSER_CONTENT_BOUNDARIES=1\nagent-browser snapshot\n# Output:\n# --- AGENT_BROWSER_PAGE_CONTENT nonce= origin=https://example.com ---\n# [accessibility tree]\n# --- END_AGENT_BROWSER_PAGE_CONTENT nonce= ---\n```\n\n### Domain Allowlist\n\nRestrict navigation to trusted domains. Wildcards like `*.example.com` also match the bare domain `example.com`. Sub-resource requests, WebSocket, and EventSource connections to non-allowed domains are also blocked. Include CDN domains your target pages depend on:\n\n```bash\nexport AGENT_BROWSER_ALLOWED_DOMAINS=\"example.com,*.example.com\"\nagent-browser open https://example.com # OK\nagent-browser open https://malicious.com # Blocked\n```\n\n### Action Policy\n\nUse a policy file to gate destructive actions:\n\n```bash\nexport AGENT_BROWSER_ACTION_POLICY=./policy.json\n```\n\nExample `policy.json`:\n\n```json\n{ \"default\": \"deny\", \"allow\": [\"navigate\", \"snapshot\", \"click\", \"scroll\", \"wait\", \"get\"] }\n```\n\nAuth vault operations (`auth login`, etc.) bypass action policy but domain allowlist still applies.\n\n### Output Limits\n\nPrevent context flooding from large pages:\n\n```bash\nexport AGENT_BROWSER_MAX_OUTPUT=50000\n```\n\n## Diffing (Verifying Changes)\n\nUse `diff snapshot` after performing an action to verify it had the intended effect. This compares the current accessibility tree against the last snapshot taken in the session.\n\n```bash\n# Typical workflow: snapshot -> action -> diff\nagent-browser snapshot -i # Take baseline snapshot\nagent-browser click @e2 # Perform action\nagent-browser diff snapshot # See what changed (auto-compares to last snapshot)\n```\n\nFor visual regression testing or monitoring:\n\n```bash\n# Save a baseline screenshot, then compare later\nagent-browser screenshot baseline.png\n# ... time passes or changes are made ...\nagent-browser diff screenshot --baseline baseline.png\n\n# Compare staging vs production\nagent-browser diff url https://staging.example.com https://prod.example.com --screenshot\n```\n\n`diff snapshot` output uses `+` for additions and `-` for removals, similar to git diff. `diff screenshot` produces a diff image with changed pixels highlighted in red, plus a mismatch percentage.\n\n## Timeouts and Slow Pages\n\nThe default Playwright timeout is 25 seconds for local browsers. This can be overridden with the `AGENT_BROWSER_DEFAULT_TIMEOUT` environment variable (value in milliseconds). For slow websites or large pages, use explicit waits instead of relying on the default timeout:\n\n```bash\n# Wait for network activity to settle (best for slow pages)\nagent-browser wait --load networkidle\n\n# Wait for a specific element to appear\nagent-browser wait \"#content\"\nagent-browser wait @e1\n\n# Wait for a specific URL pattern (useful after redirects)\nagent-browser wait --url \"**/dashboard\"\n\n# Wait for a JavaScript condition\nagent-browser wait --fn \"document.readyState === 'complete'\"\n\n# Wait a fixed duration (milliseconds) as a last resort\nagent-browser wait 5000\n```\n\nWhen dealing with consistently slow websites, use `wait --load networkidle` after `open` to ensure the page is fully loaded before taking a snapshot. If a specific element is slow to render, wait for it directly with `wait ` or `wait @ref`.\n\n## Session Management and Cleanup\n\nWhen running multiple agents or automations concurrently, always use named sessions to avoid conflicts:\n\n```bash\n# Each agent gets its own isolated session\nagent-browser --session agent1 open site-a.com\nagent-browser --session agent2 open site-b.com\n\n# Check active sessions\nagent-browser session list\n```\n\nAlways close your browser session when done to avoid leaked processes:\n\n```bash\nagent-browser close # Close default session\nagent-browser --session agent1 close # Close specific session\n```\n\nIf a previous session was not closed properly, the daemon may still be running. Use `agent-browser close` to clean it up before starting new work.\n\n## Ref Lifecycle (Important)\n\nRefs (`@e1`, `@e2`, etc.) are invalidated when the page changes. Always re-snapshot after:\n\n- Clicking links or buttons that navigate\n- Form submissions\n- Dynamic content loading (dropdowns, modals)\n\n```bash\nagent-browser click @e5 # Navigates to new page\nagent-browser snapshot -i # MUST re-snapshot\nagent-browser click @e1 # Use new refs\n```\n\n## Annotated Screenshots (Vision Mode)\n\nUse `--annotate` to take a screenshot with numbered labels overlaid on interactive elements. Each label `[N]` maps to ref `@eN`. This also caches refs, so you can interact with elements immediately without a separate snapshot.\n\n```bash\nagent-browser screenshot --annotate\n# Output includes the image path and a legend:\n# [1] @e1 button \"Submit\"\n# [2] @e2 link \"Home\"\n# [3] @e3 textbox \"Email\"\nagent-browser click @e2 # Click using ref from annotated screenshot\n```\n\nUse annotated screenshots when:\n\n- The page has unlabeled icon buttons or visual-only elements\n- You need to verify visual layout or styling\n- Canvas or chart elements are present (invisible to text snapshots)\n- You need spatial reasoning about element positions\n\n## Semantic Locators (Alternative to Refs)\n\nWhen refs are unavailable or unreliable, use semantic locators:\n\n```bash\nagent-browser find text \"Sign In\" click\nagent-browser find label \"Email\" fill \"user@test.com\"\nagent-browser find role button click --name \"Submit\"\nagent-browser find placeholder \"Search\" type \"query\"\nagent-browser find testid \"submit-btn\" click\n```\n\n## JavaScript Evaluation (eval)\n\nUse `eval` to run JavaScript in the browser context. **Shell quoting can corrupt complex expressions** -- use `--stdin` or `-b` to avoid issues.\n\n```bash\n# Simple expressions work with regular quoting\nagent-browser eval 'document.title'\nagent-browser eval 'document.querySelectorAll(\"img\").length'\n\n# Complex JS: use --stdin with heredoc (RECOMMENDED)\nagent-browser eval --stdin <<'EVALEOF'\nJSON.stringify(\n Array.from(document.querySelectorAll(\"img\"))\n .filter(i => !i.alt)\n .map(i => ({ src: i.src.split(\"/\").pop(), width: i.width }))\n)\nEVALEOF\n\n# Alternative: base64 encoding (avoids all shell escaping issues)\nagent-browser eval -b \"$(echo -n 'Array.from(document.querySelectorAll(\"a\")).map(a => a.href)' | base64)\"\n```\n\n**Why this matters:** When the shell processes your command, inner double quotes, `!` characters (history expansion), backticks, and `$()` can all corrupt the JavaScript before it reaches agent-browser. The `--stdin` and `-b` flags bypass shell interpretation entirely.\n\n**Rules of thumb:**\n\n- Single-line, no nested quotes -> regular `eval 'expression'` with single quotes is fine\n- Nested quotes, arrow functions, template literals, or multiline -> use `eval --stdin <<'EVALEOF'`\n- Programmatic/generated scripts -> use `eval -b` with base64\n\n## Configuration File\n\nCreate `agent-browser.json` in the project root for persistent settings:\n\n```json\n{\n \"headed\": true,\n \"proxy\": \"http://localhost:8080\",\n \"profile\": \"./browser-data\"\n}\n```\n\nPriority (lowest to highest): `~/.agent-browser/config.json` < `./agent-browser.json` < env vars < CLI flags. Use `--config ` or `AGENT_BROWSER_CONFIG` env var for a custom config file (exits with error if missing/invalid). All CLI options map to camelCase keys (e.g., `--executable-path` -> `\"executablePath\"`). Boolean flags accept `true`/`false` values (e.g., `--headed false` overrides config). Extensions from user and project configs are merged, not replaced.\n\n## Deep-Dive Documentation\n\n| Reference | When to Use |\n| -------------------------------------------------------------------- | --------------------------------------------------------- |\n| [references/commands.md](references/commands.md) | Full command reference with all options |\n| [references/snapshot-refs.md](references/snapshot-refs.md) | Ref lifecycle, invalidation rules, troubleshooting |\n| [references/session-management.md](references/session-management.md) | Parallel sessions, state persistence, concurrent scraping |\n| [references/authentication.md](references/authentication.md) | Login flows, OAuth, 2FA handling, state reuse |\n| [references/video-recording.md](references/video-recording.md) | Recording workflows for debugging and documentation |\n| [references/profiling.md](references/profiling.md) | Chrome DevTools profiling for performance analysis |\n| [references/proxy-support.md](references/proxy-support.md) | Proxy configuration, geo-testing, rotating proxies |\n\n## Experimental: Native Mode\n\nagent-browser has an experimental native Rust daemon that communicates with Chrome directly via CDP, bypassing Node.js and Playwright entirely. It is opt-in and not recommended for production use yet.\n\n```bash\n# Enable via flag\nagent-browser --native open example.com\n\n# Enable via environment variable (avoids passing --native every time)\nexport AGENT_BROWSER_NATIVE=1\nagent-browser open example.com\n```\n\nThe native daemon supports Chromium and Safari (via WebDriver). Firefox and WebKit are not yet supported. All core commands (navigate, snapshot, click, fill, screenshot, cookies, storage, tabs, eval, etc.) work identically in native mode. Use `agent-browser close` before switching between native and default mode within the same session.\n\n## Ready-to-Use Templates\n\n| Template | Description |\n| ------------------------------------------------------------------------ | ----------------------------------- |\n| [templates/form-automation.sh](templates/form-automation.sh) | Form filling with validation |\n| [templates/authenticated-session.sh](templates/authenticated-session.sh) | Login once, reuse state |\n| [templates/capture-workflow.sh](templates/capture-workflow.sh) | Content extraction with screenshots |\n\n```bash\n./templates/form-automation.sh https://example.com/form\n./templates/authenticated-session.sh https://app.example.com/login\n./templates/capture-workflow.sh https://example.com ./output\n```\n",".agents/skills/agent-browser/references/authentication.md":"# Authentication Patterns\n\nLogin flows, session persistence, OAuth, 2FA, and authenticated browsing.\n\n**Related**: [session-management.md](session-management.md) for state persistence details, [SKILL.md](../SKILL.md) for quick start.\n\n## Contents\n\n- [Basic Login Flow](#basic-login-flow)\n- [Saving Authentication State](#saving-authentication-state)\n- [Restoring Authentication](#restoring-authentication)\n- [OAuth / SSO Flows](#oauth--sso-flows)\n- [Two-Factor Authentication](#two-factor-authentication)\n- [HTTP Basic Auth](#http-basic-auth)\n- [Cookie-Based Auth](#cookie-based-auth)\n- [Token Refresh Handling](#token-refresh-handling)\n- [Security Best Practices](#security-best-practices)\n\n## Basic Login Flow\n\n```bash\n# Navigate to login page\nagent-browser open https://app.example.com/login\nagent-browser wait --load networkidle\n\n# Get form elements\nagent-browser snapshot -i\n# Output: @e1 [input type=\"email\"], @e2 [input type=\"password\"], @e3 [button] \"Sign In\"\n\n# Fill credentials\nagent-browser fill @e1 \"user@example.com\"\nagent-browser fill @e2 \"password123\"\n\n# Submit\nagent-browser click @e3\nagent-browser wait --load networkidle\n\n# Verify login succeeded\nagent-browser get url # Should be dashboard, not login\n```\n\n## Saving Authentication State\n\nAfter logging in, save state for reuse:\n\n```bash\n# Login first (see above)\nagent-browser open https://app.example.com/login\nagent-browser snapshot -i\nagent-browser fill @e1 \"user@example.com\"\nagent-browser fill @e2 \"password123\"\nagent-browser click @e3\nagent-browser wait --url \"**/dashboard\"\n\n# Save authenticated state\nagent-browser state save ./auth-state.json\n```\n\n## Restoring Authentication\n\nSkip login by loading saved state:\n\n```bash\n# Load saved auth state\nagent-browser state load ./auth-state.json\n\n# Navigate directly to protected page\nagent-browser open https://app.example.com/dashboard\n\n# Verify authenticated\nagent-browser snapshot -i\n```\n\n## OAuth / SSO Flows\n\nFor OAuth redirects:\n\n```bash\n# Start OAuth flow\nagent-browser open https://app.example.com/auth/google\n\n# Handle redirects automatically\nagent-browser wait --url \"**/accounts.google.com**\"\nagent-browser snapshot -i\n\n# Fill Google credentials\nagent-browser fill @e1 \"user@gmail.com\"\nagent-browser click @e2 # Next button\nagent-browser wait 2000\nagent-browser snapshot -i\nagent-browser fill @e3 \"password\"\nagent-browser click @e4 # Sign in\n\n# Wait for redirect back\nagent-browser wait --url \"**/app.example.com**\"\nagent-browser state save ./oauth-state.json\n```\n\n## Two-Factor Authentication\n\nHandle 2FA with manual intervention:\n\n```bash\n# Login with credentials\nagent-browser open https://app.example.com/login --headed # Show browser\nagent-browser snapshot -i\nagent-browser fill @e1 \"user@example.com\"\nagent-browser fill @e2 \"password123\"\nagent-browser click @e3\n\n# Wait for user to complete 2FA manually\necho \"Complete 2FA in the browser window...\"\nagent-browser wait --url \"**/dashboard\" --timeout 120000\n\n# Save state after 2FA\nagent-browser state save ./2fa-state.json\n```\n\n## HTTP Basic Auth\n\nFor sites using HTTP Basic Authentication:\n\n```bash\n# Set credentials before navigation\nagent-browser set credentials username password\n\n# Navigate to protected resource\nagent-browser open https://protected.example.com/api\n```\n\n## Cookie-Based Auth\n\nManually set authentication cookies:\n\n```bash\n# Set auth cookie\nagent-browser cookies set session_token \"abc123xyz\"\n\n# Navigate to protected page\nagent-browser open https://app.example.com/dashboard\n```\n\n## Token Refresh Handling\n\nFor sessions with expiring tokens:\n\n```bash\n#!/bin/bash\n# Wrapper that handles token refresh\n\nSTATE_FILE=\"./auth-state.json\"\n\n# Try loading existing state\nif [[ -f \"$STATE_FILE\" ]]; then\n agent-browser state load \"$STATE_FILE\"\n agent-browser open https://app.example.com/dashboard\n\n # Check if session is still valid\n URL=$(agent-browser get url)\n if [[ \"$URL\" == *\"/login\"* ]]; then\n echo \"Session expired, re-authenticating...\"\n # Perform fresh login\n agent-browser snapshot -i\n agent-browser fill @e1 \"$USERNAME\"\n agent-browser fill @e2 \"$PASSWORD\"\n agent-browser click @e3\n agent-browser wait --url \"**/dashboard\"\n agent-browser state save \"$STATE_FILE\"\n fi\nelse\n # First-time login\n agent-browser open https://app.example.com/login\n # ... login flow ...\nfi\n```\n\n## Security Best Practices\n\n1. **Never commit state files** - They contain session tokens\n\n ```bash\n echo \"*.auth-state.json\" >> .gitignore\n ```\n\n2. **Use environment variables for credentials**\n\n ```bash\n agent-browser fill @e1 \"$APP_USERNAME\"\n agent-browser fill @e2 \"$APP_PASSWORD\"\n ```\n\n3. **Clean up after automation**\n\n ```bash\n agent-browser cookies clear\n rm -f ./auth-state.json\n ```\n\n4. **Use short-lived sessions for CI/CD**\n ```bash\n # Don't persist state in CI\n agent-browser open https://app.example.com/login\n # ... login and perform actions ...\n agent-browser close # Session ends, nothing persisted\n ```\n",".agents/skills/agent-browser/references/commands.md":"# Command Reference\n\nComplete reference for all agent-browser commands. For quick start and common patterns, see SKILL.md.\n\n## Navigation\n\n```bash\nagent-browser open # Navigate to URL (aliases: goto, navigate)\n # Supports: https://, http://, file://, about:, data://\n # Auto-prepends https:// if no protocol given\nagent-browser back # Go back\nagent-browser forward # Go forward\nagent-browser reload # Reload page\nagent-browser close # Close browser (aliases: quit, exit)\nagent-browser connect 9222 # Connect to browser via CDP port\n```\n\n## Snapshot (page analysis)\n\n```bash\nagent-browser snapshot # Full accessibility tree\nagent-browser snapshot -i # Interactive elements only (recommended)\nagent-browser snapshot -c # Compact output\nagent-browser snapshot -d 3 # Limit depth to 3\nagent-browser snapshot -s \"#main\" # Scope to CSS selector\n```\n\n## Interactions (use @refs from snapshot)\n\n```bash\nagent-browser click @e1 # Click\nagent-browser click @e1 --new-tab # Click and open in new tab\nagent-browser dblclick @e1 # Double-click\nagent-browser focus @e1 # Focus element\nagent-browser fill @e2 \"text\" # Clear and type\nagent-browser type @e2 \"text\" # Type without clearing\nagent-browser press Enter # Press key (alias: key)\nagent-browser press Control+a # Key combination\nagent-browser keydown Shift # Hold key down\nagent-browser keyup Shift # Release key\nagent-browser hover @e1 # Hover\nagent-browser check @e1 # Check checkbox\nagent-browser uncheck @e1 # Uncheck checkbox\nagent-browser select @e1 \"value\" # Select dropdown option\nagent-browser select @e1 \"a\" \"b\" # Select multiple options\nagent-browser scroll down 500 # Scroll page (default: down 300px)\nagent-browser scrollintoview @e1 # Scroll element into view (alias: scrollinto)\nagent-browser drag @e1 @e2 # Drag and drop\nagent-browser upload @e1 file.pdf # Upload files\n```\n\n## Get Information\n\n```bash\nagent-browser get text @e1 # Get element text\nagent-browser get html @e1 # Get innerHTML\nagent-browser get value @e1 # Get input value\nagent-browser get attr @e1 href # Get attribute\nagent-browser get title # Get page title\nagent-browser get url # Get current URL\nagent-browser get count \".item\" # Count matching elements\nagent-browser get box @e1 # Get bounding box\nagent-browser get styles @e1 # Get computed styles (font, color, bg, etc.)\n```\n\n## Check State\n\n```bash\nagent-browser is visible @e1 # Check if visible\nagent-browser is enabled @e1 # Check if enabled\nagent-browser is checked @e1 # Check if checked\n```\n\n## Screenshots and PDF\n\n```bash\nagent-browser screenshot # Save to temporary directory\nagent-browser screenshot path.png # Save to specific path\nagent-browser screenshot --full # Full page\nagent-browser pdf output.pdf # Save as PDF\n```\n\n## Video Recording\n\n```bash\nagent-browser record start ./demo.webm # Start recording\nagent-browser click @e1 # Perform actions\nagent-browser record stop # Stop and save video\nagent-browser record restart ./take2.webm # Stop current + start new\n```\n\n## Wait\n\n```bash\nagent-browser wait @e1 # Wait for element\nagent-browser wait 2000 # Wait milliseconds\nagent-browser wait --text \"Success\" # Wait for text (or -t)\nagent-browser wait --url \"**/dashboard\" # Wait for URL pattern (or -u)\nagent-browser wait --load networkidle # Wait for network idle (or -l)\nagent-browser wait --fn \"window.ready\" # Wait for JS condition (or -f)\n```\n\n## Mouse Control\n\n```bash\nagent-browser mouse move 100 200 # Move mouse\nagent-browser mouse down left # Press button\nagent-browser mouse up left # Release button\nagent-browser mouse wheel 100 # Scroll wheel\n```\n\n## Semantic Locators (alternative to refs)\n\n```bash\nagent-browser find role button click --name \"Submit\"\nagent-browser find text \"Sign In\" click\nagent-browser find text \"Sign In\" click --exact # Exact match only\nagent-browser find label \"Email\" fill \"user@test.com\"\nagent-browser find placeholder \"Search\" type \"query\"\nagent-browser find alt \"Logo\" click\nagent-browser find title \"Close\" click\nagent-browser find testid \"submit-btn\" click\nagent-browser find first \".item\" click\nagent-browser find last \".item\" click\nagent-browser find nth 2 \"a\" hover\n```\n\n## Browser Settings\n\n```bash\nagent-browser set viewport 1920 1080 # Set viewport size\nagent-browser set device \"iPhone 14\" # Emulate device\nagent-browser set geo 37.7749 -122.4194 # Set geolocation (alias: geolocation)\nagent-browser set offline on # Toggle offline mode\nagent-browser set headers '{\"X-Key\":\"v\"}' # Extra HTTP headers\nagent-browser set credentials user pass # HTTP basic auth (alias: auth)\nagent-browser set media dark # Emulate color scheme\nagent-browser set media light reduced-motion # Light mode + reduced motion\n```\n\n## Cookies and Storage\n\n```bash\nagent-browser cookies # Get all cookies\nagent-browser cookies set name value # Set cookie\nagent-browser cookies clear # Clear cookies\nagent-browser storage local # Get all localStorage\nagent-browser storage local key # Get specific key\nagent-browser storage local set k v # Set value\nagent-browser storage local clear # Clear all\n```\n\n## Network\n\n```bash\nagent-browser network route # Intercept requests\nagent-browser network route --abort # Block requests\nagent-browser network route --body '{}' # Mock response\nagent-browser network unroute [url] # Remove routes\nagent-browser network requests # View tracked requests\nagent-browser network requests --filter api # Filter requests\n```\n\n## Tabs and Windows\n\n```bash\nagent-browser tab # List tabs\nagent-browser tab new [url] # New tab\nagent-browser tab 2 # Switch to tab by index\nagent-browser tab close # Close current tab\nagent-browser tab close 2 # Close tab by index\nagent-browser window new # New window\n```\n\n## Frames\n\n```bash\nagent-browser frame \"#iframe\" # Switch to iframe\nagent-browser frame main # Back to main frame\n```\n\n## Dialogs\n\n```bash\nagent-browser dialog accept [text] # Accept dialog\nagent-browser dialog dismiss # Dismiss dialog\n```\n\n## JavaScript\n\n```bash\nagent-browser eval \"document.title\" # Simple expressions only\nagent-browser eval -b \"\" # Any JavaScript (base64 encoded)\nagent-browser eval --stdin # Read script from stdin\n```\n\nUse `-b`/`--base64` or `--stdin` for reliable execution. Shell escaping with nested quotes and special characters is error-prone.\n\n```bash\n# Base64 encode your script, then:\nagent-browser eval -b \"ZG9jdW1lbnQucXVlcnlTZWxlY3RvcignW3NyYyo9Il9uZXh0Il0nKQ==\"\n\n# Or use stdin with heredoc for multiline scripts:\ncat <<'EOF' | agent-browser eval --stdin\nconst links = document.querySelectorAll('a');\nArray.from(links).map(a => a.href);\nEOF\n```\n\n## State Management\n\n```bash\nagent-browser state save auth.json # Save cookies, storage, auth state\nagent-browser state load auth.json # Restore saved state\n```\n\n## Global Options\n\n```bash\nagent-browser --session ... # Isolated browser session\nagent-browser --json ... # JSON output for parsing\nagent-browser --headed ... # Show browser window (not headless)\nagent-browser --full ... # Full page screenshot (-f)\nagent-browser --cdp ... # Connect via Chrome DevTools Protocol\nagent-browser -p ... # Cloud browser provider (--provider)\nagent-browser --proxy ... # Use proxy server\nagent-browser --proxy-bypass # Hosts to bypass proxy\nagent-browser --headers ... # HTTP headers scoped to URL's origin\nagent-browser --executable-path

# Custom browser executable\nagent-browser --extension ... # Load browser extension (repeatable)\nagent-browser --ignore-https-errors # Ignore SSL certificate errors\nagent-browser --help # Show help (-h)\nagent-browser --version # Show version (-V)\nagent-browser --help # Show detailed help for a command\n```\n\n## Debugging\n\n```bash\nagent-browser --headed open example.com # Show browser window\nagent-browser --cdp 9222 snapshot # Connect via CDP port\nagent-browser connect 9222 # Alternative: connect command\nagent-browser console # View console messages\nagent-browser console --clear # Clear console\nagent-browser errors # View page errors\nagent-browser errors --clear # Clear errors\nagent-browser highlight @e1 # Highlight element\nagent-browser trace start # Start recording trace\nagent-browser trace stop trace.zip # Stop and save trace\nagent-browser profiler start # Start Chrome DevTools profiling\nagent-browser profiler stop trace.json # Stop and save profile\n```\n\n## Environment Variables\n\n```bash\nAGENT_BROWSER_SESSION=\"mysession\" # Default session name\nAGENT_BROWSER_EXECUTABLE_PATH=\"/path/chrome\" # Custom browser path\nAGENT_BROWSER_EXTENSIONS=\"/ext1,/ext2\" # Comma-separated extension paths\nAGENT_BROWSER_PROVIDER=\"browserbase\" # Cloud browser provider\nAGENT_BROWSER_STREAM_PORT=\"9223\" # WebSocket streaming port\nAGENT_BROWSER_HOME=\"/path/to/agent-browser\" # Custom install location\n```\n",".agents/skills/agent-browser/references/profiling.md":"# Profiling\n\nCapture Chrome DevTools performance profiles during browser automation for performance analysis.\n\n**Related**: [commands.md](commands.md) for full command reference, [SKILL.md](../SKILL.md) for quick start.\n\n## Contents\n\n- [Basic Profiling](#basic-profiling)\n- [Profiler Commands](#profiler-commands)\n- [Categories](#categories)\n- [Use Cases](#use-cases)\n- [Output Format](#output-format)\n- [Viewing Profiles](#viewing-profiles)\n- [Limitations](#limitations)\n\n## Basic Profiling\n\n```bash\n# Start profiling\nagent-browser profiler start\n\n# Perform actions\nagent-browser navigate https://example.com\nagent-browser click \"#button\"\nagent-browser wait 1000\n\n# Stop and save\nagent-browser profiler stop ./trace.json\n```\n\n## Profiler Commands\n\n```bash\n# Start profiling with default categories\nagent-browser profiler start\n\n# Start with custom trace categories\nagent-browser profiler start --categories \"devtools.timeline,v8.execute,blink.user_timing\"\n\n# Stop profiling and save to file\nagent-browser profiler stop ./trace.json\n```\n\n## Categories\n\nThe `--categories` flag accepts a comma-separated list of Chrome trace categories. Default categories include:\n\n- `devtools.timeline` -- standard DevTools performance traces\n- `v8.execute` -- time spent running JavaScript\n- `blink` -- renderer events\n- `blink.user_timing` -- `performance.mark()` / `performance.measure()` calls\n- `latencyInfo` -- input-to-latency tracking\n- `renderer.scheduler` -- task scheduling and execution\n- `toplevel` -- broad-spectrum basic events\n\nSeveral `disabled-by-default-*` categories are also included for detailed timeline, call stack, and V8 CPU profiling data.\n\n## Use Cases\n\n### Diagnosing Slow Page Loads\n\n```bash\nagent-browser profiler start\nagent-browser navigate https://app.example.com\nagent-browser wait --load networkidle\nagent-browser profiler stop ./page-load-profile.json\n```\n\n### Profiling User Interactions\n\n```bash\nagent-browser navigate https://app.example.com\nagent-browser profiler start\nagent-browser click \"#submit\"\nagent-browser wait 2000\nagent-browser profiler stop ./interaction-profile.json\n```\n\n### CI Performance Regression Checks\n\n```bash\n#!/bin/bash\nagent-browser profiler start\nagent-browser navigate https://app.example.com\nagent-browser wait --load networkidle\nagent-browser profiler stop \"./profiles/build-${BUILD_ID}.json\"\n```\n\n## Output Format\n\nThe output is a JSON file in Chrome Trace Event format:\n\n```json\n{\n \"traceEvents\": [\n { \"cat\": \"devtools.timeline\", \"name\": \"RunTask\", \"ph\": \"X\", \"ts\": 12345, \"dur\": 100, ... },\n ...\n ],\n \"metadata\": {\n \"clock-domain\": \"LINUX_CLOCK_MONOTONIC\"\n }\n}\n```\n\nThe `metadata.clock-domain` field is set based on the host platform (Linux or macOS). On Windows it is omitted.\n\n## Viewing Profiles\n\nLoad the output JSON file in any of these tools:\n\n- **Chrome DevTools**: Performance panel > Load profile (Ctrl+Shift+I > Performance)\n- **Perfetto UI**: https://ui.perfetto.dev/ -- drag and drop the JSON file\n- **Trace Viewer**: `chrome://tracing` in any Chromium browser\n\n## Limitations\n\n- Only works with Chromium-based browsers (Chrome, Edge). Not supported on Firefox or WebKit.\n- Trace data accumulates in memory while profiling is active (capped at 5 million events). Stop profiling promptly after the area of interest.\n- Data collection on stop has a 30-second timeout. If the browser is unresponsive, the stop command may fail.\n",".agents/skills/agent-browser/references/proxy-support.md":"# Proxy Support\n\nProxy configuration for geo-testing, rate limiting avoidance, and corporate environments.\n\n**Related**: [commands.md](commands.md) for global options, [SKILL.md](../SKILL.md) for quick start.\n\n## Contents\n\n- [Basic Proxy Configuration](#basic-proxy-configuration)\n- [Authenticated Proxy](#authenticated-proxy)\n- [SOCKS Proxy](#socks-proxy)\n- [Proxy Bypass](#proxy-bypass)\n- [Common Use Cases](#common-use-cases)\n- [Verifying Proxy Connection](#verifying-proxy-connection)\n- [Troubleshooting](#troubleshooting)\n- [Best Practices](#best-practices)\n\n## Basic Proxy Configuration\n\nUse the `--proxy` flag or set proxy via environment variable:\n\n```bash\n# Via CLI flag\nagent-browser --proxy \"http://proxy.example.com:8080\" open https://example.com\n\n# Via environment variable\nexport HTTP_PROXY=\"http://proxy.example.com:8080\"\nagent-browser open https://example.com\n\n# HTTPS proxy\nexport HTTPS_PROXY=\"https://proxy.example.com:8080\"\nagent-browser open https://example.com\n\n# Both\nexport HTTP_PROXY=\"http://proxy.example.com:8080\"\nexport HTTPS_PROXY=\"http://proxy.example.com:8080\"\nagent-browser open https://example.com\n```\n\n## Authenticated Proxy\n\nFor proxies requiring authentication:\n\n```bash\n# Include credentials in URL\nexport HTTP_PROXY=\"http://username:password@proxy.example.com:8080\"\nagent-browser open https://example.com\n```\n\n## SOCKS Proxy\n\n```bash\n# SOCKS5 proxy\nexport ALL_PROXY=\"socks5://proxy.example.com:1080\"\nagent-browser open https://example.com\n\n# SOCKS5 with auth\nexport ALL_PROXY=\"socks5://user:pass@proxy.example.com:1080\"\nagent-browser open https://example.com\n```\n\n## Proxy Bypass\n\nSkip proxy for specific domains using `--proxy-bypass` or `NO_PROXY`:\n\n```bash\n# Via CLI flag\nagent-browser --proxy \"http://proxy.example.com:8080\" --proxy-bypass \"localhost,*.internal.com\" open https://example.com\n\n# Via environment variable\nexport NO_PROXY=\"localhost,127.0.0.1,.internal.company.com\"\nagent-browser open https://internal.company.com # Direct connection\nagent-browser open https://external.com # Via proxy\n```\n\n## Common Use Cases\n\n### Geo-Location Testing\n\n```bash\n#!/bin/bash\n# Test site from different regions using geo-located proxies\n\nPROXIES=(\n \"http://us-proxy.example.com:8080\"\n \"http://eu-proxy.example.com:8080\"\n \"http://asia-proxy.example.com:8080\"\n)\n\nfor proxy in \"${PROXIES[@]}\"; do\n export HTTP_PROXY=\"$proxy\"\n export HTTPS_PROXY=\"$proxy\"\n\n region=$(echo \"$proxy\" | grep -oP '^\\w+-\\w+')\n echo \"Testing from: $region\"\n\n agent-browser --session \"$region\" open https://example.com\n agent-browser --session \"$region\" screenshot \"./screenshots/$region.png\"\n agent-browser --session \"$region\" close\ndone\n```\n\n### Rotating Proxies for Scraping\n\n```bash\n#!/bin/bash\n# Rotate through proxy list to avoid rate limiting\n\nPROXY_LIST=(\n \"http://proxy1.example.com:8080\"\n \"http://proxy2.example.com:8080\"\n \"http://proxy3.example.com:8080\"\n)\n\nURLS=(\n \"https://site.com/page1\"\n \"https://site.com/page2\"\n \"https://site.com/page3\"\n)\n\nfor i in \"${!URLS[@]}\"; do\n proxy_index=$((i % ${#PROXY_LIST[@]}))\n export HTTP_PROXY=\"${PROXY_LIST[$proxy_index]}\"\n export HTTPS_PROXY=\"${PROXY_LIST[$proxy_index]}\"\n\n agent-browser open \"${URLS[$i]}\"\n agent-browser get text body > \"output-$i.txt\"\n agent-browser close\n\n sleep 1 # Polite delay\ndone\n```\n\n### Corporate Network Access\n\n```bash\n#!/bin/bash\n# Access internal sites via corporate proxy\n\nexport HTTP_PROXY=\"http://corpproxy.company.com:8080\"\nexport HTTPS_PROXY=\"http://corpproxy.company.com:8080\"\nexport NO_PROXY=\"localhost,127.0.0.1,.company.com\"\n\n# External sites go through proxy\nagent-browser open https://external-vendor.com\n\n# Internal sites bypass proxy\nagent-browser open https://intranet.company.com\n```\n\n## Verifying Proxy Connection\n\n```bash\n# Check your apparent IP\nagent-browser open https://httpbin.org/ip\nagent-browser get text body\n# Should show proxy's IP, not your real IP\n```\n\n## Troubleshooting\n\n### Proxy Connection Failed\n\n```bash\n# Test proxy connectivity first\ncurl -x http://proxy.example.com:8080 https://httpbin.org/ip\n\n# Check if proxy requires auth\nexport HTTP_PROXY=\"http://user:pass@proxy.example.com:8080\"\n```\n\n### SSL/TLS Errors Through Proxy\n\nSome proxies perform SSL inspection. If you encounter certificate errors:\n\n```bash\n# For testing only - not recommended for production\nagent-browser open https://example.com --ignore-https-errors\n```\n\n### Slow Performance\n\n```bash\n# Use proxy only when necessary\nexport NO_PROXY=\"*.cdn.com,*.static.com\" # Direct CDN access\n```\n\n## Best Practices\n\n1. **Use environment variables** - Don't hardcode proxy credentials\n2. **Set NO_PROXY appropriately** - Avoid routing local traffic through proxy\n3. **Test proxy before automation** - Verify connectivity with simple requests\n4. **Handle proxy failures gracefully** - Implement retry logic for unstable proxies\n5. **Rotate proxies for large scraping jobs** - Distribute load and avoid bans\n",".agents/skills/agent-browser/references/session-management.md":"# Session Management\n\nMultiple isolated browser sessions with state persistence and concurrent browsing.\n\n**Related**: [authentication.md](authentication.md) for login patterns, [SKILL.md](../SKILL.md) for quick start.\n\n## Contents\n\n- [Named Sessions](#named-sessions)\n- [Session Isolation Properties](#session-isolation-properties)\n- [Session State Persistence](#session-state-persistence)\n- [Common Patterns](#common-patterns)\n- [Default Session](#default-session)\n- [Session Cleanup](#session-cleanup)\n- [Best Practices](#best-practices)\n\n## Named Sessions\n\nUse `--session` flag to isolate browser contexts:\n\n```bash\n# Session 1: Authentication flow\nagent-browser --session auth open https://app.example.com/login\n\n# Session 2: Public browsing (separate cookies, storage)\nagent-browser --session public open https://example.com\n\n# Commands are isolated by session\nagent-browser --session auth fill @e1 \"user@example.com\"\nagent-browser --session public get text body\n```\n\n## Session Isolation Properties\n\nEach session has independent:\n\n- Cookies\n- LocalStorage / SessionStorage\n- IndexedDB\n- Cache\n- Browsing history\n- Open tabs\n\n## Session State Persistence\n\n### Save Session State\n\n```bash\n# Save cookies, storage, and auth state\nagent-browser state save /path/to/auth-state.json\n```\n\n### Load Session State\n\n```bash\n# Restore saved state\nagent-browser state load /path/to/auth-state.json\n\n# Continue with authenticated session\nagent-browser open https://app.example.com/dashboard\n```\n\n### State File Contents\n\n```json\n{\n \"cookies\": [...],\n \"localStorage\": {...},\n \"sessionStorage\": {...},\n \"origins\": [...]\n}\n```\n\n## Common Patterns\n\n### Authenticated Session Reuse\n\n```bash\n#!/bin/bash\n# Save login state once, reuse many times\n\nSTATE_FILE=\"/tmp/auth-state.json\"\n\n# Check if we have saved state\nif [[ -f \"$STATE_FILE\" ]]; then\n agent-browser state load \"$STATE_FILE\"\n agent-browser open https://app.example.com/dashboard\nelse\n # Perform login\n agent-browser open https://app.example.com/login\n agent-browser snapshot -i\n agent-browser fill @e1 \"$USERNAME\"\n agent-browser fill @e2 \"$PASSWORD\"\n agent-browser click @e3\n agent-browser wait --load networkidle\n\n # Save for future use\n agent-browser state save \"$STATE_FILE\"\nfi\n```\n\n### Concurrent Scraping\n\n```bash\n#!/bin/bash\n# Scrape multiple sites concurrently\n\n# Start all sessions\nagent-browser --session site1 open https://site1.com &\nagent-browser --session site2 open https://site2.com &\nagent-browser --session site3 open https://site3.com &\nwait\n\n# Extract from each\nagent-browser --session site1 get text body > site1.txt\nagent-browser --session site2 get text body > site2.txt\nagent-browser --session site3 get text body > site3.txt\n\n# Cleanup\nagent-browser --session site1 close\nagent-browser --session site2 close\nagent-browser --session site3 close\n```\n\n### A/B Testing Sessions\n\n```bash\n# Test different user experiences\nagent-browser --session variant-a open \"https://app.com?variant=a\"\nagent-browser --session variant-b open \"https://app.com?variant=b\"\n\n# Compare\nagent-browser --session variant-a screenshot /tmp/variant-a.png\nagent-browser --session variant-b screenshot /tmp/variant-b.png\n```\n\n## Default Session\n\nWhen `--session` is omitted, commands use the default session:\n\n```bash\n# These use the same default session\nagent-browser open https://example.com\nagent-browser snapshot -i\nagent-browser close # Closes default session\n```\n\n## Session Cleanup\n\n```bash\n# Close specific session\nagent-browser --session auth close\n\n# List active sessions\nagent-browser session list\n```\n\n## Best Practices\n\n### 1. Name Sessions Semantically\n\n```bash\n# GOOD: Clear purpose\nagent-browser --session github-auth open https://github.com\nagent-browser --session docs-scrape open https://docs.example.com\n\n# AVOID: Generic names\nagent-browser --session s1 open https://github.com\n```\n\n### 2. Always Clean Up\n\n```bash\n# Close sessions when done\nagent-browser --session auth close\nagent-browser --session scrape close\n```\n\n### 3. Handle State Files Securely\n\n```bash\n# Don't commit state files (contain auth tokens!)\necho \"*.auth-state.json\" >> .gitignore\n\n# Delete after use\nrm /tmp/auth-state.json\n```\n\n### 4. Timeout Long Sessions\n\n```bash\n# Set timeout for automated scripts\ntimeout 60 agent-browser --session long-task get text body\n```\n",".agents/skills/agent-browser/references/snapshot-refs.md":"# Snapshot and Refs\n\nCompact element references that reduce context usage dramatically for AI agents.\n\n**Related**: [commands.md](commands.md) for full command reference, [SKILL.md](../SKILL.md) for quick start.\n\n## Contents\n\n- [How Refs Work](#how-refs-work)\n- [Snapshot Command](#the-snapshot-command)\n- [Using Refs](#using-refs)\n- [Ref Lifecycle](#ref-lifecycle)\n- [Best Practices](#best-practices)\n- [Ref Notation Details](#ref-notation-details)\n- [Troubleshooting](#troubleshooting)\n\n## How Refs Work\n\nTraditional approach:\n\n```\nFull DOM/HTML → AI parses → CSS selector → Action (~3000-5000 tokens)\n```\n\nagent-browser approach:\n\n```\nCompact snapshot → @refs assigned → Direct interaction (~200-400 tokens)\n```\n\n## The Snapshot Command\n\n```bash\n# Basic snapshot (shows page structure)\nagent-browser snapshot\n\n# Interactive snapshot (-i flag) - RECOMMENDED\nagent-browser snapshot -i\n```\n\n### Snapshot Output Format\n\n```\nPage: Example Site - Home\nURL: https://example.com\n\n@e1 [header]\n @e2 [nav]\n @e3 [a] \"Home\"\n @e4 [a] \"Products\"\n @e5 [a] \"About\"\n @e6 [button] \"Sign In\"\n\n@e7 [main]\n @e8 [h1] \"Welcome\"\n @e9 [form]\n @e10 [input type=\"email\"] placeholder=\"Email\"\n @e11 [input type=\"password\"] placeholder=\"Password\"\n @e12 [button type=\"submit\"] \"Log In\"\n\n@e13 [footer]\n @e14 [a] \"Privacy Policy\"\n```\n\n## Using Refs\n\nOnce you have refs, interact directly:\n\n```bash\n# Click the \"Sign In\" button\nagent-browser click @e6\n\n# Fill email input\nagent-browser fill @e10 \"user@example.com\"\n\n# Fill password\nagent-browser fill @e11 \"password123\"\n\n# Submit the form\nagent-browser click @e12\n```\n\n## Ref Lifecycle\n\n**IMPORTANT**: Refs are invalidated when the page changes!\n\n```bash\n# Get initial snapshot\nagent-browser snapshot -i\n# @e1 [button] \"Next\"\n\n# Click triggers page change\nagent-browser click @e1\n\n# MUST re-snapshot to get new refs!\nagent-browser snapshot -i\n# @e1 [h1] \"Page 2\" ← Different element now!\n```\n\n## Best Practices\n\n### 1. Always Snapshot Before Interacting\n\n```bash\n# CORRECT\nagent-browser open https://example.com\nagent-browser snapshot -i # Get refs first\nagent-browser click @e1 # Use ref\n\n# WRONG\nagent-browser open https://example.com\nagent-browser click @e1 # Ref doesn't exist yet!\n```\n\n### 2. Re-Snapshot After Navigation\n\n```bash\nagent-browser click @e5 # Navigates to new page\nagent-browser snapshot -i # Get new refs\nagent-browser click @e1 # Use new refs\n```\n\n### 3. Re-Snapshot After Dynamic Changes\n\n```bash\nagent-browser click @e1 # Opens dropdown\nagent-browser snapshot -i # See dropdown items\nagent-browser click @e7 # Select item\n```\n\n### 4. Snapshot Specific Regions\n\nFor complex pages, snapshot specific areas:\n\n```bash\n# Snapshot just the form\nagent-browser snapshot @e9\n```\n\n## Ref Notation Details\n\n```\n@e1 [tag type=\"value\"] \"text content\" placeholder=\"hint\"\n│ │ │ │ │\n│ │ │ │ └─ Additional attributes\n│ │ │ └─ Visible text\n│ │ └─ Key attributes shown\n│ └─ HTML tag name\n└─ Unique ref ID\n```\n\n### Common Patterns\n\n```\n@e1 [button] \"Submit\" # Button with text\n@e2 [input type=\"email\"] # Email input\n@e3 [input type=\"password\"] # Password input\n@e4 [a href=\"/page\"] \"Link Text\" # Anchor link\n@e5 [select] # Dropdown\n@e6 [textarea] placeholder=\"Message\" # Text area\n@e7 [div class=\"modal\"] # Container (when relevant)\n@e8 [img alt=\"Logo\"] # Image\n@e9 [checkbox] checked # Checked checkbox\n@e10 [radio] selected # Selected radio\n```\n\n## Troubleshooting\n\n### \"Ref not found\" Error\n\n```bash\n# Ref may have changed - re-snapshot\nagent-browser snapshot -i\n```\n\n### Element Not Visible in Snapshot\n\n```bash\n# Scroll down to reveal element\nagent-browser scroll down 1000\nagent-browser snapshot -i\n\n# Or wait for dynamic content\nagent-browser wait 1000\nagent-browser snapshot -i\n```\n\n### Too Many Elements\n\n```bash\n# Snapshot specific container\nagent-browser snapshot @e5\n\n# Or use get text for content-only extraction\nagent-browser get text @e5\n```\n",".agents/skills/agent-browser/references/video-recording.md":"# Video Recording\n\nCapture browser automation as video for debugging, documentation, or verification.\n\n**Related**: [commands.md](commands.md) for full command reference, [SKILL.md](../SKILL.md) for quick start.\n\n## Contents\n\n- [Basic Recording](#basic-recording)\n- [Recording Commands](#recording-commands)\n- [Use Cases](#use-cases)\n- [Best Practices](#best-practices)\n- [Output Format](#output-format)\n- [Limitations](#limitations)\n\n## Basic Recording\n\n```bash\n# Start recording\nagent-browser record start ./demo.webm\n\n# Perform actions\nagent-browser open https://example.com\nagent-browser snapshot -i\nagent-browser click @e1\nagent-browser fill @e2 \"test input\"\n\n# Stop and save\nagent-browser record stop\n```\n\n## Recording Commands\n\n```bash\n# Start recording to file\nagent-browser record start ./output.webm\n\n# Stop current recording\nagent-browser record stop\n\n# Restart with new file (stops current + starts new)\nagent-browser record restart ./take2.webm\n```\n\n## Use Cases\n\n### Debugging Failed Automation\n\n```bash\n#!/bin/bash\n# Record automation for debugging\n\nagent-browser record start ./debug-$(date +%Y%m%d-%H%M%S).webm\n\n# Run your automation\nagent-browser open https://app.example.com\nagent-browser snapshot -i\nagent-browser click @e1 || {\n echo \"Click failed - check recording\"\n agent-browser record stop\n exit 1\n}\n\nagent-browser record stop\n```\n\n### Documentation Generation\n\n```bash\n#!/bin/bash\n# Record workflow for documentation\n\nagent-browser record start ./docs/how-to-login.webm\n\nagent-browser open https://app.example.com/login\nagent-browser wait 1000 # Pause for visibility\n\nagent-browser snapshot -i\nagent-browser fill @e1 \"demo@example.com\"\nagent-browser wait 500\n\nagent-browser fill @e2 \"password\"\nagent-browser wait 500\n\nagent-browser click @e3\nagent-browser wait --load networkidle\nagent-browser wait 1000 # Show result\n\nagent-browser record stop\n```\n\n### CI/CD Test Evidence\n\n```bash\n#!/bin/bash\n# Record E2E test runs for CI artifacts\n\nTEST_NAME=\"${1:-e2e-test}\"\nRECORDING_DIR=\"./test-recordings\"\nmkdir -p \"$RECORDING_DIR\"\n\nagent-browser record start \"$RECORDING_DIR/$TEST_NAME-$(date +%s).webm\"\n\n# Run test\nif run_e2e_test; then\n echo \"Test passed\"\nelse\n echo \"Test failed - recording saved\"\nfi\n\nagent-browser record stop\n```\n\n## Best Practices\n\n### 1. Add Pauses for Clarity\n\n```bash\n# Slow down for human viewing\nagent-browser click @e1\nagent-browser wait 500 # Let viewer see result\n```\n\n### 2. Use Descriptive Filenames\n\n```bash\n# Include context in filename\nagent-browser record start ./recordings/login-flow-2024-01-15.webm\nagent-browser record start ./recordings/checkout-test-run-42.webm\n```\n\n### 3. Handle Recording in Error Cases\n\n```bash\n#!/bin/bash\nset -e\n\ncleanup() {\n agent-browser record stop 2>/dev/null || true\n agent-browser close 2>/dev/null || true\n}\ntrap cleanup EXIT\n\nagent-browser record start ./automation.webm\n# ... automation steps ...\n```\n\n### 4. Combine with Screenshots\n\n```bash\n# Record video AND capture key frames\nagent-browser record start ./flow.webm\n\nagent-browser open https://example.com\nagent-browser screenshot ./screenshots/step1-homepage.png\n\nagent-browser click @e1\nagent-browser screenshot ./screenshots/step2-after-click.png\n\nagent-browser record stop\n```\n\n## Output Format\n\n- Default format: WebM (VP8/VP9 codec)\n- Compatible with all modern browsers and video players\n- Compressed but high quality\n\n## Limitations\n\n- Recording adds slight overhead to automation\n- Large recordings can consume significant disk space\n- Some headless environments may have codec limitations\n",".agents/skills/ai-sdk/SKILL.md":"---\nname: ai-sdk\ndescription: 'Answer questions about the AI SDK and help build AI-powered features. Use when developers: (1) Ask about AI SDK functions like generateText, streamText, ToolLoopAgent, embed, or tools, (2) Want to build AI agents, chatbots, RAG systems, or text generation features, (3) Have questions about AI providers (OpenAI, Anthropic, Google, etc.), streaming, tool calling, structured output, or embeddings, (4) Use React hooks like useChat or useCompletion. Triggers on: \"AI SDK\", \"Vercel AI SDK\", \"generateText\", \"streamText\", \"add AI to my app\", \"build an agent\", \"tool calling\", \"structured output\", \"useChat\".'\n---\n\n## Prerequisites\n\nBefore searching docs, check if `node_modules/ai/docs/` exists. If not, install **only** the `ai` package using the project's package manager (e.g., `pnpm add ai`).\n\nDo not install other packages at this stage. Provider packages (e.g., `@ai-sdk/openai`) and client packages (e.g., `@ai-sdk/react`) should be installed later when needed based on user requirements.\n\n## Critical: Do Not Trust Internal Knowledge\n\nEverything you know about the AI SDK is outdated or wrong. Your training data contains obsolete APIs, deprecated patterns, and incorrect usage.\n\n**When working with the AI SDK:**\n\n1. Ensure `ai` package is installed (see Prerequisites)\n2. Search `node_modules/ai/docs/` and `node_modules/ai/src/` for current APIs\n3. If not found locally, search ai-sdk.dev documentation (instructions below)\n4. Never rely on memory - always verify against source code or docs\n5. **`useChat` has changed significantly** - check [Common Errors](references/common-errors.md) before writing client code\n6. When deciding which model and provider to use (e.g. OpenAI, Anthropic, Gemini), use the Vercel AI Gateway provider unless the user specifies otherwise. See [AI Gateway Reference](references/ai-gateway.md) for usage details.\n7. **Always fetch current model IDs** - Never use model IDs from memory. Before writing code that uses a model, run `curl -s https://ai-gateway.vercel.sh/v1/models | jq -r '[.data[] | select(.id | startswith(\"provider/\")) | .id] | reverse | .[]'` (replacing `provider` with the relevant provider like `anthropic`, `openai`, or `google`) to get the full list with newest models first. Use the model with the highest version number (e.g., `claude-sonnet-4-5` over `claude-sonnet-4` over `claude-3-5-sonnet`).\n8. Run typecheck after changes to ensure code is correct\n9. **Be minimal** - Only specify options that differ from defaults. When unsure of defaults, check docs or source rather than guessing or over-specifying.\n\nIf you cannot find documentation to support your answer, state that explicitly.\n\n## Finding Documentation\n\n### ai@6.0.34+\n\nSearch bundled docs and source in `node_modules/ai/`:\n\n- **Docs**: `grep \"query\" node_modules/ai/docs/`\n- **Source**: `grep \"query\" node_modules/ai/src/`\n\nProvider packages include docs at `node_modules/@ai-sdk//docs/`.\n\n### Earlier versions\n\n1. Search: `https://ai-sdk.dev/api/search-docs?q=your_query`\n2. Fetch `.md` URLs from results (e.g., `https://ai-sdk.dev/docs/agents/building-agents.md`)\n\n## When Typecheck Fails\n\n**Before searching source code**, grep [Common Errors](references/common-errors.md) for the failing property or function name. Many type errors are caused by deprecated APIs documented there.\n\nIf not found in common-errors.md:\n\n1. Search `node_modules/ai/src/` and `node_modules/ai/docs/`\n2. Search ai-sdk.dev (for earlier versions or if not found locally)\n\n## Building and Consuming Agents\n\n### Creating Agents\n\nAlways use the `ToolLoopAgent` pattern. Search `node_modules/ai/docs/` for current agent creation APIs.\n\n**File conventions**: See [type-safe-agents.md](references/type-safe-agents.md) for where to save agents and tools.\n\n**Type Safety**: When consuming agents with `useChat`, always use `InferAgentUIMessage` for type-safe tool results. See [reference](references/type-safe-agents.md).\n\n### Consuming Agents (Framework-Specific)\n\nBefore implementing agent consumption:\n\n1. Check `package.json` to detect the project's framework/stack\n2. Search documentation for the framework's quickstart guide\n3. Follow the framework-specific patterns for streaming, API routes, and client integration\n\n## References\n\n- [Common Errors](references/common-errors.md) - Renamed parameters reference (parameters → inputSchema, etc.)\n- [AI Gateway](references/ai-gateway.md) - Gateway setup and usage\n- [Type-Safe Agents with useChat](references/type-safe-agents.md) - End-to-end type safety with InferAgentUIMessage\n- [DevTools](references/devtools.md) - Set up local debugging and observability (development only)\n",".agents/skills/ai-sdk/references/ai-gateway.md":"---\ntitle: Vercel AI Gateway\ndescription: Reference for using Vercel AI Gateway with the AI SDK.\n---\n\n# Vercel AI Gateway\n\nThe Vercel AI Gateway is the fastest way to get started with the AI SDK. It provides access to models from OpenAI, Anthropic, Google, and other providers through a single API.\n\n## Authentication\n\nAuthenticate with OIDC (for Vercel deployments) or an [AI Gateway API key](https://vercel.com/d?to=%2F%5Bteam%5D%2F%7E%2Fai-gateway%2Fapi-keys&title=AI+Gateway+API+Keys):\n\n```env filename=\".env.local\"\nAI_GATEWAY_API_KEY=your_api_key_here\n```\n\n## Usage\n\nThe AI Gateway is the default global provider, so you can access models using a simple string:\n\n```ts\nimport { generateText } from 'ai'\n\nconst { text } = await generateText({\n model: 'anthropic/claude-sonnet-4.5',\n prompt: 'What is love?',\n})\n```\n\nYou can also explicitly import and use the gateway provider:\n\n```ts\n// Option 1: Import from 'ai' package (included by default)\nimport { gateway } from 'ai'\nmodel: gateway('anthropic/claude-sonnet-4.5')\n\n// Option 2: Install and import from '@ai-sdk/gateway' package\nimport { gateway } from '@ai-sdk/gateway'\nmodel: gateway('anthropic/claude-sonnet-4.5')\n```\n\n## Find Available Models\n\n**Important**: Always fetch the current model list before writing code. Never use model IDs from memory - they may be outdated.\n\nList all available models through the gateway API:\n\n```bash\ncurl https://ai-gateway.vercel.sh/v1/models\n```\n\nFilter by provider using `jq`. **Do not truncate with `head`** - always fetch the full list to find the latest models:\n\n```bash\n# Anthropic models\ncurl -s https://ai-gateway.vercel.sh/v1/models | jq -r '[.data[] | select(.id | startswith(\"anthropic/\")) | .id] | reverse | .[]'\n\n# OpenAI models\ncurl -s https://ai-gateway.vercel.sh/v1/models | jq -r '[.data[] | select(.id | startswith(\"openai/\")) | .id] | reverse | .[]'\n\n# Google models\ncurl -s https://ai-gateway.vercel.sh/v1/models | jq -r '[.data[] | select(.id | startswith(\"google/\")) | .id] | reverse | .[]'\n```\n\nWhen multiple versions of a model exist, use the one with the highest version number (e.g., prefer `claude-sonnet-4-5` over `claude-sonnet-4` over `claude-3-5-sonnet`).\n",".agents/skills/ai-sdk/references/common-errors.md":"---\ntitle: Common Errors\ndescription: Reference for common AI SDK errors and how to resolve them.\n---\n\n# Common Errors\n\n## `maxTokens` → `maxOutputTokens`\n\n```typescript\n// ❌ Incorrect\nconst result = await generateText({\n model: 'anthropic/claude-opus-4.5',\n maxTokens: 512, // deprecated: use `maxOutputTokens` instead\n prompt: 'Write a short story',\n})\n\n// ✅ Correct\nconst result = await generateText({\n model: 'anthropic/claude-opus-4.5',\n maxOutputTokens: 512,\n prompt: 'Write a short story',\n})\n```\n\n## `maxSteps` → `stopWhen: stepCountIs(n)`\n\n```typescript\n// ❌ Incorrect\nconst result = await generateText({\n model: 'anthropic/claude-opus-4.5',\n tools: { weather },\n maxSteps: 5, // deprecated: use `stopWhen: stepCountIs(n)` instead\n prompt: 'What is the weather in NYC?',\n})\n\n// ✅ Correct\nimport { generateText, stepCountIs } from 'ai'\n\nconst result = await generateText({\n model: 'anthropic/claude-opus-4.5',\n tools: { weather },\n stopWhen: stepCountIs(5),\n prompt: 'What is the weather in NYC?',\n})\n```\n\n## `parameters` → `inputSchema` (in tool definition)\n\n```typescript\n// ❌ Incorrect\nconst weatherTool = tool({\n description: 'Get weather for a location',\n parameters: z.object({\n // deprecated: use `inputSchema` instead\n location: z.string(),\n }),\n execute: async ({ location }) => ({ location, temp: 72 }),\n})\n\n// ✅ Correct\nconst weatherTool = tool({\n description: 'Get weather for a location',\n inputSchema: z.object({\n location: z.string(),\n }),\n execute: async ({ location }) => ({ location, temp: 72 }),\n})\n```\n\n## `generateObject` → `generateText` with `output`\n\n`generateObject` is deprecated. Use `generateText` with the `output` option instead.\n\n```typescript\n// ❌ Deprecated\nimport { generateObject } from 'ai' // deprecated: use `generateText` with `output` instead\n\nconst result = await generateObject({\n // deprecated function\n model: 'anthropic/claude-opus-4.5',\n schema: z.object({\n // deprecated: use `Output.object({ schema })` instead\n recipe: z.object({\n name: z.string(),\n ingredients: z.array(z.string()),\n }),\n }),\n prompt: 'Generate a recipe for chocolate cake',\n})\n\n// ✅ Correct\nimport { generateText, Output } from 'ai'\n\nconst result = await generateText({\n model: 'anthropic/claude-opus-4.5',\n output: Output.object({\n schema: z.object({\n recipe: z.object({\n name: z.string(),\n ingredients: z.array(z.string()),\n }),\n }),\n }),\n prompt: 'Generate a recipe for chocolate cake',\n})\n\nconsole.log(result.output) // typed object\n```\n\n## Manual JSON parsing → `generateText` with `output`\n\n```typescript\n// ❌ Incorrect\nconst result = await generateText({\n model: 'anthropic/claude-opus-4.5',\n prompt: `Extract the user info as JSON: { \"name\": string, \"age\": number }\n\n Input: John is 25 years old`,\n})\nconst parsed = JSON.parse(result.text)\n\n// ✅ Correct\nimport { generateText, Output } from 'ai'\n\nconst result = await generateText({\n model: 'anthropic/claude-opus-4.5',\n output: Output.object({\n schema: z.object({\n name: z.string(),\n age: z.number(),\n }),\n }),\n prompt: 'Extract the user info: John is 25 years old',\n})\n\nconsole.log(result.output) // { name: 'John', age: 25 }\n```\n\n## Other `output` options\n\n```typescript\n// Output.array - for generating arrays of items\nconst result = await generateText({\n model: 'anthropic/claude-opus-4.5',\n output: Output.array({\n element: z.object({\n city: z.string(),\n country: z.string(),\n }),\n }),\n prompt: 'List 5 capital cities',\n})\n\n// Output.choice - for selecting from predefined options\nconst result = await generateText({\n model: 'anthropic/claude-opus-4.5',\n output: Output.choice({\n options: ['positive', 'negative', 'neutral'] as const,\n }),\n prompt: 'Classify the sentiment: I love this product!',\n})\n\n// Output.json - for untyped JSON output\nconst result = await generateText({\n model: 'anthropic/claude-opus-4.5',\n output: Output.json(),\n prompt: 'Return some JSON data',\n})\n```\n\n## `toDataStreamResponse` → `toUIMessageStreamResponse`\n\nWhen using `useChat` on the frontend, use `toUIMessageStreamResponse()` instead of `toDataStreamResponse()`. The UI message stream format is designed to work with the chat UI components and handles message state correctly.\n\n```typescript\n// ❌ Incorrect (when using useChat)\nconst result = streamText({\n // config\n})\n\nreturn result.toDataStreamResponse() // deprecated for useChat: use toUIMessageStreamResponse\n\n// ✅ Correct\nconst result = streamText({\n // config\n})\n\nreturn result.toUIMessageStreamResponse()\n```\n\n## Removed managed input state in `useChat`\n\nThe `useChat` hook no longer manages input state internally. You must now manage input state manually.\n\n```tsx\n// ❌ Deprecated\nimport { useChat } from '@ai-sdk/react'\n\nexport default function Page() {\n const {\n input, // deprecated: manage input state manually with useState\n handleInputChange, // deprecated: use custom onChange handler\n handleSubmit, // deprecated: use sendMessage() instead\n } = useChat({\n api: '/api/chat', // deprecated: use `transport: new DefaultChatTransport({ api })` instead\n })\n\n return (\n

\n \n \n
\n )\n}\n\n// ✅ Correct\nimport { useChat } from '@ai-sdk/react'\nimport { DefaultChatTransport } from 'ai'\nimport { useState } from 'react'\n\nexport default function Page() {\n const [input, setInput] = useState('')\n const { sendMessage } = useChat({\n transport: new DefaultChatTransport({ api: '/api/chat' }),\n })\n\n const handleSubmit = (e) => {\n e.preventDefault()\n sendMessage({ text: input })\n setInput('')\n }\n\n return (\n
\n setInput(e.target.value)} />\n \n
\n )\n}\n```\n\n## `tool-invocation` → `tool-{toolName}` (typed tool parts)\n\nWhen rendering messages with `useChat`, use the typed tool part names (`tool-{toolName}`) instead of the generic `tool-invocation` type. This provides better type safety and access to tool-specific input/output types.\n\n> For end-to-end type-safety, see [Type-Safe Agents](type-safe-agents.md).\n\nTyped tool parts also use different property names:\n\n- `part.args` → `part.input`\n- `part.result` → `part.output`\n\n```tsx\n// ❌ Incorrect - using generic tool-invocation\n{\n message.parts.map((part, i) => {\n switch (part.type) {\n case 'text':\n return
{part.text}
\n case 'tool-invocation': // deprecated: use typed tool parts instead\n return 
{JSON.stringify(part.toolInvocation, null, 2)}
\n }\n })\n}\n\n// ✅ Correct - using typed tool parts (recommended)\n{\n message.parts.map((part) => {\n switch (part.type) {\n case 'text':\n return part.text\n case 'tool-askForConfirmation':\n // handle askForConfirmation tool\n break\n case 'tool-getWeatherInformation':\n // handle getWeatherInformation tool\n break\n }\n })\n}\n\n// ✅ Alternative - using isToolUIPart as a catch-all\nimport { isToolUIPart } from 'ai'\n\n{\n message.parts.map((part) => {\n if (part.type === 'text') {\n return part.text\n }\n if (isToolUIPart(part)) {\n // handle any tool part generically\n return (\n
\n {part.toolName}: {part.state}\n
\n )\n }\n })\n}\n```\n\n## `useChat` state-dependent property access\n\nTool part properties are only available in certain states. TypeScript will error if you access them without checking state first.\n\n```tsx\n// ❌ Incorrect - input may be undefined during streaming\n// TS18048: 'part.input' is possibly 'undefined'\nif (part.type === 'tool-getWeather') {\n const location = part.input.location\n}\n\n// ✅ Correct - check for input-available or output-available\nif (part.type === 'tool-getWeather' && (part.state === 'input-available' || part.state === 'output-available')) {\n const location = part.input.location\n}\n\n// ❌ Incorrect - output is only available after execution\n// TS18048: 'part.output' is possibly 'undefined'\nif (part.type === 'tool-getWeather') {\n const weather = part.output\n}\n\n// ✅ Correct - check for output-available\nif (part.type === 'tool-getWeather' && part.state === 'output-available') {\n const location = part.input.location\n const weather = part.output\n}\n```\n\n## `part.toolInvocation.args` → `part.input`\n\n```tsx\n// ❌ Incorrect\nif (part.type === 'tool-invocation') {\n // deprecated: use `part.input` on typed tool parts instead\n const location = part.toolInvocation.args.location\n}\n\n// ✅ Correct\nif (part.type === 'tool-getWeather' && (part.state === 'input-available' || part.state === 'output-available')) {\n const location = part.input.location\n}\n```\n\n## `part.toolInvocation.result` → `part.output`\n\n```tsx\n// ❌ Incorrect\nif (part.type === 'tool-invocation') {\n // deprecated: use `part.output` on typed tool parts instead\n const weather = part.toolInvocation.result\n}\n\n// ✅ Correct\nif (part.type === 'tool-getWeather' && part.state === 'output-available') {\n const weather = part.output\n}\n```\n\n## `part.toolInvocation.toolCallId` → `part.toolCallId`\n\n```tsx\n// ❌ Incorrect\nif (part.type === 'tool-invocation') {\n // deprecated: use `part.toolCallId` on typed tool parts instead\n const id = part.toolInvocation.toolCallId\n}\n\n// ✅ Correct\nif (part.type === 'tool-getWeather') {\n const id = part.toolCallId\n}\n```\n\n## Tool invocation states renamed\n\n```tsx\n// ❌ Incorrect\nswitch (part.toolInvocation.state) {\n case 'partial-call': // deprecated: use `input-streaming` instead\n return
Loading...
\n case 'call': // deprecated: use `input-available` instead\n return
Executing...
\n case 'result': // deprecated: use `output-available` instead\n return
Done
\n}\n\n// ✅ Correct\nswitch (part.state) {\n case 'input-streaming':\n return
Loading...
\n case 'input-available':\n return
Executing...
\n case 'output-available':\n return
Done
\n}\n```\n\n## `addToolResult` → `addToolOutput`\n\n```tsx\n// ❌ Incorrect\naddToolResult({\n // deprecated: use `addToolOutput` instead\n toolCallId: part.toolInvocation.toolCallId,\n result: 'Yes, confirmed.', // deprecated: use `output` instead\n})\n\n// ✅ Correct\naddToolOutput({\n tool: 'askForConfirmation',\n toolCallId: part.toolCallId,\n output: 'Yes, confirmed.',\n})\n```\n\n## `messages` → `uiMessages` in `createAgentUIStreamResponse`\n\n```typescript\n// ❌ Incorrect\nreturn createAgentUIStreamResponse({\n agent: myAgent,\n messages, // incorrect: use `uiMessages` instead\n})\n\n// ✅ Correct\nreturn createAgentUIStreamResponse({\n agent: myAgent,\n uiMessages: messages,\n})\n```\n",".agents/skills/ai-sdk/references/devtools.md":"---\ntitle: AI SDK DevTools\ndescription: Debug AI SDK calls by inspecting captured runs and steps.\n---\n\n# AI SDK DevTools\n\n## Why Use DevTools\n\nDevTools captures all AI SDK calls (`generateText`, `streamText`, `ToolLoopAgent`) to a local JSON file. This lets you inspect LLM requests, responses, tool calls, and multi-step interactions without manually logging.\n\n## Setup\n\nRequires AI SDK 6. Install `@ai-sdk/devtools` using your project's package manager.\n\nWrap your model with the middleware:\n\n```ts\nimport { wrapLanguageModel, gateway } from 'ai'\nimport { devToolsMiddleware } from '@ai-sdk/devtools'\n\nconst model = wrapLanguageModel({\n model: gateway('anthropic/claude-sonnet-4.5'),\n middleware: devToolsMiddleware(),\n})\n```\n\n## Viewing Captured Data\n\nAll runs and steps are saved to:\n\n```\n.devtools/generations.json\n```\n\nRead this file directly to inspect captured data:\n\n```bash\ncat .devtools/generations.json | jq\n```\n\nOr launch the web UI:\n\n```bash\nnpx @ai-sdk/devtools\n# Open http://localhost:4983\n```\n\n## Data Structure\n\n- **Run**: A complete multi-step interaction grouped by initial prompt\n- **Step**: A single LLM call within a run (includes input, output, tool calls, token usage)\n",".agents/skills/ai-sdk/references/type-safe-agents.md":"---\ntitle: Type-Safe useChat with Agents\ndescription: Build end-to-end type-safe agents by inferring UIMessage types from your agent definition.\n---\n\n# Type-Safe useChat with Agents\n\nBuild end-to-end type-safe agents by inferring `UIMessage` types from your agent definition for type-safe UI rendering with `useChat`.\n\n## Recommended Structure\n\n```\nlib/\n agents/\n my-agent.ts # Agent definition + type export\n tools/\n weather-tool.ts # Individual tool definitions\n calculator-tool.ts\n```\n\n## Define Tools\n\n```ts\n// lib/tools/weather-tool.ts\nimport { tool } from 'ai'\nimport { z } from 'zod'\n\nexport const weatherTool = tool({\n description: 'Get current weather for a location',\n inputSchema: z.object({\n location: z.string().describe('City name'),\n }),\n execute: async ({ location }) => {\n return { temperature: 72, condition: 'sunny', location }\n },\n})\n```\n\n## Define Agent and Export Type\n\n```ts\n// lib/agents/my-agent.ts\nimport { ToolLoopAgent, InferAgentUIMessage } from 'ai'\nimport { weatherTool } from '../tools/weather-tool'\nimport { calculatorTool } from '../tools/calculator-tool'\n\nexport const myAgent = new ToolLoopAgent({\n model: 'anthropic/claude-sonnet-4',\n instructions: 'You are a helpful assistant.',\n tools: {\n weather: weatherTool,\n calculator: calculatorTool,\n },\n})\n\n// Infer the UIMessage type from the agent\nexport type MyAgentUIMessage = InferAgentUIMessage\n```\n\n### With Custom Metadata\n\n```ts\n// lib/agents/my-agent.ts\nimport { z } from 'zod'\n\nconst metadataSchema = z.object({\n createdAt: z.number(),\n model: z.string().optional(),\n})\n\ntype MyMetadata = z.infer\n\nexport type MyAgentUIMessage = InferAgentUIMessage\n```\n\n## Use with `useChat`\n\n```tsx\n// app/chat.tsx\nimport { useChat } from '@ai-sdk/react'\nimport type { MyAgentUIMessage } from '@/lib/agents/my-agent'\n\nexport function Chat() {\n const { messages } = useChat()\n\n return (\n
\n {messages.map((message) => (\n \n ))}\n
\n )\n}\n```\n\n## Rendering Parts with Type Safety\n\nTool parts are typed as `tool-{toolName}` based on your agent's tools:\n\n```tsx\nfunction Message({ message }: { message: MyAgentUIMessage }) {\n return (\n
\n {message.parts.map((part, i) => {\n switch (part.type) {\n case 'text':\n return

{part.text}

\n\n case 'tool-weather':\n // part.input and part.output are fully typed\n if (part.state === 'output-available') {\n return (\n
\n Weather in {part.input.location}: {part.output.temperature}F\n
\n )\n }\n return
Loading weather...
\n\n case 'tool-calculator':\n // TypeScript knows this is the calculator tool\n return
Calculating...
\n\n default:\n return null\n }\n })}\n
\n )\n}\n```\n\nThe `part.type` discriminant narrows the type, giving you autocomplete and type checking for `input` and `output` based on each tool's schema.\n\n## Splitting Tool Rendering into Components\n\nWhen rendering many tools, you may want to split each tool into its own component. Use `UIToolInvocation` to derive a typed invocation from your tool and export it alongside the tool definition:\n\n```ts\n// lib/tools/weather-tool.ts\nimport { tool, UIToolInvocation } from 'ai'\nimport { z } from 'zod'\n\nexport const weatherTool = tool({\n description: 'Get current weather for a location',\n inputSchema: z.object({\n location: z.string().describe('City name'),\n }),\n execute: async ({ location }) => {\n return { temperature: 72, condition: 'sunny', location }\n },\n})\n\n// Export the invocation type for use in UI components\nexport type WeatherToolInvocation = UIToolInvocation\n```\n\nThen import only the type in your component:\n\n```tsx\n// components/weather-tool.tsx\nimport type { WeatherToolInvocation } from '@/lib/tools/weather-tool'\n\nexport function WeatherToolComponent({ invocation }: { invocation: WeatherToolInvocation }) {\n // invocation.input and invocation.output are fully typed\n if (invocation.state === 'output-available') {\n return (\n
\n Weather in {invocation.input.location}: {invocation.output.temperature}F\n
\n )\n }\n return
Loading weather for {invocation.input?.location}...
\n}\n```\n\nUse the component in your message renderer:\n\n```tsx\nfunction Message({ message }: { message: MyAgentUIMessage }) {\n return (\n
\n {message.parts.map((part, i) => {\n switch (part.type) {\n case 'text':\n return

{part.text}

\n case 'tool-weather':\n return \n case 'tool-calculator':\n return \n default:\n return null\n }\n })}\n
\n )\n}\n```\n\nThis approach keeps your tool rendering logic organized while maintaining full type safety, without needing to import the tool implementation into your UI components.\n",".agents/skills/bibi/SKILL.md":"---\nname: bibi\ndescription: >\n BibiGPT CLI for summarizing videos, audio, and podcasts directly in the terminal.\n Use when the user wants to summarize a URL (YouTube, Bilibili, podcast, etc.)\n or check their BibiGPT authentication status.\n Requires the BibiGPT desktop app installed with an active login session,\n or a BIBI_API_TOKEN environment variable set.\n---\n\n# BibiGPT CLI (`bibi`)\n\nSummarize videos, audio, and podcasts from the terminal using the BibiGPT API.\n\n## Installation\n\n### macOS (Homebrew)\n\n```bash\nbrew install --cask jimmylv/bibigpt/bibigpt\n```\n\n### Windows\n\nDownload the installer from: **https://bibigpt.co/download/desktop**\n\n> `winget install BibiGPT` is pending review and not yet available.\n\n### Verify installation\n\n```bash\nbibi --version\n```\n\n## Authentication\n\nAfter installing, the user must log in via the desktop app at least once. The CLI reads the saved session automatically from the desktop app's settings.\n\nAlternatively, set an API token:\n\n```bash\nexport BIBI_API_TOKEN=\n```\n\nOn Windows (PowerShell):\n\n```powershell\n$env:BIBI_API_TOKEN=\"\"\n```\n\n## Commands\n\n### Summarize a URL\n\n**Important**: URLs containing `?` or `&` must be quoted to avoid shell glob errors.\n\n```bash\n# Basic summary (Markdown output to stdout)\nbibi summarize \"\"\n\n# Async mode — recommended for long videos (>30min)\nbibi summarize \"\" --async\n\n# Chapter-by-chapter summary\nbibi summarize \"\" --chapter\n\n# Fetch subtitles/transcript only (no AI summary)\nbibi summarize \"\" --subtitle\n\n# Full JSON response\nbibi summarize \"\" --json\n\n# Combine flags\nbibi summarize \"\" --subtitle --json\n```\n\n**Supported URL types**: YouTube, Bilibili, podcasts, audio files, and any URL supported by BibiGPT.\n\n### Authentication\n\n```bash\n# Check current auth status\nbibi auth check\n\n# Open browser to log in\nbibi auth login\n\n# Show how to set API token\nbibi auth set-token \n```\n\n### Updates\n\n```bash\n# Check if a new version is available\nbibi check-update\n\n# Download and install the latest version\nbibi self-update\n```\n\n## Output Format\n\n- **Default**: Markdown summary text sent to stdout. Progress info goes to stderr.\n- **--json**: Complete API response as pretty-printed JSON to stdout.\n\nThis means you can pipe the output:\n\n```bash\nbibi summarize \"\" > summary.md\nbibi summarize \"\" --json | jq '.summary'\n```\n\n## Error Handling\n\n| Exit Code | Meaning |\n| --------- | ---------------------------------------------- |\n| 0 | Success |\n| 1 | Error (auth missing, API error, timeout, etc.) |\n\n| HTTP Status | User Action |\n| ----------- | ---------------------------------------------------------------- |\n| 401 | Token expired — run `bibi auth login` or re-login in desktop app |\n| 402/403 | Quota exceeded — visit https://bibigpt.co/pricing |\n| 429 | Rate limited — wait and retry |\n\n## Usage Tips\n\n- For very long videos, use `--async` to avoid HTTP timeout.\n- Use `--subtitle` to get raw subtitles/transcript without AI summarization.\n- Use `--json` when you need structured data (e.g., `sourceUrl`, `htmlUrl`, `detail`).\n- The `--chapter` flag provides section-by-section summaries, useful for lectures or tutorials.\n- The CLI does NOT open any GUI window — all output goes to the terminal.\n- Run `bibi check-update` periodically to get new features and bug fixes.\n",".agents/skills/find-skills/SKILL.md":"---\nname: find-skills\ndescription: Helps users discover and install agent skills when they ask questions like \"how do I do X\", \"find a skill for X\", \"is there a skill that can...\", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.\n---\n\n# Find Skills\n\nThis skill helps you discover and install skills from the open agent skills ecosystem.\n\n## When to Use This Skill\n\nUse this skill when the user:\n\n- Asks \"how do I do X\" where X might be a common task with an existing skill\n- Says \"find a skill for X\" or \"is there a skill for X\"\n- Asks \"can you do X\" where X is a specialized capability\n- Expresses interest in extending agent capabilities\n- Wants to search for tools, templates, or workflows\n- Mentions they wish they had help with a specific domain (design, testing, deployment, etc.)\n\n## What is the Skills CLI?\n\nThe Skills CLI (`npx skills`) is the package manager for the open agent skills ecosystem. Skills are modular packages that extend agent capabilities with specialized knowledge, workflows, and tools.\n\n**Key commands:**\n\n- `npx skills find [query]` - Search for skills interactively or by keyword\n- `npx skills add ` - Install a skill from GitHub or other sources\n- `npx skills check` - Check for skill updates\n- `npx skills update` - Update all installed skills\n\n**Browse skills at:** https://skills.sh/\n\n## How to Help Users Find Skills\n\n### Step 1: Understand What They Need\n\nWhen a user asks for help with something, identify:\n\n1. The domain (e.g., React, testing, design, deployment)\n2. The specific task (e.g., writing tests, creating animations, reviewing PRs)\n3. Whether this is a common enough task that a skill likely exists\n\n### Step 2: Search for Skills\n\nRun the find command with a relevant query:\n\n```bash\nnpx skills find [query]\n```\n\nFor example:\n\n- User asks \"how do I make my React app faster?\" → `npx skills find react performance`\n- User asks \"can you help me with PR reviews?\" → `npx skills find pr review`\n- User asks \"I need to create a changelog\" → `npx skills find changelog`\n\nThe command will return results like:\n\n```\nInstall with npx skills add \n\nvercel-labs/agent-skills@vercel-react-best-practices\n└ https://skills.sh/vercel-labs/agent-skills/vercel-react-best-practices\n```\n\n### Step 3: Present Options to the User\n\nWhen you find relevant skills, present them to the user with:\n\n1. The skill name and what it does\n2. The install command they can run\n3. A link to learn more at skills.sh\n\nExample response:\n\n```\nI found a skill that might help! The \"vercel-react-best-practices\" skill provides\nReact and Next.js performance optimization guidelines from Vercel Engineering.\n\nTo install it:\nnpx skills add vercel-labs/agent-skills@vercel-react-best-practices\n\nLearn more: https://skills.sh/vercel-labs/agent-skills/vercel-react-best-practices\n```\n\n### Step 4: Offer to Install\n\nIf the user wants to proceed, you can install the skill for them:\n\n```bash\nnpx skills add -g -y\n```\n\nThe `-g` flag installs globally (user-level) and `-y` skips confirmation prompts.\n\n## Common Skill Categories\n\nWhen searching, consider these common categories:\n\n| Category | Example Queries |\n| --------------- | ---------------------------------------- |\n| Web Development | react, nextjs, typescript, css, tailwind |\n| Testing | testing, jest, playwright, e2e |\n| DevOps | deploy, docker, kubernetes, ci-cd |\n| Documentation | docs, readme, changelog, api-docs |\n| Code Quality | review, lint, refactor, best-practices |\n| Design | ui, ux, design-system, accessibility |\n| Productivity | workflow, automation, git |\n\n## Tips for Effective Searches\n\n1. **Use specific keywords**: \"react testing\" is better than just \"testing\"\n2. **Try alternative terms**: If \"deploy\" doesn't work, try \"deployment\" or \"ci-cd\"\n3. **Check popular sources**: Many skills come from `vercel-labs/agent-skills` or `ComposioHQ/awesome-claude-skills`\n\n## When No Skills Are Found\n\nIf no relevant skills exist:\n\n1. Acknowledge that no existing skill was found\n2. Offer to help with the task directly using your general capabilities\n3. Suggest the user could create their own skill with `npx skills init`\n\nExample:\n\n```\nI searched for skills related to \"xyz\" but didn't find any matches.\nI can still help you with this task directly! Would you like me to proceed?\n\nIf this is something you do often, you could create your own skill:\nnpx skills init my-xyz-skill\n```\n",".agents/skills/next-best-practices/SKILL.md":"---\nname: next-best-practices\ndescription: Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling\nuser-invocable: false\n---\n\n# Next.js Best Practices\n\nApply these rules when writing or reviewing Next.js code.\n\n## File Conventions\n\nSee [file-conventions.md](./file-conventions.md) for:\n\n- Project structure and special files\n- Route segments (dynamic, catch-all, groups)\n- Parallel and intercepting routes\n- Middleware rename in v16 (middleware → proxy)\n\n## RSC Boundaries\n\nDetect invalid React Server Component patterns.\n\nSee [rsc-boundaries.md](./rsc-boundaries.md) for:\n\n- Async client component detection (invalid)\n- Non-serializable props detection\n- Server Action exceptions\n\n## Async Patterns\n\nNext.js 15+ async API changes.\n\nSee [async-patterns.md](./async-patterns.md) for:\n\n- Async `params` and `searchParams`\n- Async `cookies()` and `headers()`\n- Migration codemod\n\n## Runtime Selection\n\nSee [runtime-selection.md](./runtime-selection.md) for:\n\n- Default to Node.js runtime\n- When Edge runtime is appropriate\n\n## Directives\n\nSee [directives.md](./directives.md) for:\n\n- `'use client'`, `'use server'` (React)\n- `'use cache'` (Next.js)\n\n## Functions\n\nSee [functions.md](./functions.md) for:\n\n- Navigation hooks: `useRouter`, `usePathname`, `useSearchParams`, `useParams`\n- Server functions: `cookies`, `headers`, `draftMode`, `after`\n- Generate functions: `generateStaticParams`, `generateMetadata`\n\n## Error Handling\n\nSee [error-handling.md](./error-handling.md) for:\n\n- `error.tsx`, `global-error.tsx`, `not-found.tsx`\n- `redirect`, `permanentRedirect`, `notFound`\n- `forbidden`, `unauthorized` (auth errors)\n- `unstable_rethrow` for catch blocks\n\n## Data Patterns\n\nSee [data-patterns.md](./data-patterns.md) for:\n\n- Server Components vs Server Actions vs Route Handlers\n- Avoiding data waterfalls (`Promise.all`, Suspense, preload)\n- Client component data fetching\n\n## Route Handlers\n\nSee [route-handlers.md](./route-handlers.md) for:\n\n- `route.ts` basics\n- GET handler conflicts with `page.tsx`\n- Environment behavior (no React DOM)\n- When to use vs Server Actions\n\n## Metadata & OG Images\n\nSee [metadata.md](./metadata.md) for:\n\n- Static and dynamic metadata\n- `generateMetadata` function\n- OG image generation with `next/og`\n- File-based metadata conventions\n\n## Image Optimization\n\nSee [image.md](./image.md) for:\n\n- Always use `next/image` over ``\n- Remote images configuration\n- Responsive `sizes` attribute\n- Blur placeholders\n- Priority loading for LCP\n\n## Font Optimization\n\nSee [font.md](./font.md) for:\n\n- `next/font` setup\n- Google Fonts, local fonts\n- Tailwind CSS integration\n- Preloading subsets\n\n## Bundling\n\nSee [bundling.md](./bundling.md) for:\n\n- Server-incompatible packages\n- CSS imports (not link tags)\n- Polyfills (already included)\n- ESM/CommonJS issues\n- Bundle analysis\n\n## Scripts\n\nSee [scripts.md](./scripts.md) for:\n\n- `next/script` vs native script tags\n- Inline scripts need `id`\n- Loading strategies\n- Google Analytics with `@next/third-parties`\n\n## Hydration Errors\n\nSee [hydration-error.md](./hydration-error.md) for:\n\n- Common causes (browser APIs, dates, invalid HTML)\n- Debugging with error overlay\n- Fixes for each cause\n\n## Suspense Boundaries\n\nSee [suspense-boundaries.md](./suspense-boundaries.md) for:\n\n- CSR bailout with `useSearchParams` and `usePathname`\n- Which hooks require Suspense boundaries\n\n## Parallel & Intercepting Routes\n\nSee [parallel-routes.md](./parallel-routes.md) for:\n\n- Modal patterns with `@slot` and `(.)` interceptors\n- `default.tsx` for fallbacks\n- Closing modals correctly with `router.back()`\n\n## Self-Hosting\n\nSee [self-hosting.md](./self-hosting.md) for:\n\n- `output: 'standalone'` for Docker\n- Cache handlers for multi-instance ISR\n- What works vs needs extra setup\n\n## Debug Tricks\n\nSee [debug-tricks.md](./debug-tricks.md) for:\n\n- MCP endpoint for AI-assisted debugging\n- Rebuild specific routes with `--debug-build-paths`\n",".agents/skills/next-best-practices/async-patterns.md":"# Async Patterns\n\nIn Next.js 15+, `params`, `searchParams`, `cookies()`, and `headers()` are asynchronous.\n\n## Async Params and SearchParams\n\nAlways type them as `Promise<...>` and await them.\n\n### Pages and Layouts\n\n```tsx\ntype Props = { params: Promise<{ slug: string }> }\n\nexport default async function Page({ params }: Props) {\n const { slug } = await params\n}\n```\n\n### Route Handlers\n\n```tsx\nexport async function GET(request: Request, { params }: { params: Promise<{ id: string }> }) {\n const { id } = await params\n}\n```\n\n### SearchParams\n\n```tsx\ntype Props = {\n params: Promise<{ slug: string }>\n searchParams: Promise<{ query?: string }>\n}\n\nexport default async function Page({ params, searchParams }: Props) {\n const { slug } = await params\n const { query } = await searchParams\n}\n```\n\n### Synchronous Components\n\nUse `React.use()` for non-async components:\n\n```tsx\nimport { use } from 'react'\n\ntype Props = { params: Promise<{ slug: string }> }\n\nexport default function Page({ params }: Props) {\n const { slug } = use(params)\n}\n```\n\n### generateMetadata\n\n```tsx\ntype Props = { params: Promise<{ slug: string }> }\n\nexport async function generateMetadata({ params }: Props): Promise {\n const { slug } = await params\n return { title: slug }\n}\n```\n\n## Async Cookies and Headers\n\n```tsx\nimport { cookies, headers } from 'next/headers'\n\nexport default async function Page() {\n const cookieStore = await cookies()\n const headersList = await headers()\n\n const theme = cookieStore.get('theme')\n const userAgent = headersList.get('user-agent')\n}\n```\n\n## Migration Codemod\n\n```bash\nnpx @next/codemod@latest next-async-request-api .\n```\n",".agents/skills/next-best-practices/bundling.md":"# Bundling\n\nFix common bundling issues with third-party packages.\n\n## Server-Incompatible Packages\n\nSome packages use browser APIs (`window`, `document`, `localStorage`) and fail in Server Components.\n\n### Error Signs\n\n```\nReferenceError: window is not defined\nReferenceError: document is not defined\nReferenceError: localStorage is not defined\nModule not found: Can't resolve 'fs'\n```\n\n### Solution 1: Mark as Client-Only\n\nIf the package is only needed on client:\n\n```tsx\n// Bad: Fails - package uses window\nimport SomeChart from 'some-chart-library'\n\nexport default function Page() {\n return \n}\n\n// Good: Use dynamic import with ssr: false\nimport dynamic from 'next/dynamic'\n\nconst SomeChart = dynamic(() => import('some-chart-library'), {\n ssr: false,\n})\n\nexport default function Page() {\n return \n}\n```\n\n### Solution 2: Externalize from Server Bundle\n\nFor packages that should run on server but have bundling issues:\n\n```js\n// next.config.js\nmodule.exports = {\n serverExternalPackages: ['problematic-package'],\n}\n```\n\nUse this for:\n\n- Packages with native bindings (sharp, bcrypt)\n- Packages that don't bundle well (some ORMs)\n- Packages with circular dependencies\n\n### Solution 3: Client Component Wrapper\n\nWrap the entire usage in a client component:\n\n```tsx\n// components/ChartWrapper.tsx\n'use client'\n\nimport { Chart } from 'chart-library'\n\nexport function ChartWrapper(props) {\n return \n}\n\n// app/page.tsx (server component)\nimport { ChartWrapper } from '@/components/ChartWrapper'\n\nexport default function Page() {\n return \n}\n```\n\n## CSS Imports\n\nImport CSS files instead of using `` tags. Next.js handles bundling and optimization.\n\n```tsx\n// Bad: Manual link tag\n;\n\n// Good: Import CSS\nimport './styles.css'\n\n// Good: CSS Modules\nimport styles from './Button.module.css'\n```\n\n## Polyfills\n\nNext.js includes common polyfills automatically. Don't load redundant ones from polyfill.io or similar CDNs.\n\nAlready included: `Array.from`, `Object.assign`, `Promise`, `fetch`, `Map`, `Set`, `Symbol`, `URLSearchParams`, and 50+ others.\n\n```tsx\n// Bad: Redundant polyfills\n\n\n// Good: Next.js Script component\nimport Script from 'next/script'\n;\n```\n\n## Don't Put Script in Head\n\n`next/script` should not be placed inside `next/head`. It handles its own positioning.\n\n```tsx\n// Bad: Script inside Head\nimport Head from 'next/head'\nimport Script from 'next/script'\n\n\n \n\n// Good: Next.js component\nimport { GoogleAnalytics } from '@next/third-parties/google'\n\nexport default function Layout({ children }) {\n return (\n \n {children}\n \n \n )\n}\n```\n\n## Google Tag Manager\n\n```tsx\nimport { GoogleTagManager } from '@next/third-parties/google'\n\nexport default function Layout({ children }) {\n return (\n \n \n {children}\n \n )\n}\n```\n\n## Other Third-Party Scripts\n\n```tsx\n// YouTube embed\nimport { YouTubeEmbed } from '@next/third-parties/google'\n;\n\n// Google Maps\nimport { GoogleMapsEmbed } from '@next/third-parties/google'\n;\n```\n\n## Quick Reference\n\n| Pattern | Issue | Fix |\n| --------------------------------------------- | -------------------------- | ------------------------- |\n| `\n\n// Good: Next.js Script component\nimport Script from 'next/script'\n;\n```\n\n## Don't Put Script in Head\n\n`next/script` should not be placed inside `next/head`. It handles its own positioning.\n\n```tsx\n// Bad: Script inside Head\nimport Head from 'next/head'\nimport Script from 'next/script'\n\n\n \n\n// Good: Next.js component\nimport { GoogleAnalytics } from '@next/third-parties/google'\n\nexport default function Layout({ children }) {\n return (\n \n {children}\n \n \n )\n}\n```\n\n## Google Tag Manager\n\n```tsx\nimport { GoogleTagManager } from '@next/third-parties/google'\n\nexport default function Layout({ children }) {\n return (\n \n \n {children}\n \n )\n}\n```\n\n## Other Third-Party Scripts\n\n```tsx\n// YouTube embed\nimport { YouTubeEmbed } from '@next/third-parties/google'\n;\n\n// Google Maps\nimport { GoogleMapsEmbed } from '@next/third-parties/google'\n;\n```\n\n## Quick Reference\n\n| Pattern | Issue | Fix |\n| --------------------------------------------- | -------------------------- | ------------------------- |\n| `\n\n// Good: Next.js Script component\nimport Script from 'next/script'\n;\n```\n\n## Don't Put Script in Head\n\n`next/script` should not be placed inside `next/head`. It handles its own positioning.\n\n```tsx\n// Bad: Script inside Head\nimport Head from 'next/head'\nimport Script from 'next/script'\n\n\n \n\n// Good: Next.js component\nimport { GoogleAnalytics } from '@next/third-parties/google'\n\nexport default function Layout({ children }) {\n return (\n \n {children}\n \n \n )\n}\n```\n\n## Google Tag Manager\n\n```tsx\nimport { GoogleTagManager } from '@next/third-parties/google'\n\nexport default function Layout({ children }) {\n return (\n \n \n {children}\n \n )\n}\n```\n\n## Other Third-Party Scripts\n\n```tsx\n// YouTube embed\nimport { YouTubeEmbed } from '@next/third-parties/google'\n;\n\n// Google Maps\nimport { GoogleMapsEmbed } from '@next/third-parties/google'\n;\n```\n\n## Quick Reference\n\n| Pattern | Issue | Fix |\n| --------------------------------------------- | -------------------------- | ------------------------- |\n| `