dev-browser

Browser automation with persistent page state lets you run small, focused scripts that build on each other without losing context. This Skill uses Playwright-based runtime to maintain your browser session across executions, so navigation, form data, and authentication persist between runs.

Yes. This Skill automates Playwright-based workflows for web testing, form filling, screenshot capture, and data scraping. It supports both standalone browser instances and connection to existing ones, making it suitable for testing authenticated workflows and multi-step interactions.

Standalone mode spawns a fresh browser instance for each session, ideal for isolated tests. Extension mode connects to an existing browser, preserving authentication and user context—useful for workflows that require logged-in interactions or reusing established sessions.

Install dependencies with `npm i`, start the local server with `npm run start-server`, then launch extension mode with `npm run start-extension`. This sets up the Playwright runtime and local server needed to maintain page state across incremental script executions.

Yes. This Skill supports incremental workflow assembly—you write deterministic small scripts that reuse the persistent browser context across executions, letting you compose larger automations step by step while maintaining navigation history and filled form data.

Yes. Common use cases include site navigation, web data scraping, and screenshot capture. Persistent page state ensures multi-step scraping workflows can navigate through pages and extract data without re-authenticating or losing your position in the site.