Layout composition

Layout Composition

Concept of the skill

Layout composition is the discipline of assigning priority-ranked content to space across the full range of viewports a surface must serve, so the task hierarchy survives every real screen. It runs in one direction — hierarchy first, structure second. Given the primary, secondary, and supporting content (handed over from task analysis or a route contract), composition chooses a scan pattern (single column, master-detail, sidebar/content, table-first, card grid, or step flow), lays down a grid or flex skeleton, and then sets breakpoints at the points where the content actually breaks rather than at marketed device widths. Two constraints are non-negotiable: spatial stability — fixed-format elements such as tables, charts, media, and cards get stable dimensions so they do not jump on hover, loading, or label changes; and ordered survival — at every breakpoint the primary content stays above the fold and the action and recovery order is preserved as elements stack, pin, collapse, or hide. The layout is the visible contract between task priority and available space, and it must hold not only at full data but across loading, empty, and error states. Composition arranges; it does not decide why the content exists, how the user navigates to it, how it is styled, or how its components are built.

Coverage

Compose page and screen structure so the hierarchy survives real viewports. Covers section order, scan pattern, grid and flex choices, responsive breakpoints, mobile-first stacking, stable dimensions, responsive media, density, empty/loaded-state footprint, and handoff from task hierarchy to implementation-ready layout.

Scan patterns are the structural archetypes: single column (linear reading/forms), master-detail (a list plus a detail pane), sidebar/content (persistent nav or filters beside the main region), table-first (dense tabular data leads), card grid (browsable peers), and step flow (sequenced screens). The pattern is chosen from the content hierarchy, not from aesthetic preference.

Breakpoints are defined where the content breaks — where a column becomes too narrow to read, where a table can no longer show its essential columns, where a card grid drops below a usable card width — not at named device widths (375, 768, 1024). Designing to devices dates the layout the moment a new device ships; designing to content-break points keeps it durable.

Stable dimensions protect elements that must not resize on hover, load, or label change: reserve space for tables, charts, images (aspect-ratio), and toolbars so the surrounding layout does not reflow when their content arrives or updates. Layout shift during loading is a designed-out defect, not an inevitability.

Reflow decisions at each breakpoint specify what collapses (multi-column to single), stacks (side-by-side to vertical), pins (a toolbar/action bar stays reachable), hides (secondary detail behind disclosure), or moves. Across all of these, the primary task stays visible before supporting detail and the action/recovery order is preserved.

State footprints matter: the loading, empty, and error states of a region must occupy the same structural slot as the loaded state so the page does not jump between states, and responsive media must not overflow its container.

Philosophy of the skill

Layout is the visible contract between task priority and available space. A surface that has the right content can still fail if primary information collapses below the fold, controls jump between states, or a desktop-only composition is squeezed into a narrow viewport.

Start from hierarchy, then choose structure. Do not design to named devices; design to the point where the content starts to break. A breakpoint tied to a device is a breakpoint that expires; a breakpoint tied to content is one that endures.

Stability is a feature. An element that holds its position through loading, hover, and label changes is doing invisible work — it keeps the user's spatial memory intact. Treat layout shift as a defect to design out, not an artifact to tolerate.

Method

1. Read the primary, secondary, and supporting hierarchy from task-analysis or the route contract.
2. Identify fixed-format elements: tables, cards, charts, boards, media, toolbars, and forms.
3. Choose the scan pattern: single column, master-detail, sidebar/content, table-first, card grid, or step flow.
4. Define responsive breakpoints where content breaks, not where devices are marketed.
5. Set stable dimensions for elements that must not resize on hover, loading, or label changes.
6. Decide what collapses, stacks, pins, hides, or moves at each breakpoint.
7. Check mobile, tablet, desktop, low-data, loading, empty, and error states.

Verification

• The primary task remains visible before supporting detail.
• Breakpoints are content-driven rather than device-name-driven.
• Fixed-format elements have stable dimensions or aspect ratios.
• Mobile and narrow layouts preserve action order and recovery paths.
• Loading, empty, and error states do not shift the core layout unpredictably.
• Responsive media cannot overflow its container.
• Accessibility landmarks, heading order, and focus order still match the visual order.

Do NOT Use When

Use instead	When
task-analysis	The user goal, top task, or first-viewport hierarchy is not yet known.
information-architecture	The problem is global navigation, sitemap shape, or page grouping.
visual-design-foundations	The task is color, typography, spacing taste, mood, or polish.
design-system-architecture	The task is token taxonomy, component API, theming, or system governance.
a11y	The primary question is WCAG, ARIA, keyboard behavior, labels, or assistive-tech output.