agentleFS
phazurlabsphazurlabs/sumi/skills/responsive-block-patterns/SKILL.md

responsive-block-patterns

Skill58 starsChanged 23 days agoApache-2.0View on GitHub

How every block and component transforms across breakpoints: container queries, fluid scaling, breakpoint transformation catalogs, responsive grids, and mobile-first CSS with production code. Use when a layout must survive small screens, or when specifying responsive behavior for handoff.

The file

Files
SKILL.md

Responsive Block Patterns — Cross-Breakpoint Design Intelligence

Mental model

Responsive design is not resizing. It is deciding, per component, which of four things happens as space runs out: it reflows, it stacks, it transforms into a different component, or it disappears.

  • Container queries beat media queries for anything reusable. A card should respond to its container, not the viewport, or it breaks the moment you put it in a sidebar.
  • Fluid before stepped. clamp() handles the continuum; breakpoints handle the genuine transformations. Six breakpoints usually means someone was using them to do clamp()'s job.
  • Design the transformation, not the two end states. A table becoming a card list is a decision about what to drop; specifying only "table" and "cards" leaves that decision to whoever implements it.
  • Touch targets do not scale down. 44px is 44px at every breakpoint.

Constants

--bp-sm:  640px;   /* large phone            */
--bp-md:  768px;   /* tablet portrait        */
--bp-lg: 1024px;   /* tablet landscape, small laptop */
--bp-xl: 1280px;   /* desktop                */
--bp-2xl:1536px;   /* wide desktop           */

The clamp() master formula: clamp(min, preferred + relative, max), where preferred is in rem and relative is in vw.

Index

NeedReference
What a given component does at each breakpointbreakpoint-transformation-catalog.md
Adaptive card, morphing nav, table-to-cardscontainer-query-patterns.md
Container query syntax and unitscontainer-query-patterns.md
Fluid type scale, fluid space scalefluid-scaling-system.md
The clamp() formula and when it beats breakpointsfluid-scaling-system.md
Responsive typography, images, tables, nav as coderesponsive-component-patterns.md
Column progressions, collapsing sidebar, holy grailresponsive-layout-recipes.md

Reference architecture

FileCoversLines
references/responsive-component-patterns.mdcomponent-level responsive code1878
references/container-query-patterns.mdcontainer query recipes1728
references/responsive-layout-recipes.mdwhole-layout recipes1524
references/fluid-scaling-system.mdclamp(), fluid scales842
references/breakpoint-transformation-catalog.md60+ components x breakpoint707

What every reference file contains

  1. The transformation type — reflow, stack, transform, or hide
  2. The breakpoint or container size that triggers it, and why that value
  3. Complete CSS, container-query-first where it applies
  4. What is deliberately dropped at the smallest size
  5. Touch target and thumb-reach implications

Routing

For what each component does at each breakpoint — 60+ components across navigation, content, input and layout with their transformation type: read references/breakpoint-transformation-catalog.md.

For container queries — fundamentals plus adaptive cards, morphing navigation, table-to-card transformation and the rest: read references/container-query-patterns.md.

For fluid scaling — the clamp() master formula, complete fluid type and space scales, and fluid padding: read references/fluid-scaling-system.md.

For component-level responsive code — responsive typography, images, tables, navigation and the other patterns as production CSS: read references/responsive-component-patterns.md.

For whole-layout recipes — column progressions, collapsing sidebars, holy grail and the rest: read references/responsive-layout-recipes.md.

For odds and ends — the patterns that had no home in the files above when this skill was converted to a router: read references/responsive-supplementary.md.

Cross-References

  • layout-block-intelligence, component-patterns-code, mobile-ux-design, page-composition-engine
  • platform-visual-standards (iOS 26, Material 3 breakpoint conventions)
  • form-design-encyclopedia (responsive form patterns)
  • navigation-pattern-encyclopedia (responsive nav transformations)
  • typography-pairing-recipes (fluid type scales)
  • data-visualization-mastery (responsive chart patterns)

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.