From remorses-playwriter
Automates user's existing Chrome browser with Playwright code snippets in stateful JS sandbox via playwriter CLI. Use for JS-heavy sites like Instagram/Twitter, cookie walls, lazy UIs over webfetch.
npx claudepluginhub joshuarweaver/cascade-code-testing-misc --plugin remorses-playwriterThis skill uses the workspace's default tool permissions.
**Before using playwriter, you MUST run this command:**
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Before using playwriter, you MUST run this command:
playwriter skill # IMPORTANT! do not use | head here. read in full!
This outputs the complete documentation including:
Do NOT skip this step. The quick examples below will fail without understanding timeouts, selector rules, and common pitfalls from the full docs.
Read the ENTIRE output. Do NOT pipe through head, tail, or any truncation command. The skill output must be read in its entirety — critical rules about timeouts, selectors, and common pitfalls are spread throughout the document, not just at the top.
playwriter session new
playwriter -s 1 -e 'await page.goto("https://example.com")'
Always use single quotes for the -e argument. Single quotes prevent bash from interpreting $, backticks, and backslashes inside your JS code. Use double quotes or backtick template literals for strings inside the JS.
If playwriter is not found, use npx playwriter@latest or bunx playwriter@latest.