cal/claude-configs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add Chrome vs playwright-cli positioning guide

Browse Source 
Clarifies when to use native Chrome integration vs playwright-cli
(headless automation, network mocking, persistent sessions, SSH/containers).

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Cal Corum 2026-03-05 19:52:12 -06:00
parent 67337a6771
commit 7f745fc061
1 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
skills/playwright-cli/SKILL.md
View File

@ -6,6 +6,17 @@ allowed-tools: Bash(playwright-cli:*)
# Browser Automation with playwright-cli
## When to Use This vs Native Chrome
| Scenario | Use |
|----------|-----|
| Interactive testing, visual debugging | Native Chrome integration |
| Quick form automation in your session | Native Chrome integration |
| Headless/unattended automation (scheduled tasks) | playwright-cli |
| Persistent sessions across prompts | playwright-cli |
| Network mocking / route interception | playwright-cli |
| Running in containers or SSH sessions | playwright-cli |
## Quick start
```bash