dev-tools-skill
Use when the user says "use the DevTools skill" or when they need help debugging a web app with Chrome DevTools MCP (UI bugs, incorrect behavior, console errors, network/API failures, or performance/lag), especially if the user seems inexperienced and needs guided, step-by-step diagnosis.
What this skill does
# Dev Tools Skill ## Overview Use the Chrome DevTools MCP server to diagnose and fix frontend issues by observing the live page, gathering evidence (console, network, performance), and proposing targeted code changes. ## Quick Start 1. Confirm the user wants DevTools used (or they already asked). 2. Open the target page, then take an a11y snapshot. 3. Triage via console + network + quick DOM inspection. 4. Choose the appropriate workflow below and follow it end-to-end. 5. Summarize findings + propose the smallest safe fix. ## Workflow Decision Tree - **UI/interaction bug** (layout, hover/click, missing text): use *UI/Interaction Workflow*. - **Performance/lag** (slow load, jank, long TTI): use *Performance Workflow*. - **API/network issue** (failed fetch, wrong data): use *Network Workflow*. - **Runtime error** (crash, blank screen, stack trace): use *Console/Error Workflow*. ## Core Workflows ### 1) Triage (always first) - Capture state: `list_pages` → `select_page` → `take_snapshot`. - Scan for visible errors (missing sections, broken layout) in snapshot text. - Check console messages (`list_console_messages`, then `get_console_message` for details). - Check network requests (`list_network_requests`, then `get_network_request` for errors/slow calls). - Form a hypothesis and select a workflow below. ### 2) UI/Interaction Workflow - Use `take_snapshot` to locate the target element; if unclear, `take_screenshot`. - Inspect element text/attributes via `evaluate_script` (read-only DOM queries). - Reproduce the issue with `click`, `hover`, or `press_key`. - If layout is involved, measure box sizes/positions via `evaluate_script`. - Propose minimal CSS/JS fixes; if unsure, ask 1 targeted question. ### 3) Performance Workflow - Run a trace: `performance_start_trace` (reload=true) → reproduce → `performance_stop_trace`. - Identify top issue via `performance_analyze_insight`. - Correlate with network timings and large asset loads. - Recommend fixes: reduce bundle size, defer non-critical JS, optimize images, avoid layout thrash. ### 4) Network Workflow - List requests and find failures/slow endpoints. - Open failing request details (`get_network_request`), capture status, timing, payload. - Cross-check console for CORS or runtime fetch errors. - Suggest fixes: endpoint URL, headers/auth, payload shape, caching, retries. ### 5) Console/Error Workflow - Read console errors and stack traces in full. - Identify the first failing module/function; map to code location if possible. - Confirm if error is user-triggered vs load-time. - Suggest smallest code change + safe rollback steps. ## UX & Safety Rules - Explain actions in plain language; assume the user is less experienced. - Avoid submitting forms or destructive actions without explicit user confirmation. - Keep fixes minimal and reversible; call out any risk. ## References - See `references/mcp-cheatsheet.md` for MCP command usage. - See `references/debug-workflows.md` for detailed steps and examples. - See `references/performance.md` for perf triage patterns. - See `references/network.md` for network debugging patterns. - See `references/ui-debug.md` for DOM/layout debugging tips.
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.