phazurlabs/sumi

responsive-block-patterns

How every block and component transforms across breakpoints: container queries, fluid scaling, breakpoint transformation catalogs, responsive grids, and mobile-first CSS with production code.

First seen Aug 10, 2026

Installation

$ npx skills add phazurlabs/sumi --skill responsive-block-patterns

Summary

  • 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.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from phazurlabs/sumi · top by installs.

npx skills add phazurlabs/sumi

Browse all from phazurlabs/sumi

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 40
License LICENSE
Default branch main
Open issues 1
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 4,585 B
  • docs SUMMARY.md 322 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 11 installs

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

Need Reference
What a given component does at each breakpoint breakpoint-transformation-catalog.md
Adaptive card, morphing nav, table-to-cards container-query-patterns.md
Container query syntax and units container-query-patterns.md
Fluid type scale, fluid space scale fluid-scaling-system.md
The clamp() formula and when it beats breakpoints fluid-scaling-system.md
Responsive typography, images, tables, nav as code responsive-component-patterns.md
Column progressions, collapsing sidebar, holy grail responsive-layout-recipes.md

Reference architecture

File Covers Lines
references/responsive-component-patterns.md component-level responsive code 1878
references/container-query-patterns.md container query recipes 1728
references/responsive-layout-recipes.md whole-layout recipes 1524
references/fluid-scaling-system.md clamp(), fluid scales 842
references/breakpoint-transformation-catalog.md 60+ components x breakpoint 707

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)