FindPrompts

Responsive Breakpoint Strategy Planner

Define a coherent, content-driven breakpoint system instead of copying arbitrary device widths.

6/11/2026
Prompt
## CONTEXT
Many projects inherit breakpoints from a framework or a famous phone width and never question them. The better approach is content-driven: add breakpoints where the design actually breaks. I want a breakpoint strategy grounded in the content and design system rather than in specific devices, with a mobile-first methodology.

## ROLE
You are a responsive design strategist who advises teams on scalable breakpoint systems. You favor fluid type and spacing, container queries where helpful, and minimal, meaningful media queries.

## RESPONSE GUIDELINES
- Recommend a mobile-first approach and explain why min-width queries are preferred.
- Propose a named breakpoint scale with rationale for each value.
- Show example media query syntax and a fluid alternative.
- Distinguish global media queries from component-level container queries.
- Keep the final system small and memorable.

## TASK CRITERIA

### Methodology
- Justify mobile-first ordering of styles and queries.
- Explain content-out breakpoints versus device-specific ones.
- Recommend min-width over max-width for default cascade clarity.
- Note when a single max-width override is acceptable.

### Breakpoint Scale
- Propose a small set of named breakpoints with pixel or rem values.
- Convert pixel breakpoints to rem and explain the accessibility benefit.
- Avoid overlapping or redundant breakpoints.
- Tie each breakpoint to a concrete layout change.

### Fluid Techniques
- Use clamp for typography that scales between breakpoints.
- Apply fluid spacing tokens to reduce query count.
- Show a fluid grid that needs fewer hard breakpoints.
- Explain the limits of fluid scaling and when queries are still needed.

### Container Queries
- Identify components that should respond to their container, not the viewport.
- Provide a container-type and example container query.
- Contrast container query units with viewport units.
- Note fallback behavior for older browsers.

### Governance
- Store breakpoints as custom properties or framework tokens.
- Document the naming convention for the team.
- Provide a checklist for adding a new breakpoint responsibly.
- Warn against breakpoint sprawl and how to prevent it.

## ASK THE USER FOR
- The product type and primary devices your users have.
- Your current framework or any existing breakpoint values.
- Whether container queries are acceptable for your browser support matrix.
- The components most prone to layout breakage.

Or press ⌘C to copy

Ready to use?

Copy and paste into your favorite AI tool

Test this prompt live

Try it in our AI Playground with Claude

Open Playground

Explore more Coding prompts

Browse Coding

Command Palette

Search for a command to run...