adapt

Adapt designs for different screen sizes, devices, and platforms using responsive breakpoints and fluid layouts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Designs built for one context often break or feel wrong on other devices, and this Skill guides the systematic adaptation of layouts, interactions, and content across mobile, tablet, desktop, print, and email contexts. ## Core Features & Use Cases - Context Assessment: Identifies source assumptions and target constraints including device type, input method, screen size, connection speed, and usage context. - Platform-Specific Strategies: Provides concrete layout, interaction, content, and navigation strategies for mobile, tablet, desktop, print, and email adaptations. - Implementation Techniques: Covers responsive breakpoints, CSS Grid/Flexbox reflow, container queries, clamp() fluid sizing, touch target sizing, and responsive images. - Use Case: A desktop web dashboard needs a mobile version. The Skill guides converting multi-column layouts to single-column stacking, replacing hover interactions with 44x44px touch targets, and moving navigation to a bottom bar. ## Quick Start Adapt this desktop dashboard design for mobile devices with touch-friendly targets and a single-column layout.

Frequently Asked Questions about adapt

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

FAQPage Schema
How do I adapt a desktop design for mobile devices?

Convert multi-column layouts to single-column vertical stacking, replace hover interactions with touch targets of at least 44x44px, move navigation to a hamburger menu or bottom bar, and prioritize primary content with progressive disclosure.

What breakpoints should I use for responsive design?

Common breakpoints are 320-767px for mobile, 768-1023px for tablet, and 1024px and above for desktop. Prefer content-driven breakpoints where the design actually breaks rather than generic device widths.

What is the minimum touch target size for mobile design?

Touch targets should be at least 44x44px with adequate spacing between interactive elements. Remove hover-dependent interactions and add touch feedback such as ripples or highlights.

How do I adapt a web page for print?

Remove navigation and interactive elements, add page breaks at logical points, expand hidden content and full URLs, include page numbers and headers, and convert charts to print-friendly versions with proper margins.

Why should I test responsive designs on real devices instead of browser DevTools?

Device emulation is helpful but imperfect because it cannot fully replicate touch behavior, performance constraints, and rendering differences across iOS, Android, and various browsers. Real-device testing catches issues emulation misses.

What are common mistakes when adapting designs across platforms?

Common mistakes include hiding core functionality on mobile, using different information architecture per context, ignoring landscape orientation, blindly applying generic breakpoints, and treating adaptation as simple scaling rather than rethinking the experience.