11 tagged browser-testing, measured the same way as everything else here.
Skill Claude CodeCodex
Use when an agent needs to operate HeadlessX through the published headlessx CLI instead of calling files or APIs directly. Covers installing the CLI package, bootstrapping local HeadlessX with headlessx init, updating an existing workspace with headlessx init update, using the guided modern setup/login prompts…
Skill Claude CodeCodex
Part of daily-working
End-to-end pipeline: pull a task from Redmine by ID, sanity-check and impact-assess it against the codebase before touching anything, implement it with the Claude CLI, verify the result in a real browser via the Claude Chrome extension (claude-in-chrome), and keep the Redmine ticket in sync throughout (in-progress…
Skill Claude CodeCodex
Route and run BeforeUsersDo QA through its MCP tools. Use when a user asks to test, QA, review, or get feedback on a website, app, feature, preview, or user flow; asks for AI QA, a personal self-review, a real human tester, QA status, video, transcript, findings, or a completed BeforeUsersDo report.
Skill Claude CodeCodex
Part of flipbook
Validate that a web application actually works by recording the browser while driving it, then judging the recording against a rubric. Use when asked to check, verify, test, or QA a web app's behaviour in a real browser — especially for anything involving loading states, animations, timing, flicker, layout shift, or…
Skill Claude CodeCodex
Battle-tested Playwright patterns for E2E, API, component, visual, accessibility, and security testing. Covers locators, fixtures, POM, network mocking, auth flows, debugging, CI/CD (GitHub Actions, GitLab, CircleCI, Azure, Jenkins), framework recipes (React, Next.js, Vue, Angular), and migration guides from…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: