adapt

Adapt designs across screen sizes, input methods, and usage contexts.

Updated Jul 5, 2025
One-click install
npx skills add https://github.com/nsuberi/proto-portal-showcase-hub --skill adapt-nsuberi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adapt
Source: https://github.com/nsuberi/proto-portal-showcase-hub/tree/main/apps/ai-builders-portal/.claude/skills/adapt
Command: npx skills add https://github.com/nsuberi/proto-portal-showcase-hub --skill adapt-nsuberi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Adapting designs to different screen sizes, input methods, and usage contexts so interfaces remain usable, accessible, and effective when moved between desktop, mobile, tablet, print, or email. It reduces broken layouts, unusable interactions, and poor content prioritization that occur when a design is simply scaled instead of rethought for a new context.

Core Features & Use Cases

  • Context assessment: Identify source assumptions (input method, connection, screen size) and gather target platform details before making changes.
  • Layout & interaction strategies: Prescribes single-column stacking, bottom navigation, touch target sizing (44x44px), container queries, CSS Grid/Flexbox, and breakpoint planning.
  • Platform-specific adaptations: Guidance for mobile-first reflows, tablet master-detail, desktop enhancements (hover, shortcuts), print-friendly pagination, and email-safe single-column layouts.
  • Verification checklist: Emphasizes real-device testing, orientation checks, accessibility, and slow-network simulations.

Quick Start

Adapt the homepage from desktop to mobile by prioritizing primary content, switching to a single-column layout, using 44x44px touch targets, and defining breakpoints around 375px and 768px.

Frequently Asked Questions about adapt

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

FAQPage Schema
How do I make my desktop design responsive for mobile and tablet screens?

Make designs responsive by assessing source assumptions, prioritizing primary content, and applying single-column stacking, CSS Grid, and touch target sizing. Use breakpoint planning around common widths like 375px and 768px to ensure layouts reflow correctly across mobile and tablet devices.

What is the best way to choose CSS breakpoints for responsive layouts?

Choosing CSS breakpoints involves identifying target platform screen sizes and applying layout strategies like container queries and Flexbox. Breakpoints should be selected around common device widths, such as 375px for mobile and 768px for tablets, to trigger single-column stacking or master-detail views.

How do I convert a web layout to an email-safe single-column format?

Convert web layouts to email-safe formats by applying platform-specific adaptations that reflow content into a single-column layout. This adaptation ensures interfaces remain usable within constrained email viewports by prioritizing content and avoiding complex responsive techniques like CSS Grid that email clients do not support.

Why do my interactive elements fail on touch devices and how do I fix them?

Interactive elements fail on touch devices when designs are simply scaled instead of rethought for new input methods. Fix this by resizing touch targets to 44x44px, implementing bottom navigation, and verifying interactions through real-device testing and orientation checks to ensure accessibility.

Does container queries work for adapting components inside constrained viewports?

Container queries work for adapting components inside constrained viewports by allowing layouts to respond to their parent container size rather than the entire screen. This responsive design technique ensures components remain usable and effective when moved between different page sections or layout contexts.

What are the limitations of simply scaling a design instead of using responsive design techniques?

Simply scaling a design instead of using responsive techniques leads to broken layouts, unusable touch interactions, and poor content prioritization. Limitations arise from ignoring context assumptions like input methods and screen size, requiring rethought layouts using CSS Grid, progressive disclosure, and real-device verification.