Menu
User acceptance testing procedures for web applications. Use when: validating features with real users, conducting UAT sessions, or preparing for release.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Audit the developer experience of a product, SDK, docs site, or SKILL.md by dropping multiple Claude subagents at it with only a tiny task prompt and real tools (WebFetch, Bash, Write). Agents must discover the docs themselves, install deps, ask for credentials if needed, and attempt real execution. The skill captures each agent's trace — tool calls, retries, wall time, errors — and scores on Setup Friction, Speed, Efficiency, Error Recovery, and Doc Quality, then emits an HTML report with an A–F grade and concrete fixes. Use when the user asks to audit agent experience, test a skill, audit docs for agents, check if a SDK is agent-friendly, validate a SKILL.md, measure agent DX, or benchmark how painful onboarding is for an AI agent. Triggers: 'audit agent experience', 'test this skill', 'audit docs for agents', 'is my SDK agent-friendly', 'run a DX audit', 'agent experience test', 'test my docs', 'how do agents do with my product'.
Self-improving browser automation via the auto-research loop. Iteratively runs a browsing task, reads the trace, and improves the navigation skill (strategy.md) until it reliably passes. Supports parallel runs across multiple tasks using sub-agents. Use when you want to build or improve browser automation skills for specific website tasks.
Create polished design artifacts as self-contained HTML: UI mockups, interactive prototypes, wireframes, landing pages, dashboards, app screens, mobile apps, slide decks, and visual explorations. Use whenever the user asks to design, mock up, prototype, wireframe, visualize, or explore an interface, product screen, user flow, content layout, visual artifact, or pitch/deck concept, even if they do not say "design". Also use for setting up, importing, or authoring reusable design systems, UI kits, brand tokens, component libraries, or loadable design-system bundles. The skill guides context gathering, clarifying questions, choosing fidelity, selecting or binding design systems, creating project folders, building one or more HTML deliverables, previewing them, and verifying they load cleanly. It is harness-agnostic for Claude Code, Cursor, Codex Agent, and similar file-capable agents; harness-specific ask, preview, screenshot, and verification tools are resolved from references/.
Use the Browserbase CLI (`browse`) for Browserbase Functions and platform API workflows. Use when the user asks to run `browse`, deploy or invoke functions, manage sessions, projects, contexts, or extensions, fetch a page through the Browserbase Fetch API, search the web through the Browserbase Search API, or scaffold starter templates. Prefer the Browser skill for interactive browsing; use the top-level `browse` driver commands (`browse open`, `browse get`, etc.) only when the user explicitly wants the CLI path.
Sync cookies from local Chrome to a Browserbase persistent context so the browse CLI can access authenticated sites. Use when the user wants to browse as themselves, sync cookies, or log into sites via Browserbase.
Build local constrained-browser agents with a safe_browser tool that owns CDP, enforces a domain allowlist with Fetch interception, and lets a runtime Claude Agent SDK agent complete browsing tasks without raw browser, shell, or CDP access. Use when the user wants an agent to browse or scrape while staying on approved domains, demo blocked off-domain navigation, or generate a safe browser client.
| name | WebApp UAT |
| description | User acceptance testing procedures for web applications. Use when: validating features with real users, conducting UAT sessions, or preparing for release. |
User acceptance testing framework for real-world validation.
1. UAT Plan → 2. Test Cases → 3. User Testing → 4. Bug Reports → 5. Sign-off
## UAT Plan: [Feature Name]
### Objective
Validate [feature] meets business requirements.
### Scope
- Included: [list]
- Excluded: [list]
### Test Environment
- URL: https://staging.mansoni.com
- Credentials: [provided separately]
- Test data: [seed instructions]
### Test Cases
| ID | Description | Steps | Expected Result | Priority |
|----|-------------|-------|----------------|----------|
| UAT-001 | Login flow | 1. Navigate to /login... | Success message | P1 |
### Success Criteria
- [ ] All P1 test cases pass
- [ ] No HIGH/CRITICAL bugs open
- [ ] Stakeholder sign-off received
### Schedule
- Start: [date]
- End: [date]
## Bug Report: [ID]
**Title:** [concise summary]
**Severity:** P1/P2/P3/P4
**Environment:** [browser, OS, device]
### Steps to Reproduce
1. Navigate to [page]
2. Click on [element]
3. Observe [result]
### Expected
[what should happen]
### Actual
[what happened]
### Evidence
[screenshots, logs]
### Priority to Fix
[P1/P2/P3/P4]
Key UAT scenarios: