adapt

Adapt designs across screen sizes, devices, and platforms using breakpoints and fluid layouts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Designs built for one context often break or feel wrong on other devices, input methods, or platforms. This Skill guides the systematic adaptation of existing designs for mobile, tablet, desktop, print, and email contexts without losing functionality or brand consistency. ## Core Features & Use Cases - Context Assessment: Identifies source-context assumptions (screen size, input method, connection speed) and maps them against target-context constraints before changing anything. - Platform-Specific Strategies: Provides concrete layout, interaction, content, and navigation strategies for desktop-to-mobile, tablet hybrid, mobile-to-desktop, print, and email adaptations. - Implementation Techniques: Covers responsive breakpoints, CSS Grid/Flexbox reflow, container queries, clamp() fluid sizing, 44px touch targets, and responsive images. - Use Case: A desktop web dashboard needs a mobile version. The Skill walks through collapsing multi-column layouts, replacing hover interactions with touch targets, converting navigation to a bottom bar, and verifying on real devices. ## Quick Start Adapt this desktop dashboard design for mobile phones 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 website design for mobile?

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

What breakpoints should I use for responsive design?

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

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, add touch feedback, and place key controls within thumb reach.

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, use print-friendly colors, and include page numbers, headers, and metadata like print date.

Why does my responsive design fail on real devices but work in DevTools?

Device emulation does not replicate real touch behavior, network conditions, or OS-specific rendering. Test on actual phones and tablets across orientations, browsers, and throttled connections to catch these issues.