browser-devtools-mcp
Integrating Chrome DevTools and browser automation via MCP for live UI inspection, screenshot-to-code workflows, and visual debugging. Bridges the gap between design and implementation.
What this skill does
# Browser DevTools MCP Integration
Leverage browser automation and DevTools through MCP (Model Context Protocol) for live UI inspection, screenshot-to-code workflows, and visual debugging. This skill enables direct observation and manipulation of running interfaces.
---
## When to Use This Skill
- Capturing screenshots of live UIs for analysis
- Inspecting CSS and computed styles programmatically
- Implementing screenshot-to-code workflows
- Debugging layout issues with visual feedback
- Extracting design tokens from existing sites
- Automating visual regression testing
- Building live preview workflows
---
## MCP Architecture Overview
### What is MCP?
Model Context Protocol (MCP) is Anthropic's standard for connecting LLMs to external tools. It provides:
- **Standardized tool interface** - Consistent way to expose capabilities
- **Bidirectional communication** - Tools can query the model
- **Stateful sessions** - Maintain context across interactions
- **Permission boundaries** - Control what tools can do
### Browser MCP Landscape
```
+-------------------+ +-------------------+ +-------------------+
| Playwright MCP | | Puppeteer MCP | | Chrome DevTools |
| (Full browser) | | (Headless) | | Protocol (CDP) |
+-------------------+ +-------------------+ +-------------------+
| | |
+-----------+-------------+-----------+-------------+
| |
+------v------+ +------v------+
| Screenshot | | Element |
| Capture | | Inspection |
+-------------+ +-------------+
| |
+------v------+ +------v------+
| Visual | | Style |
| Comparison | | Extraction |
+-------------+ +-------------+
```
---
## Core MCP Tools for UI Work
### Available Browser MCP Tools
When using Playwright MCP (common in Claude Code):
```typescript
// Navigation and page control
mcp__playwright__browser_navigate({ url: string })
mcp__playwright__browser_navigate_back()
mcp__playwright__browser_close()
mcp__playwright__browser_resize({ width: number, height: number })
// Screenshots and visual capture
mcp__playwright__browser_take_screenshot({
filename?: string,
fullPage?: boolean,
type?: "png" | "jpeg",
element?: string, // Human-readable description
ref?: string // Element reference from snapshot
})
// Accessibility snapshots (better than screenshots for structure)
mcp__playwright__browser_snapshot({
filename?: string // Optional: save to file
})
// Interactions
mcp__playwright__browser_click({ element: string, ref: string })
mcp__playwright__browser_type({ element: string, ref: string, text: string })
mcp__playwright__browser_hover({ element: string, ref: string })
// Form handling
mcp__playwright__browser_fill_form({ fields: FormField[] })
// Evaluation
mcp__playwright__browser_evaluate({ function: string, element?: string, ref?: string })
// Tab management
mcp__playwright__browser_tabs({ action: "list" | "new" | "close" | "select" })
```
---
## Screenshot-to-Code Workflows
### Workflow 1: Direct Screenshot Analysis
Capture and analyze a live UI for recreation:
```python
class ScreenshotToCodeWorkflow:
"""
Convert a screenshot of a UI into working code.
"""
async def capture_and_analyze(self, url: str) -> CodeOutput:
# Step 1: Navigate to target
await mcp.browser_navigate(url=url)
# Step 2: Wait for full render
await mcp.browser_wait_for(time=2)
# Step 3: Take high-quality screenshot
screenshot = await mcp.browser_take_screenshot(
filename="capture.png",
fullPage=False,
type="png"
)
# Step 4: Get accessibility snapshot for structure
snapshot = await mcp.browser_snapshot()
# Step 5: Analyze with vision + structure
analysis = await self.analyze_screenshot(screenshot, snapshot)
# Step 6: Generate code
code = await self.generate_code(analysis)
return code
async def analyze_screenshot(self, screenshot: str, snapshot: str) -> UIAnalysis:
"""
Combine visual and structural analysis.
"""
prompt = f"""
Analyze this UI screenshot and accessibility snapshot.
## Accessibility Snapshot (Structure)
{snapshot}
## Analysis Tasks
1. **Layout Structure**
- Identify major sections (header, sidebar, main, footer)
- Determine grid/flexbox patterns
- Note responsive breakpoint hints
2. **Visual Elements**
- Extract color palette (background, text, accent)
- Identify typography (font family, sizes, weights)
- Note spacing patterns
3. **Components**
- List all UI components visible
- Describe their visual treatment
- Note interactive elements
4. **Design System Inference**
- What design system might this be based on?
- What are the governing principles?
Output as structured JSON.
"""
return await self.llm.analyze_image(screenshot, prompt)
```
### Workflow 2: Element-Specific Extraction
Extract and recreate specific elements:
```python
class ElementExtractionWorkflow:
"""
Extract and recreate specific UI elements.
"""
async def extract_element(self, url: str, selector: str) -> ElementCode:
# Navigate to page
await mcp.browser_navigate(url=url)
# Get page snapshot to find element
snapshot = await mcp.browser_snapshot()
# Find element reference in snapshot
ref = self.find_element_ref(snapshot, selector)
# Take element-specific screenshot
element_screenshot = await mcp.browser_take_screenshot(
element=f"Target element: {selector}",
ref=ref
)
# Extract computed styles via evaluation
styles = await mcp.browser_evaluate(
function="""
(element) => {
const computed = window.getComputedStyle(element);
return {
display: computed.display,
flexDirection: computed.flexDirection,
padding: computed.padding,
margin: computed.margin,
backgroundColor: computed.backgroundColor,
color: computed.color,
fontSize: computed.fontSize,
fontWeight: computed.fontWeight,
borderRadius: computed.borderRadius,
boxShadow: computed.boxShadow,
};
}
""",
element=f"Target element: {selector}",
ref=ref
)
# Generate code from extracted data
return await self.generate_element_code(element_screenshot, styles)
```
### Workflow 3: Design Token Extraction
Extract design tokens from a live site:
```python
class TokenExtractionWorkflow:
"""
Extract design tokens from a live website.
"""
async def extract_tokens(self, url: str) -> DesignTokens:
await mcp.browser_navigate(url=url)
# Extract colors from key elements
colors = await mcp.browser_evaluate(
function="""
() => {
const elements = document.querySelectorAll(
'button, a, h1, h2, h3, p, [class*="bg-"], [class*="text-"]'
);
const colors = new Set();
elements.forEach(el => {
const style = window.getComputedStyle(el);
colors.add(style.color);
colors.addRelated 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.