About responsive-design
A design skill for creating interfaces that adapt across devices and contexts, covering layouts, breakpoints, input methods, typography, and images. It is intended for design work that plans and checks experiences across screen sizes.
Key features
- 01Plan fluid and adaptive layouts
- 02Apply mobile-first or content-first strategies
- 03Choose breakpoints and responsive patterns
- 04Adapt to touch, mouse, keyboard, and voice
- 05Adjust responsive typography and images
Use cases
- 01Plan phone, tablet, and desktop layouts
- 02Reflow content for different screen sizes
- 03Check accessibility at each breakpoint
Install
Copy the command and run it in a terminal.
$
npx skills add https:/After installing, type/responsive-designin Claude Code to confirm it loaded.
Details
From the project READMEResponsive Design
You are an expert in designing interfaces that adapt gracefully across devices and contexts.
What You Do
You design adaptive layouts and interactions that work across all screen sizes, pixel densities, and input methods.
Responsive Strategies
- Fluid: Percentage-based widths, flexible within ranges
- Adaptive: Distinct layouts at specific breakpoints
- Mobile-first: Start with smallest, enhance upward
- Content-first: Let content needs drive breakpoints
Common Breakpoints
- Small: 375-639px (phones)
- Medium: 640-1023px (tablets)
- Large: 1024-1439px (laptops)
- Extra large: 1440px+ (desktops)
Responsive Patterns
- Column drop: reduce columns at smaller sizes
- Reflow: stack horizontal elements vertically
- Off-canvas: hide secondary content behind toggle
- Priority+: show most important, overflow the rest
Input Method Adaptation
- Touch: 44px minimum targets, gesture support
- Mouse: hover states, precise targeting
- Keyboard: focus indicators, logical tab order
- Voice: clear labels, logical structure
Responsive Typography and Images
- Fluid type scaling between breakpoints
- Responsive images with appropriate srcset
- Art direction: different crops per breakpoint
Best Practices
- Design for content, not devices
- Test on real devices, not just browser resize
- Consider landscape and portrait
- Account for slow connections
- Test with accessibility tools at each breakpoint
Comments
Markdown supported