browser-verification
Automatically verify UI changes in a real browser after implementation. Integrated into the /work workflow — checks visual elements, interactions, and console errors using Playwright. Not a standalone skill.
What this skill does
# Browser Verification Skill
Automatically verify UI changes in a real browser after implementation.
## When This Skill Is Used
This skill is triggered during the `/work` workflow after the implementer completes a task that modifies UI-related files. It is NOT a standalone skill - it's integrated into the work loop.
## Purpose
Catch visual and functional issues before code review by testing in a real browser. This prevents:
- CSS issues that look fine in code but break in browser
- JavaScript errors that only appear at runtime
- Responsive/layout issues
- Missing visual elements
## Testability Checks
Browser verification only runs when ALL three conditions are met:
### 1. Browser Tools Available
Must have either:
- Playwright MCP tools (`mcp__plugin_playwright_*`)
- Chrome Extension tools (`mcp__claude-in-chrome__*`)
### 2. Server Running
Must have an HTTP server on a dev port (3000-8999) or ability to start one via package.json scripts.
### 3. Renderable Files Changed
Task must have modified files that affect browser output:
- `.html`, `.css`, `.scss`, `.less`
- `.tsx`, `.jsx`, `.vue`, `.svelte`
- Template files (`.hbs`, `.ejs`, `.pug`)
- Files in `components/`, `views/`, `ui/`, `pages/`
If any condition fails, verification is silently skipped.
## Verification Process
1. **Navigate** to the development server
2. **Screenshot** the initial state
3. **Analyze** the page snapshot for expected elements
4. **Test interactions** if the task involves interactive behavior
5. **Check console** for JavaScript errors
6. **Report** pass/fail with evidence
## Advisory Behavior
This is NOT a hard gate. If verification suggests issues but the user believes the implementation is correct:
- User can provide a reason for skipping
- Skip reason is logged in task notes
- Work continues to spec review with warning flag
## Configuration
Projects can customize in `.pokayokay.json`:
```json
{
"browserVerification": {
"enabled": true,
"portRange": [3000, 9999],
"additionalPaths": ["src/templates/"],
"excludePaths": ["src/email-templates/"]
}
}
```
## Reference Documents
- `references/testability-detection.md` - How to determine if verification should run
- `references/verification-flow.md` - Step-by-step verification process
- `references/configuration.md` - Project-level configuration options
## Integration Point
```
yokay-implementer → browser-verify → yokay-spec-reviewer → yokay-quality-reviewer → complete
```
Browser verification runs AFTER implementation and BEFORE spec review.
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.