Visual QA validation with agent-browser. Use when: - User asks to "validate", "check visually", "QA check" - After creating or modifying components - Before PR submission - User mentions "accessibility", "a11y", "contrast", "touch targets" - User wants to verify UI looks correct
Scanned 2/12/2026
Install via CLI
openskills install darkroomengineering/cc-settings---
name: qa
description: |
Visual QA validation with agent-browser. Use when:
- User asks to "validate", "check visually", "QA check"
- After creating or modifying components
- Before PR submission
- User mentions "accessibility", "a11y", "contrast", "touch targets"
- User wants to verify UI looks correct
context: fork
allowed-tools: [Bash]
---
# Visual QA Validation
Comprehensive visual and accessibility validation using agent-browser.
## Quick Start
```bash
# Validate dev server
agent-browser navigate http://localhost:3000
agent-browser screenshot
agent-browser snapshot
```
## Validation Checklist
### Accessibility
- [ ] All images have `alt` text
- [ ] Icon-only buttons have `aria-label`
- [ ] Form inputs have labels
- [ ] Heading hierarchy is correct
- [ ] Focus order is logical
### Touch Targets
- [ ] Interactive elements ≥ 44x44px
- [ ] Adequate spacing between targets
### Contrast
- [ ] Text meets 4.5:1 ratio
- [ ] UI elements are distinguishable
### Layout
- [ ] No horizontal overflow
- [ ] Proper spacing and alignment
- [ ] Responsive at different sizes
### States
- [ ] Hover states visible
- [ ] Focus indicators present
- [ ] Loading states implemented
- [ ] Error states clear
## Workflow
1. **Navigate** to target URL
2. **Screenshot** current state
3. **Snapshot** accessibility tree
4. **Analyze** against checklist
5. **Report** issues with fixes
## Commands
```bash
# Navigate
agent-browser navigate http://localhost:3000/page
# Screenshot
agent-browser screenshot
# Accessibility tree
agent-browser snapshot
# Interact with elements
agent-browser click @e5
agent-browser type @e3 "test input"
```
## Output
```
## QA Report: [Page/Component]
### Passed
- [x] Touch targets adequate
- [x] Heading hierarchy correct
### Issues
- [ ] Missing alt text on hero image
→ Add alt="..." to components/hero/index.tsx:15
- [ ] Contrast too low on muted text
→ Change text-gray-400 to text-gray-500
### Recommendations
- Consider adding loading skeleton for async content
```
## Prerequisites
```bash
npm i -g agent-browser@0.8.3
```
No comments yet. Be the first to comment!
Playbook for creating and editing uCoz landing pages via MCP tools (`templates_tool`, `ftp_tool`, `modules_tool`). Use for tasks such as: "build a landing page", "update the homepage as a landing page", "create a promo page on the homepage", "add a lead form / menu / SEO to the homepage". Homepage: `page_list`, `page_get`; first publish — `page_update` with full `page_tmpl`; HTML edits after generation — `patch_template` (module_id=2, template_id=1), not `update_template`. Activate the mail f...
Interact with the Paperclip control plane API to manage tasks, coordinate with other agents, and follow company governance. Use when you need to check assignments, update task status, delegate work, post comments, set up or manage routines (recurring scheduled tasks), or call any Paperclip API endpoint. Do NOT use for the actual domain work itself (writing code, research, etc.) — only for Paperclip coordination.
Digital Audio Workstation usage, music composition, interactive music systems, and game audio implementation for immersive soundscapes.
Instantly.ai cold email outreach API - manage campaigns, leads, accounts, and analytics. Use for cold email automation, lead management, campaign creation/monitoring, and email account warmup.
Use when an operation issue asks you to ingest a captured source from `raw/` into the LLM Wiki, or when the user explicitly says "ingest <slug>". The issue body will name a file under `raw/` (e.g. `raw/karpathy-llm-wiki.md`) and ask for durable wiki pages. Do not invoke this skill for Paperclip activity bundles — those use `paperclip-distill` instead.