responsive-design-system
Implements responsive design systems with mobile-first breakpoints, container queries, fluid typography, and adaptive layouts using Tailwind CSS. Use when users request "responsive design", "mobile-first", "breakpoints", "fluid typography", or "adaptive layout".
What this skill does
# Responsive Design System
Build adaptive, mobile-first layouts with modern CSS features and Tailwind.
## Core Workflow
1. **Define breakpoints**: Establish responsive breakpoint system
2. **Set fluid typography**: Clamp-based responsive fonts
3. **Create layout grid**: Responsive grid system
4. **Add container queries**: Component-level responsiveness
5. **Build responsive components**: Adaptive patterns
6. **Test across devices**: Verify on all viewports
## Breakpoint System
### Tailwind Default Breakpoints
| Breakpoint | Min Width | Target Devices |
|------------|-----------|----------------|
| `sm` | 640px | Large phones (landscape) |
| `md` | 768px | Tablets |
| `lg` | 1024px | Laptops |
| `xl` | 1280px | Desktops |
| `2xl` | 1536px | Large screens |
### Custom Breakpoints
```javascript
// tailwind.config.js
module.exports = {
theme: {
screens: {
'xs': '475px',
'sm': '640px',
'md': '768px',
'lg': '1024px',
'xl': '1280px',
'2xl': '1536px',
'3xl': '1920px',
// Max-width breakpoints
'max-sm': { max: '639px' },
'max-md': { max: '767px' },
'max-lg': { max: '1023px' },
// Range breakpoints
'tablet': { min: '768px', max: '1023px' },
// Feature queries
'touch': { raw: '(hover: none) and (pointer: coarse)' },
'stylus': { raw: '(hover: none) and (pointer: fine)' },
'mouse': { raw: '(hover: hover) and (pointer: fine)' },
},
},
};
```
## Fluid Typography
### CSS Clamp Function
```css
/* globals.css */
:root {
/* Fluid type scale: min, preferred, max */
--text-xs: clamp(0.75rem, 0.7rem + 0.25vw, 0.875rem);
--text-sm: clamp(0.875rem, 0.8rem + 0.35vw, 1rem);
--text-base: clamp(1rem, 0.9rem + 0.5vw, 1.125rem);
--text-lg: clamp(1.125rem, 1rem + 0.6vw, 1.25rem);
--text-xl: clamp(1.25rem, 1.1rem + 0.75vw, 1.5rem);
--text-2xl: clamp(1.5rem, 1.2rem + 1.5vw, 2rem);
--text-3xl: clamp(1.875rem, 1.4rem + 2.25vw, 2.5rem);
--text-4xl: clamp(2.25rem, 1.5rem + 3.75vw, 3.5rem);
--text-5xl: clamp(3rem, 1.8rem + 6vw, 5rem);
/* Fluid spacing */
--space-xs: clamp(0.25rem, 0.2rem + 0.25vw, 0.5rem);
--space-sm: clamp(0.5rem, 0.4rem + 0.5vw, 0.75rem);
--space-md: clamp(1rem, 0.8rem + 1vw, 1.5rem);
--space-lg: clamp(1.5rem, 1rem + 2.5vw, 3rem);
--space-xl: clamp(2rem, 1.2rem + 4vw, 5rem);
}
```
### Tailwind Fluid Typography
```javascript
// tailwind.config.js
const plugin = require('tailwindcss/plugin');
module.exports = {
theme: {
extend: {
fontSize: {
'fluid-xs': 'clamp(0.75rem, 0.7rem + 0.25vw, 0.875rem)',
'fluid-sm': 'clamp(0.875rem, 0.8rem + 0.35vw, 1rem)',
'fluid-base': 'clamp(1rem, 0.9rem + 0.5vw, 1.125rem)',
'fluid-lg': 'clamp(1.125rem, 1rem + 0.6vw, 1.25rem)',
'fluid-xl': 'clamp(1.25rem, 1.1rem + 0.75vw, 1.5rem)',
'fluid-2xl': 'clamp(1.5rem, 1.2rem + 1.5vw, 2rem)',
'fluid-3xl': 'clamp(1.875rem, 1.4rem + 2.25vw, 2.5rem)',
'fluid-4xl': 'clamp(2.25rem, 1.5rem + 3.75vw, 3.5rem)',
'fluid-5xl': 'clamp(3rem, 1.8rem + 6vw, 5rem)',
},
},
},
};
```
### Usage
```html
<h1 class="text-fluid-4xl font-bold">Responsive Headline</h1>
<p class="text-fluid-base">Body text that scales smoothly.</p>
```
## Container Queries
### Enable Container Queries
```javascript
// tailwind.config.js
module.exports = {
theme: {
extend: {
containers: {
'xs': '320px',
'sm': '384px',
'md': '448px',
'lg': '512px',
'xl': '576px',
'2xl': '672px',
},
},
},
};
```
### Container Query Usage
```html
<!-- Define container -->
<div class="@container">
<!-- Respond to container size, not viewport -->
<div class="flex flex-col @md:flex-row @lg:gap-8">
<div class="@md:w-1/2">
<h2 class="text-lg @lg:text-2xl">Card Title</h2>
</div>
<div class="@md:w-1/2">
<p class="text-sm @lg:text-base">Card content</p>
</div>
</div>
</div>
<!-- Named containers -->
<div class="@container/main">
<div class="@lg/main:grid-cols-3">...</div>
</div>
```
### Responsive Card Component
```tsx
// components/ResponsiveCard.tsx
export function ResponsiveCard({ title, description, image }: CardProps) {
return (
<article className="@container">
<div className="flex flex-col @sm:flex-row gap-4 p-4 bg-white rounded-lg shadow">
<img
src={image}
alt=""
className="w-full @sm:w-32 @md:w-48 h-32 @sm:h-auto object-cover rounded"
/>
<div className="flex-1">
<h3 className="text-lg @md:text-xl font-semibold">{title}</h3>
<p className="text-sm @md:text-base text-gray-600 mt-2">
{description}
</p>
<button className="mt-4 px-4 py-2 bg-blue-500 text-white rounded @md:px-6">
Learn More
</button>
</div>
</div>
</article>
);
}
```
## Responsive Grid Layouts
### Auto-Fit Grid
```html
<!-- Cards that automatically adjust columns -->
<div class="grid grid-cols-1 sm:grid-cols-2 lg:grid-cols-3 xl:grid-cols-4 gap-6">
<!-- Cards -->
</div>
<!-- CSS Grid auto-fit -->
<div class="grid gap-6" style="grid-template-columns: repeat(auto-fit, minmax(280px, 1fr))">
<!-- Cards automatically fit -->
</div>
```
### Dashboard Layout
```tsx
// components/DashboardLayout.tsx
export function DashboardLayout({ sidebar, main }: LayoutProps) {
return (
<div className="min-h-screen flex flex-col lg:flex-row">
{/* Sidebar: Full width on mobile, fixed width on desktop */}
<aside className="w-full lg:w-64 xl:w-80 bg-gray-900 text-white">
<div className="p-4 lg:sticky lg:top-0">{sidebar}</div>
</aside>
{/* Main content */}
<main className="flex-1 p-4 md:p-6 lg:p-8">
<div className="max-w-7xl mx-auto">{main}</div>
</main>
</div>
);
}
```
### Holy Grail Layout
```tsx
export function HolyGrailLayout({ header, sidebar, main, aside, footer }: LayoutProps) {
return (
<div className="min-h-screen grid grid-rows-[auto_1fr_auto]">
<header className="bg-white border-b px-4 py-3">
{header}
</header>
<div className="grid grid-cols-1 md:grid-cols-[240px_1fr] lg:grid-cols-[240px_1fr_240px]">
<aside className="hidden md:block bg-gray-50 p-4 border-r">
{sidebar}
</aside>
<main className="p-4 md:p-6 overflow-auto">
{main}
</main>
<aside className="hidden lg:block bg-gray-50 p-4 border-l">
{aside}
</aside>
</div>
<footer className="bg-gray-900 text-white px-4 py-6">
{footer}
</footer>
</div>
);
}
```
## Responsive Images
### Srcset and Sizes
```html
<img
src="/images/hero-800.jpg"
srcset="
/images/hero-400.jpg 400w,
/images/hero-800.jpg 800w,
/images/hero-1200.jpg 1200w,
/images/hero-1600.jpg 1600w
"
sizes="(max-width: 640px) 100vw,
(max-width: 1024px) 75vw,
50vw"
alt="Hero image"
class="w-full h-auto"
/>
```
### Next.js Image
```tsx
import Image from 'next/image';
export function ResponsiveImage({ src, alt }: ImageProps) {
return (
<div className="relative aspect-video w-full">
<Image
src={src}
alt={alt}
fill
sizes="(max-width: 640px) 100vw,
(max-width: 1024px) 75vw,
50vw"
className="object-cover"
/>
</div>
);
}
```
### Art Direction with Picture
```html
<picture>
<!-- Mobile: Square crop -->
<source
media="(max-width: 639px)"
srcset="/images/hero-mobile.jpg"
/>
<!-- Tablet: 4:3 crop -->
<source
media="(max-width: 1023px)"
srcset="/images/hero-tablet.jpg"
/>
<!-- Desktop: Wide crop -->
<img
src="/images/hero-desktop.jpg"
alt="Hero"
class="w-full h-auto"
/>
</picture>
```
## Responsive Navigation
### Mobile Menu Pattern
```tsx
'use client';
import { useState } from 'react';
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.