From 7f745fc0616a71559b6901c8fdf6dd04639972e0 Mon Sep 17 00:00:00 2001 From: Cal Corum Date: Thu, 5 Mar 2026 19:52:12 -0600 Subject: [PATCH] Add Chrome vs playwright-cli positioning guide 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 --- skills/playwright-cli/SKILL.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/skills/playwright-cli/SKILL.md b/skills/playwright-cli/SKILL.md index 11bad2b..3127636 100644 --- a/skills/playwright-cli/SKILL.md +++ b/skills/playwright-cli/SKILL.md @@ -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