responsive-design

Implements fluid layouts, content-driven breakpoints, and container queries for adaptive web interfaces.

1|Updated Sep 11, 2026
One-click install
npx skills add https://github.com/rebuildup/my-web-2026 --skill responsive-design-rebuildup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: responsive-design
Source: https://github.com/rebuildup/my-web-2026/tree/main/skills/responsive-design
Command: npx skills add https://github.com/rebuildup/my-web-2026 --skill responsive-design-rebuildup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Building interfaces that only work at a few fixed device widths leads to broken layouts at intermediate sizes, zoom levels, and unexpected content lengths. This Skill replaces device-preset thinking with a systematic workflow for making web UIs adapt naturally to any viewport, container, zoom level, or input environment. ## Core Features & Use Cases - Content-driven breakpoint discovery: Start fluid from narrow widths, find stress points by continuously resizing, and add discrete breakpoints only where content actually demands transformation. - Media query vs container query guidance: Use media queries for page-level and environmental changes, and container queries for reusable components that must adapt to their allocated width. - Structured verification checklist: Validate reflow at 320 CSS px, 400% zoom, long localized text, intermediate widths, and keyboard/reading order consistency. - Use Case: When a card component breaks inside a narrow sidebar despite working full-width, apply container queries so the component adapts to its own available space instead of the viewport. ## Quick Start Ask the AI to review a page or component for responsive behavior and implement fluid layout fixes with content-driven breakpoints and container queries where needed.

Frequently Asked Questions about responsive-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose breakpoints for responsive web design?

Choose breakpoints from content stress points, not device names. Start narrow with fluid layout, widen the viewport continuously, and add a breakpoint only where the layout, typography, or controls visibly break down.

When should I use container queries instead of media queries?

Use container queries when a reusable component must adapt to the width allocated to it, such as cards, widgets, or toolbar groups in sidebars. Use media queries for page-level changes like global shells, navigation, orientation, and user preferences.

How do I fix horizontal overflow on mobile layouts?

First classify the overflow as accidental or semantic. Accidental overflow from fixed widths, unbreakable text, or oversized media should be fixed with fluid sizing; semantic 2D surfaces like data tables may use internal scroll with visible scrollbars.

Does responsive design require separate mobile and desktop DOMs?

No. Duplicating DOM per device is discouraged. Prefer reflow, repositioning, disclosure patterns, and container queries so one structure adapts, keeping visual order consistent with keyboard and screen-reader order.

How do I test responsive layouts beyond device presets?

Resize continuously from minimum to wide widths, check breakpoint edges and intermediate sizes, test 320 CSS px and 400% zoom per WCAG reflow criteria, and inject long localized text and dynamic data to expose stress points.