responsive-design-tester
Tests a page across a six-device viewport matrix (Mobile S/M/L, Tablet, Desktop, Ultrawide). For each viewport captures a screenshot, detects active CSS media queries, checks horizontal overflow, validates touch targets (min 48x48), font readability (min 16px body), viewport meta tag, and image srcset/sizes. Produces a comparison table with per-viewport issue counts.
What this skill does
# Responsive Design Tester
Run a full responsive design audit across six viewports. At each breakpoint the
skill captures layout screenshots, measures interactive element sizes, checks
font readability, detects horizontal overflow, and validates responsive image
markup.
## When to Use
- Before shipping a new page or component to verify cross-device rendering.
- Diagnosing layout issues reported on specific device widths.
- Auditing touch-target compliance with WCAG 2.5.8 / Material guidelines.
- Checking that images serve appropriate sizes via srcset/sizes.
- Verifying the viewport meta tag is present and correct.
## Prerequisites
- **Playwright MCP server** connected and responding (all `mcp__playwright__browser_*` tools available).
- **Chromium-based browser** recommended for full `matchMedia` and CDP touch emulation support.
- Target page must be reachable from the browser instance.
## Viewport Matrix
| Name | Width | Height | Type |
|------------|-------|--------|---------|
| Mobile S | 320 | 568 | Mobile |
| Mobile M | 375 | 667 | Mobile |
| Mobile L | 425 | 812 | Mobile |
| Tablet | 768 | 1024 | Tablet |
| Desktop | 1440 | 900 | Desktop |
| Ultrawide | 2560 | 1080 | Desktop |
## Workflow
Repeat Steps 1 through 9 for each viewport in the matrix above.
### Step 1 -- Resize the Viewport
Call `browser_resize` with the current viewport dimensions.
```
browser_resize({ width: 320, height: 568 })
```
### Step 2 -- Enable Touch Emulation (Mobile Viewports Only)
For Mobile S, Mobile M, and Mobile L viewports, enable touch emulation via CDP
so the page receives touch events and may activate mobile-specific styles.
```javascript
browser_run_code({
code: `async (page) => {
const client = await page.context().newCDPSession(page);
await client.send('Emulation.setTouchEmulationEnabled', {
enabled: true,
maxTouchPoints: 5
});
return 'Touch emulation enabled';
}`
})
```
For Tablet, Desktop, and Ultrawide viewports, disable touch emulation:
```javascript
browser_run_code({
code: `async (page) => {
const client = await page.context().newCDPSession(page);
await client.send('Emulation.setTouchEmulationEnabled', {
enabled: false
});
return 'Touch emulation disabled';
}`
})
```
### Step 3 -- Navigate to the Target Page
Call `browser_navigate` to load the page fresh at this viewport size so that
media queries are evaluated during load.
```
browser_navigate({ url: "<target_url>" })
```
Wait for the page to settle:
```
browser_wait_for({ time: 2 })
```
### Step 4 -- Validate Viewport Meta Tag
Check that the page has a proper viewport meta tag for responsive rendering.
```javascript
browser_evaluate({
function: `() => {
const meta = document.querySelector('meta[name="viewport"]');
if (!meta) {
return { present: false, content: null, issues: ['Missing <meta name="viewport"> tag'] };
}
const content = meta.getAttribute('content') || '';
const issues = [];
if (!content.includes('width=device-width')) {
issues.push('Missing width=device-width');
}
if (!content.includes('initial-scale')) {
issues.push('Missing initial-scale');
}
if (content.includes('maximum-scale=1') || content.includes('user-scalable=no')) {
issues.push('Zoom disabled -- accessibility concern (WCAG 1.4.4)');
}
return { present: true, content, issues };
}`
})
```
### Step 5 -- Detect Active CSS Media Queries
Determine which common breakpoint media queries are currently active.
```javascript
browser_evaluate({
function: `() => {
const queries = [
'(max-width: 320px)',
'(max-width: 375px)',
'(max-width: 425px)',
'(max-width: 480px)',
'(max-width: 576px)',
'(max-width: 640px)',
'(max-width: 768px)',
'(max-width: 1024px)',
'(max-width: 1200px)',
'(max-width: 1440px)',
'(min-width: 320px)',
'(min-width: 576px)',
'(min-width: 768px)',
'(min-width: 1024px)',
'(min-width: 1200px)',
'(min-width: 1440px)',
'(min-width: 1920px)',
'(prefers-color-scheme: dark)',
'(prefers-reduced-motion: reduce)',
'(orientation: portrait)',
'(orientation: landscape)',
'(hover: hover)',
'(hover: none)',
'(pointer: fine)',
'(pointer: coarse)'
];
const active = [];
const inactive = [];
for (const q of queries) {
if (window.matchMedia(q).matches) {
active.push(q);
} else {
inactive.push(q);
}
}
return {
viewportWidth: window.innerWidth,
viewportHeight: window.innerHeight,
devicePixelRatio: window.devicePixelRatio,
activeQueries: active,
inactiveQueries: inactive
};
}`
})
```
### Step 6 -- Check Horizontal Overflow
Detect whether any content overflows the viewport horizontally, which causes
unwanted horizontal scrolling on mobile devices.
```javascript
browser_evaluate({
function: `() => {
const docWidth = document.documentElement.scrollWidth;
const viewportWidth = window.innerWidth;
const hasOverflow = docWidth > viewportWidth;
// Find overflowing elements
const overflowing = [];
if (hasOverflow) {
const all = document.querySelectorAll('*');
for (const el of all) {
const rect = el.getBoundingClientRect();
if (rect.right > viewportWidth + 1 || rect.left < -1) {
const tag = el.tagName.toLowerCase();
const id = el.id ? '#' + el.id : '';
const cls = el.className && typeof el.className === 'string'
? '.' + el.className.trim().split(/\\s+/).slice(0, 2).join('.')
: '';
overflowing.push({
element: tag + id + cls,
left: Math.round(rect.left),
right: Math.round(rect.right),
width: Math.round(rect.width),
overflowPx: Math.round(Math.max(0, rect.right - viewportWidth) + Math.max(0, -rect.left))
});
}
}
// Deduplicate: keep only elements that are not ancestors of smaller overflowing elements
overflowing.sort((a, b) => b.overflowPx - a.overflowPx);
}
return {
documentWidth: docWidth,
viewportWidth,
hasHorizontalOverflow: hasOverflow,
overflowPx: Math.max(0, docWidth - viewportWidth),
overflowingElements: overflowing.slice(0, 15)
};
}`
})
```
### Step 7 -- Validate Touch Targets
Check that all interactive elements meet the minimum 48x48px touch target
size recommended by Material Design and WCAG 2.5.8.
```javascript
browser_evaluate({
function: `() => {
const MIN_SIZE = 48;
const interactive = document.querySelectorAll(
'a, button, input, select, textarea, [role="button"], [role="link"], ' +
'[role="checkbox"], [role="radio"], [role="tab"], [onclick], [tabindex]'
);
const results = { total: 0, passing: 0, failing: 0, failures: [] };
const seen = new Set();
for (const el of interactive) {
// Skip hidden elements
const style = window.getComputedStyle(el);
if (style.display === 'none' || style.visibility === 'hidden' || style.opacity === '0') continue;
const rect = el.getBoundingClientRect();
if (rect.width === 0 && rect.height === 0) continue;
results.total++;
const w = Math.round(rect.width);
const h = Math.round(rect.height);
if (w >= MIN_SIZE && h >= MIN_SIZE) {
results.passing++;
} else {
results.failing++;
const tag = el.tagName.toLowerCase();
const id = el.id ? '#' + el.id : '';
const text = (el.textContent || '').trim().substring(0, 30);
const key = tag + id + w + 'x' + h;
if (!seen.has(key)) {
seen.add(key);
results.failures.push({
element: tag + id,
text: text || null,
width: w,
height: h,
isRelated 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.