adapt

Adapt user interface designs across devices, screen sizes, and contexts.

Updated Apr 29, 2026
One-click install
npx skills add https://github.com/jean-sotil/presskitpro-webapp --skill adapt-jean-sotil
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adapt
Source: https://github.com/jean-sotil/presskitpro-webapp/tree/main/.agents/skills/adapt
Command: npx skills add https://github.com/jean-sotil/presskitpro-webapp --skill adapt-jean-sotil

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of designs breaking or feeling unusable when screen sizes, input methods, or usage contexts change, causing poor readability, awkward navigation, and inaccessible interactions.

Core Features & Use Cases

  • Context-aware responsive planning: Determine the source context, target device/input constraints, and the real adaptation challenges beyond simple scaling.
  • Breakpoint- and layout-specific strategies: Apply mobile (single column, touch-first), tablet (hybrid two-column), desktop (multi-panel), print (page breaks), and email (single-column table-based) approaches.
  • Interaction and content adjustments: Ensure touch targets (44x44px minimum), reduce hover dependence, use progressive disclosure, and load appropriate images/content patterns.

Use Case: A marketing page designed for desktop needs to work for mobile shoppers; adapt navigation, spacing, and content hierarchy so actions are reachable with thumbs and key information remains visible without hover.

Quick Start

Adapt the current UI for mobile by identifying the intended desktop assumptions, selecting mobile-first breakpoints, and rewriting layout, navigation, touch targets, and content hierarchy to match real thumb-and-tap usage.

Frequently Asked Questions about adapt

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

FAQPage Schema
How do I adapt an existing desktop UI design for mobile responsive layouts?

Adapt desktop UI for mobile responsive layouts by identifying original desktop assumptions, selecting mobile-first breakpoints, and rewriting layout to single-column, touch-first patterns with 44x44px minimum tap targets.

What is the best way to convert a web layout for print formatting?

Converting a web layout for print formatting requires applying page-break strategies, restructuring content hierarchy, and removing hover-dependent interactions to ensure readability and proper pagination across physical pages.

How do you handle mobile navigation and touch targets during responsive redesign?

Mobile navigation and touch targets require progressive disclosure patterns, minimum 44x44px tap zones, and reduced hover dependence, ensuring key actions remain reachable via thumb interactions without hidden menus.

Does this responsive design approach work for email template adaptation?

Responsive design adaptation works for email formatting by restructuring multi-panel desktop layouts into single-column, table-based approaches that ensure content readability and interaction safety across email clients.

Why does my responsive layout break when moving between tablet and desktop breakpoints?

Responsive layouts break across tablet and desktop breakpoints when adaptation relies on simple scaling rather than rethinking hybrid two-column and multi-panel strategies, requiring context-aware breakpoint planning and real-device verification.

When should I not use simple scaling for cross-device layout adaptation?

Avoid simple scaling for layout adaptation when interaction methods or usage contexts change, as screen size shifts demand rethinking navigation patterns, content hierarchy, and interaction affordances rather than resizing elements.