browser-tools
Interactive browser automation via Chrome DevTools Protocol. Use when you need to interact with web pages, test frontends, or when user interaction with a visible browser is required.
Essential command-line tools and system utilities.
Interactive browser automation via Chrome DevTools Protocol. Use when you need to interact with web pages, test frontends, or when user interaction with a visible browser is required.
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
Detect visual changes in UI components using screenshot comparison. Use when detecting unintended UI changes or pixel differences. Trigger with phrases like "test visual changes", "compare screenshots", or "detect UI regressions".
Measure and improve test coverage by identifying untested code paths and prioritizing high-risk areas for testing
Analyze code coverage metrics and identify untested code paths. Use when analyzing untested code or coverage gaps. Trigger with phrases like "analyze coverage", "check test coverage", or "find untested code".
Create and execute load tests for performance validation using k6, JMeter, and Artillery. Use when validating application performance under load conditions or identifying bottlenecks. Trigger with phrases like "run load test", "create stress test", or "validate performance under load".
Browser automation, debugging, and performance analysis via Puppeteer CLI scripts. Use when you need to take screenshots of web pages, automate browser interactions, analyze Core Web Vitals, monitor network requests, scrape web content, fill forms programmatically, or debug JavaScript in page context.
Validates project wrangler version on session start, detects breaking changes, and recommends updates
Universal code generator - clones your existing code style exactly
Write, test, and update Unison code using MCP tools. Use when working with Unison language files (.u extension), UCM operations, or Unison projects. Enforces TDD with strict typechecking via development skill. Used as a part of the XP skill.
Process review comments in a file after user finishes reviewing in file-review GUI. Extracts HTML comment markers, guides Claude through addressing each comment interactively, and removes resolved markers.
Update the wrangler plugin to the latest version by clearing all caching layers. Use when user says "update yourself", "update wrangler", or after pushing changes to the wrangler repo.
Finds WHERE code lives in a codebase - locates files by topic/feature, categorizes by purpose, organizes findings. Super grep/glob/ls tool for navigating unfamiliar codebases.
Configure TypeScript for the Orient monorepo packages. Use when creating new packages, fixing build errors, configuring tsconfig.json, setting up project references, or debugging "cannot find module" errors. Covers package tsconfig templates, turbo build order, path aliases, and common build errors.
Propose code changes to the supervisor Claude. Generate diffs and rationale, but do not execute. Wait for supervisor approval.
Use BEFORE reading multiple files to understand code. Reminds you to use codebase-analyzer agent instead of manual file reading.
Detects stale documentation - outdated status markers, old TODOs, version lag
MANDATORY for all naming decisions - variables, functions, files, folders, classes, database tables, routes, CSS classes. Must be followed when creating or renaming any identifier. Non-negotiable baseline for consistent, readable names across all languages and contexts.
Use when exploring/explaining code, designing/updating architecture, or when asked to visualize structure. Shows annotated file trees inline.
Use safe-rm command to safely 'remove' files by renaming them to .obsolete instead of permanent deletion. Reversible, collision-safe, hook-compliant.