Use when implementing responsive CSS layouts: mobile-first breakpoints, container queries, fluid typography, Grid and Flexbox, and responsive images. Covers touch targets, logical properties and common overflow issues.
Installs into .claude/skills of the current project.
Are you the author of Responsive Design?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/monoes-responsive-design)
---
name: responsive-design
description: "Use when implementing responsive CSS layouts: mobile-first breakpoints, container queries, fluid typography, Grid and Flexbox, and responsive images. Covers touch targets, logical properties and common overflow issues."
tags: ["design","frontend","ui","accessibility"]
tools: ["monodesign_detect","monodesign_fix"]
license: MIT
source: https://github.com/wshobson/agents
source_path: "plugins/ui-design/skills/responsive-design"
source_commit: 4236bb91f8395b0435f1d8b8baf9e8e4c69a8620
---
# 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
