responsive-layout
Skill12 starsChanged 11 days agoMITView on GitHub
Use when a page or component must survive narrow containers, long or translated content, zoom, reflow, or overflow without device-name breakpoints.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- thewyattbrocato/design-and-copy-skillstheir own version, first seen Oct 17, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- thewyattbrocato/design-and-copy-skills★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository21 other files it gives its agents.
- AGENTS.mdAGENTS.md
- llms.txtllms.txt
- a11y-passSkill
- art-directionSkill
- cognitive-a11ySkill
- color-systemSkill
- component-statesSkill
- data-vizSkill
- design-system-interviewSkill
- deslop-uiSkill
- empty-statesSkill
- form-uxSkill
- humanize-copySkill
- i18n-readySkill
- improve-existing-websiteSkill
- micro-motionSkill
- spacing-systemSkill
- tastecheck-passSkill
- tasterollSkill
- themingSkill
- web-typographySkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 5 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
Start mobile-first with Grid/Flex intrinsic sizing (minmax, auto-fit, clamp, %/fr).
- Distinctive: line 16
Add breakpoints only where content breaks.
- Distinctive: line 17
Verify minimum supported viewport, 200–400% zoom, long/translated content, narrow embeds, and wide views without overflow or collapse.
- Very specific: line 22
Start with non-disappearing content, reading order, and narrowest real container.
- Distinctive: line 28
Start from the narrowest supported content state.
- Distinctive: line 30
Prefer container queries for reusable components when their behavior depends on their container, not the viewport.
- Very specific: line 38
Use references/patterns.md for grid, sidebar, stack, cluster, and container-query patterns.
- Very specific: line 39
Start with minmax(min(16rem, 100%), 1fr), min-width: 0, logical sizing, and content-led breakpoints.
- Distinctive: line 50
Use five-field ledger; start Reason with check ID.
- Very specific: line 78
Stop / handoff: Pause when content priority is unknown and reflow would silently hide required information (+1 in contract.json).
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Responsive Layout
Responsive layout is intrinsic reflow plus content-led breakpoints/container queries, not named-device CSS.
The decision order
- Start mobile-first with Grid/Flex intrinsic sizing (
minmax,auto-fit,clamp,%/fr). - Add breakpoints only where content breaks; reusable components use container queries.
- Verify minimum supported viewport, 200–400% zoom, long/translated content, narrow embeds, and wide views without overflow or collapse.
Preserve hierarchy under pressure
Start with non-disappearing content, reading order, and narrowest real container. Choose stack/reorder/progressive reveal/rail from observed pressure; test long content, locale, zoom, and embeds before calling it responsive.
Non-negotiables
- Start from the narrowest supported content state; avoid device-name breakpoints.
- Prevent overflow with
min-width: 0, bounded media, and wrapping; reflow rather than shrink to unusable. - Prefer container queries for reusable components when their behavior depends on their container, not the viewport.
- At narrow widths and zoom, reading/interaction should not require two-dimensional scrolling. Isolate essential exceptions (wide tables, maps, timelines, canvases) in a labelled, keyboard-operable scroll region.
Quick-start patterns
Use references/patterns.md for grid, sidebar, stack, cluster, and container-query patterns.
Start with minmax(min(16rem, 100%), 1fr), min-width: 0, logical sizing, and content-led
breakpoints.
Reference files
assets/layout-patterns.css— intrinsic examples after pressure evidence.references/patterns.md— patterns, units, images, and overflow debugging.references/decision-records.md— novel-case ADR rules.
Evidence
Use five-field ledger; start Reason with check ID.
| Status | Reason | Remediation | Evidence | Provenance |
| layout-strategy — content hierarchy and intrinsic composition | ||||
| containment — breakpoint and container-query rationale | ||||
| narrow-reflow — 320px, long-content, and overflow result | ||||
| zoom-interaction — zoom and keyboard-reachable interaction result | ||||
| handoff — component and accessibility boundary |
Pressure test
Each row names longest-pressure fixture, width/zoom, expected and observed result (or fail-closed missing evidence). Test full shell, narrow, 400%, and narrow embed; record what stays first/stacks/folds and why. No rendered build means plan, not pass.
How to deliver
Deliver content-led layout/breakpoints and rerunnable narrow/long/container/zoom/keyboard evidence; hand type, rhythm, and state concerns onward.
<!-- contract:v1:start -->Contract (generated)
Canonical detail: contract.json.
- Route: A layout needs intrinsic reflow, responsive hierarchy, container behavior, or overflow repair (+1 in contract.json); avoid: The request is only to choose a spacing scale or type system (+1 in contract.json)
- Exclude: Do not choose breakpoints from device names (+1 in contract.json)
- Stop / handoff: Pause when content priority is unknown and reflow would silently hide required information (+1 in contract.json); receives [art-direction, design-system-interview, improve-existing-website, spacing-system, tasteroll, theming, web-typography] -> sends [component-states, form-ux, a11y-pass, deslop-ui, i18n-ready]
- Output: An intrinsic layout strategy with justified breakpoints and responsive verification evidence
- Evidence:
table_with_evidencewithstatus,reason,remediation,evidence,provenance.
<!-- contract:v1:end -->Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.