playwright-browser | ai-coding-config | ClaudePluginHub

Skill

Community

playwright-browser

From ai-coding-config

11

Description

Use when automating browsers, testing pages, taking screenshots, checking UI, verifying login flows, or testing responsive behavior

AI Summary

Automate browser testing and UI verification with Playwright. Triggers when you need to test pages, take screenshots, check login flows, or verify responsive behavior.

Install

1

Add the repository(one-time)

$

/plugin marketplace add TechNickAI/ai-coding-config

2

Install the plugin

$

/plugin install ai-coding-config@ai-coding-config

Tool Access

This skill inherits all available tools. When active, it can use any tool Claude has access to.

Supporting Assets

View in Repository

API_REFERENCE.md

package.json

run.js

Skill Content

<objective> Browser automation via Playwright. Write scripts, execute via run.js. </objective> <execution> Write Playwright code to /tmp, execute from skill directory:

node $SKILL_DIR/run.js /tmp/playwright-task.js

For inline code (variables are auto-injected, see below):

node $SKILL_DIR/run.js "const b = await chromium.launch(); const p = await b.newPage(); await p.goto('http://localhost:3000'); console.log(await p.title()); await b.close();"

$SKILL_DIR is where you loaded this file from. </execution>

<headless-vs-headed> Default: headless (invisible, less intrusive).

Use { headless: false } when user wants to see the browser. You know when that is. </headless-vs-headed>

<defaults> Screenshots to /tmp. Use `slowMo: 100` for debugging. </defaults> <injected-variables> For inline code, these are available:

BASE_URL - from PLAYWRIGHT_BASE_URL env var
CI_ARGS - browser args for CI (['--no-sandbox', '--disable-setuid-sandbox'])
EXTRA_HEADERS - from PW_HEADER_NAME/VALUE or PW_EXTRA_HEADERS
chromium, firefox, webkit, devices - from playwright

Example:

node $SKILL_DIR/run.js "
const browser = await chromium.launch({ args: CI_ARGS });
const page = await browser.newPage();
await page.goto(BASE_URL || 'http://localhost:3000');
console.log(await page.title());
await browser.close();
"

</injected-variables> <auto-install> run.js auto-installs Playwright on first use. No manual setup needed. </auto-install> <advanced-patterns> For network mocking, auth persistence, multi-tab, downloads, video, traces: [API_REFERENCE.md](API_REFERENCE.md) </advanced-patterns>

Links

GitHub Stats

0 forks

Updated 2 days ago

Similar Skills

Command Development

This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.

53.4k

Agent Development

This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.

53.4k

Hook Development

This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.

53.4k