# Restore the missing responsive breakpoints on one screen

A screen that only works at the width it was designed at, corrected at each supported breakpoint.

Category: Design system and UI
Source: https://letsship.ai/use-cases/restore-missing-responsive-breakpoints
Published: 2026-08-25

## Goal

Make one screen work at every supported breakpoint.

## Acceptance criteria

- The screen is usable at each supported breakpoint
- Screenshots at each are attached
- No horizontal scrolling appears on the page body
- Layout uses the project's existing responsive conventions

## What lands as proof

A screenshot per breakpoint, which is the only way to show the layout holds rather than merely that it compiles.

## Prompt

Copy this to an agent to open the ticket:

```text
Create a Linear issue in my team and assign it to the SHIP agent.

Title: Fix the responsive layout of {screen}

Description: Make one screen work at every supported breakpoint.

Acceptance criteria:
- The screen is usable at each supported breakpoint
- Screenshots at each are attached
- No horizontal scrolling appears on the page body
- Layout uses the project's existing responsive conventions

Before you create the issue, open this repository's screens at a narrow width, find the worst one, and replace {screen} with it.
```

## Questions

### What does the agent actually change?

The ticket is scoped to one outcome: make one screen work at every supported breakpoint. Work that serves that outcome is in scope, and anything outside it is left for a separate ticket, so the pull request stays reviewable.

### How do I know the work is done?

The pull request carries the evidence, not only the diff. Here that means screenshots at each breakpoint in the pull request, so a reviewer can confirm the result without reproducing the work locally.

### How much oversight does this need?

The run stops once the plan is written. Somebody reads the approach and approves it before any code exists, which is the cheapest moment to redirect the work.