From theclauu
Use for headless-browser QA work — systematic testing with optional fixes, post-deploy canary monitoring, performance benchmarking, ad-hoc navigation, cookie setup, and autonomous visual crawl.
npx claudepluginhub artemis-xyz/theclauu --plugin theclauuThis skill uses the workspace's default tool permissions.
Browser-automation framework with modes for different QA tasks. Uses a fast headless browser (~100ms per command) for navigating, interacting, screenshotting, and verifying state.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
Browser-automation framework with modes for different QA tasks. Uses a fast headless browser (~100ms per command) for navigating, interacting, screenshotting, and verifying state.
Pick the mode based on the task:
When: user says "qa", "test this site", "find bugs and fix them", "test and fix."
Process:
Three tiers based on user's appetite:
When: user says "qa report only", "just check for bugs", "don't fix anything."
Same as test-and-fix but stops at step 3. Deliverable is a structured report (bug list + screenshots + repro). No code changes.
When: user says "canary", "monitor deploy", "verify deploy", "watch production."
Process:
When: user says "benchmark", "performance", "page speed", "check bundle size", "web vitals."
Process:
When: user says "open in browser", "screenshot this page", "click this button then verify X", "test this form."
A general-purpose browser automation interface. Navigate, interact with elements, take screenshots, verify assertions, handle dialogs, test forms/uploads.
No process — it's a tool. Agent picks commands based on task.
When: user needs to test authenticated pages.
Process:
Use before test-and-fix, report-only, canary, or visual-crawl if auth is required.
When: user says "visual crawl", "screenshot every page", "test the whole frontend."
Process:
--deep: click every button, fill every form, simulate chat, verify state changes).--output session for chat-only analysis, or --output github for issue creation).Heavier than test-and-fix; use for full-frontend audits.
Consolidated from gstack's qa, qa-only, canary, benchmark, browse, setup-browser-cookies, and claudefather's visual-crawl. Pick the mode based on the task.