responsive-paradigms

Adapt interface layouts and interactions for mobile, tablet, and desktop breakpoints.

33|6|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/dembrandt/dembrandt-skills --skill responsive-paradigms-dembrandt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: responsive-paradigms
Source: https://github.com/dembrandt/dembrandt-skills/tree/main/skills/responsive-paradigms
Command: npx skills add https://github.com/dembrandt/dembrandt-skills --skill responsive-paradigms-dembrandt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents responsive interfaces from becoming shrunken desktop layouts by helping you adapt navigation, content, controls, and interaction patterns to the needs of mobile, tablet, and desktop users.

Core Features & Use Cases

  • Breakpoint-Specific Design: Choose appropriate layouts, navigation models, visibility rules, and sticky behavior for mobile, tablet, desktop, and ultra-wide screens.
  • Mobile-First Interaction: Prioritize touch-friendly targets, reachable primary actions, single-column content, and tap-based alternatives to hover interactions.
  • Use Case: When adapting a dense desktop dashboard for phones, use this Skill to determine which sections should stack, collapse, move within their region, or disappear while keeping key actions accessible.

Quick Start

Ask the responsive paradigms skill to redesign this desktop layout for mobile and tablet, including breakpoint behavior, navigation changes, touch targets, and ultra-wide constraints.

Frequently Asked Questions about responsive-paradigms

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I adapt a desktop dashboard layout for mobile without just shrinking it?

Adapting a desktop dashboard for mobile requires reflowing content into a single column, collapsing non-critical sections, and ensuring primary actions remain reachable. You must replace hover interactions with tap-based alternatives and apply breakpoint-specific sticky behavior to maintain usability.

What is the minimum touch target size for mobile UI accessibility?

The minimum touch target size for mobile UI accessibility is 44 by 44 pixels. Ensuring touch targets meet this threshold prevents mis-taps and makes interactive elements accessible on small screens. If controls are shortened to save space, accessible labels must be added.

When do I need different navigation models for tablet and desktop layouts?

Different navigation models for tablet and desktop layouts are needed when interaction patterns and available space shift significantly between devices. You should apply breakpoint-specific visibility rules and navigation changes to ensure primary actions stay reachable and content widths are capped appropriately.

How do I handle ultra-wide screen layouts without stretching content?

Handling ultra-wide screen layouts involves capping content widths to prevent over-stretched text and maintaining readable line lengths. You should apply specific visibility rules and sticky behavior for ultra-wide breakpoints to keep dashboards structured and visually anchored.

Does mobile-first responsive design require accessible labels for shortened controls?

Mobile-first responsive design requires accessible labels for shortened controls because shrinking interface elements obscures their purpose. Adding accessible labels ensures that collapsed or icon-only navigation buttons remain understandable for users interacting via touch.

What's the best way to choose breakpoints for adaptive UI?

Choosing breakpoints for adaptive UI involves defining distinct layout paradigms for mobile, tablet, desktop, and ultra-wide screens rather than merely scaling a single design. Breakpoints should trigger changes in navigation models, content stacking, and sticky behavior to optimize interaction patterns.