skills/browser-dev/SKILL.md
Lightweight browser automation via custom scripts. Use when Playwright MCP or Claude-in-Chrome is unavailable, or for building reusable browser check flows.
npx skillsauth add RonanCodes/ronan-skills browser-devInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Write and run Node.js browser automation scripts using Playwright as a library. No MCP required. Scripts are saved for reuse.
/browser-dev http://localhost:3000 --screenshot
/browser-dev http://localhost:3000 --check
/browser-dev --script .browser-dev/login-flow.js
/browser-dev http://localhost:3000 --flow "click Sign In, fill email, fill password, submit, check dashboard loads"
Before running, detect the automation library:
node -e "require('playwright')" 2>/dev/null && echo "playwright" || \
node -e "require('puppeteer')" 2>/dev/null && echo "puppeteer" || echo "none"
If none: tell the user to install one — npm install -D playwright && npx playwright install chromium. Prefer Playwright (cross-browser, auto-waiting, better API). Do NOT proceed without a library installed.
| Flag | Action |
|------|--------|
| --screenshot <url> | Full-page screenshot, saved to .browser-dev/screenshots/<timestamp>.png |
| --check <url> | Verify page loads (200), no console errors, no uncaught exceptions. Pass/fail table. Exit 1 on fail |
| --script <path> | Run an existing script: node <path> [args]. No generation needed |
| --flow "desc" | Generate a custom script from natural-language description, save to .browser-dev/flows/<slug>.js, run it |
All generated scripts follow this pattern:
const { chromium } = require('playwright');
(async () => {
const browser = await chromium.launch({ headless: true });
const context = await browser.newContext({ viewport: { width: 1280, height: 720 } });
const page = await context.newPage();
const errors = [];
page.on('pageerror', err => errors.push(err.message));
page.on('console', msg => { if (msg.type() === 'error') errors.push(msg.text()); });
// --- flow logic here ---
await browser.close();
if (errors.length) { console.error('Errors:', errors); process.exit(1); }
})();
.browser-dev/
├── screenshots/ # --screenshot output
├── flows/ # saved --flow scripts
└── scripts/ # user's custom scripts
Add .browser-dev/ to .gitignore if not already present.
playwright or puppeteer before generating scripts — adapt require() to whichever is installedheadless: true unless the user explicitly asks for headed mode--scriptwaitUntil: 'networkidle' for page loads by defaultdevelopment
--- name: worktree description: Coordinate multiple agents on one repo via a worktree-lock pool, so two agents never clobber each other's working tree. Acquire the first free slot (main, then beta/gamma… worktrees, created on demand), work there on your own branch, release when you've pushed. Use before modifying any repo that might be in use by another agent (factory, dataforce, etc.), or whenever you're told a repo is being worked on. Backed by `ro worktree`. category: development argument-hin
testing
--- name: ship description: Ship a feature branch the local-CI-first way — run the full local gate, push, open a PR, squash-merge, then deploy, without waiting on GitHub Actions. Use when a branch is ready for main and you want it merged and deployed now. Reads CI policy from `ro ci` (default skips remote CI because GitHub Actions billing keeps hitting limits). Sibling to /ro:gh-ship (waits on GitHub checks) and /ro:cf-ship (the deploy half). Triggers on "ship it", "ship this", "merge and deploy
testing
--- name: setup-logging description: Set up (or audit) the observability stack in a TanStack Start + Cloudflare Workers app so it is "diagnosable by default" — structured logging (logtape) with a request context carrying trace_id + userId + tenant/orgId, a trace_id propagated FE→BE→logs→Sentry→PostHog, Cloudflare Workers observability enabled, and Sentry + PostHog wired. Two modes: `setup` (wire it into an app) and `audit` (check an existing app + report gaps). Use when scaffolding a new app, wh
development
Manage credentials INSIDE the active ~/.claude/.env file — read which token/account to use for a given app (Simplicity vs Dataforce vs Ronan-personal), add or update a secret WITHOUT it passing through the chat (an interactive Terminal window prompts for it), and track secrets that were exposed in a transcript so they get rotated. Sibling to /ro:context (which switches WHICH env file is active). Use when the user wants to add an API key/token/secret, asks "which credential do I use for X", needs the env organized/labelled, or a secret was pasted into the chat and should be rotated.