Results for “playwright-cli”

Control a headless browser to navigate pages, click elements, fill forms, take screenshots, record video, and execute JavaScript using Playwright and inference.sh.

Automates filling in a Microsoft Forms form using Playwright MCP, with a review step before submission.

Explores websites using Playwright to identify core features and generate test cases.

Generates a Playwright test from a user-provided scenario by recording browser interactions via Playwright MCP, then saves and runs the test until it passes.

Create or update Cursor agent skills (SKILL.md). Use when authoring a new skill, updating an existing skill, or asking about SKILL.md structure and best practices.

Build or refactor CLI tools designed for AI agent consumption: non-interactive, flag-driven, idempotent, with --json output and --dry-run preview. Use when creating a new script the agent will call, adding agent-friendly flags to an existing tool, or debugging why an agent keeps failing to use your CLI.

Structured producer who turns research insights into production-ready slide deck outlines and scripts. Triggers: 'create slides', 'write webinar script', 'build slide deck', 'webinar outline', 'produce webinar', or when user asks for the Producer.

Build and run Gemini 2.5 Computer Use browser-control agents with Playwright. Use when a user wants to automate web browser tasks via the Gemini Computer Use model, needs an agent loop (screenshot → function_call → action → function_response), or asks to integrate safety confirmation for risky UI actions.

Reuse a running Chrome session for browser automation via Playwriter CLI + MCP. Use when the task depends on the browser the user already has open — existing logins, cookies, extensions, passkey-friendly flows, or live-tab continuity. Route repeatable fresh-browser or CI-style checks to `browser-harness` instead.

Write robust, maintainable end-to-end tests with Playwright using Page Object Model, proper selectors, auto-waiting, and debugging workflows.

Sets up a codebase for reliable agent-driven development by making it legible (structured docs, custom lints, code graph), executable (one-command dev stack, cloud sandbox), and verifiable (e2e gate, verify-before-ship loop).

Use the public `orca` CLI to operate Orca-managed worktrees, folder contexts, terminals, repos, automations, worktree comments, and the browser embedded inside the Orca app. Use when the user says "$orca-cli", "use orca cli", "Orca worktree", "child worktree", "cardStatus", "spawn codex/claude in a worktree", "read/wait/send Orca terminal", "terminal send", "full handoff", "handover", "give this to another agent", "another worktree", "Orca browser", or "control the browser inside Orca". Prefer this over raw `git worktree`, ad hoc PTYs, Playwright, or Computer Use when the task touches Orca-managed state. Use Computer Use for browser windows, webviews, or desktop UI outside Orca's embedded browser.