skills/playwright-check/SKILL.md
Browser-based verification using Playwright MCP or Claude-in-Chrome. Navigate pages, interact, screenshot, check console errors. Use when you need to check a page, verify UI, take screenshots, or test browser interactions.
npx skillsauth add RonanCodes/ronan-skills playwright-checkInstall 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.
Browser verification. Navigate to pages, interact with UI, take screenshots, check for console errors.
/playwright-check http://localhost:3000
/playwright-check http://localhost:3000/settings --flow "click #save-btn, wait 1s, check .toast"
/playwright-check http://localhost:3000 --responsive
Try browser tools in priority order. Attempt to use each; if it errors, fall back:
mcp__playwright__ tools (navigate, screenshot, click)mcp__claude-in-chrome__ toolscurl -s -o /dev/null -w "%{http_code}" for basic HTTP checksState which tool is being used in the output.
Navigate to URL, wait for load, screenshot (unless --no-screenshot), check console for errors/warnings, verify HTTP 200.
Parse comma-separated actions: click <selector>, type <selector> "text", wait <duration>, check <selector>, submit <selector>. Screenshot after each action.
Screenshot at 375px (mobile), 768px (tablet), 1440px (desktop). Flag overlapping elements, horizontal scroll, or cut-off content.
Save to .playwright-checks/<feature>/ (e.g. desktop-1440.png, after-click-save.png). Add .playwright-checks/ to .gitignore if not already there.
## Browser Check: [url]
- Tool: Playwright MCP
- Status: 200 OK
- Console errors: none
| Check | Status | Notes |
|-------|--------|-------|
| Page load | Pass | Loaded in 1.2s |
| Console | Pass | No errors |
| Click #save-btn | Pass | Toast appeared |
--no-screenshot.playwright-checks/ to .gitignore if missingdevelopment
--- 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.