responsive design
- Repo stars 36,312
- Author repo agents
- Domain
- Design
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @wshobson · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No explicit requirements detected
- Detected file/system behavior
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
# Detailed patterns and worked examples
Detailed pattern documentation lives in `references/details.md`. Read that file when the navigation tier above is insufficient.
# Responsive Design
Master modern responsive design techniques to create interfaces that adapt seamlessly across all screen sizes and device contexts.
## When to Use This Skill
- Implementing mobile-first responsive layouts
- Using container queries for component-based responsiveness
- Creating fluid typography and spacing scales
- Building complex layouts with CSS Grid and Flexbox
- Designing breakpoint strategies for design systems
- Implementing responsive images and media
- Creating adaptive navigation patterns
- Building responsive tables and data displays
## Detailed patterns and worked examples
Detailed pattern documentation lives in `references/details.md`. Read that file when the navigation tier above is insufficient.
## Best Practices
1. **Mobile-First**: Start with mobile styles, enhance for larger screens
2. **Content Breakpoints**: Set breakpoints based on content, not devices
3. **Fluid Over Fixed**: Use fluid values for typography and spacing
4. **Container Queries**: Use for component-level responsiveness
5. **Test Real Devices**: Simulators don't catch all issues
6. **Performance**: Optimize images, lazy load off-screen content
7. **Touch Targets**: Maintain 44x44px minimum on mobile
8. **Logical Properties**: Use inline/block for internationalization
## Common Issues
- **Horizontal Overflow**: Content breaking out of viewport
- **Fixed Widths**: Using px instead of relative units
- **Viewport Height**: 100vh issues on mobile browsers
- **Font Size**: Text too small on mobile
- **Touch Targets**: Buttons too small to tap accurately
- **Aspect Ratio**: Images squishing or stretching
- **Z-Index Stacking**: Overlays breaking on different screens
Sections and files
Listed in source order.
sections -> When to Use This Skill → Detailed patterns and worked examples → Best Practices → Common Issues
terms -> Mobile-First · Content Breakpoints · Fluid Over Fixed · Container Queries · Test Real Devices · Performance · Touch Targets · Logical Properties
files/cmd -> references/details.md · inline/block
body sha256 -> 42aef05cea2a
When to Use This Skill
Implementing mobile-first responsive layouts Using container queries for component-based responsiveness Creating fluid typography and spacing scales Building complex layouts with CSS Grid and Flexbox Designing breakpoint strategies for design systems
Detailed patterns and worked examples
Detailed pattern documentation lives in
references/details.md. Read that file when the navigation tier above is insufficient.Best Practices
Mobile-First: Start with mobile styles, enhance for larger screens Content Breakpoints: Set breakpoints based on content, not devices Fluid Over Fixed: Use fluid values for typography and spacing Container Queries: Use for component-level responsiveness Test Real Devices: Simulators don't catch all issues
Common Issues
Horizontal Overflow: Content breaking out of viewport Fixed Widths: Using px instead of relative units Viewport Height: 100vh issues on mobile browsers Font Size: Text too small on mobile Touch Targets: Buttons too small to tap accurately