adapt

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

Updated May 4, 2026
One-click install
npx skills add https://github.com/Gito125/gideon_portfolio --skill adapt-gito125
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: adapt
Source: https://github.com/Gito125/gideon_portfolio/tree/main/.github/skills/adapt
Command: npx skills add https://github.com/Gito125/gideon_portfolio --skill adapt-gito125

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Designs built for one context often break or feel wrong on other devices — hover states fail on touchscreens, multi-column layouts collapse on phones, and desktop patterns confuse mobile users. This Skill guides the systematic adaptation of existing designs to new screen sizes, devices, input methods, and platforms. ## Core Features & Use Cases - Context Assessment: Analyzes source and target contexts (device, input method, connection, usage scenario) to identify what won't fit, won't work, or is inappropriate. - 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, 44px touch targets, and responsive images. - Use Case: You have a desktop web dashboard and need it to work on phones. The Skill walks you through converting multi-column layouts to single-column stacking, replacing hover interactions with touch targets, and restructuring navigation into a hamburger or bottom bar. ## Quick Start Ask the AI to adapt your desktop dashboard design for mobile devices with touch-friendly layouts and navigation.

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 devices?▼

Convert multi-column layouts to single-column vertical stacking, replace hover interactions with 44x44px touch targets, and move navigation to a hamburger menu or bottom bar. Prioritize primary content with progressive disclosure and use 16px minimum text size.

What breakpoints should I use for responsive design?▼

Common breakpoints are 320-767px for mobile, 768-1023px for tablet, and 1024px+ for desktop. However, content-driven breakpoints — where the design actually breaks — are preferred over generic device-based values.

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 like ripples or highlights for confirmation.

How do I adapt a web page for print?▼

Remove navigation, footers, and interactive elements, then add page breaks at logical points with proper margins. Expand hidden content, include page numbers and metadata, and convert charts to print-friendly black-and-white versions.

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

Browser device emulation does not perfectly replicate real hardware behavior, touch handling, or network conditions. Always test on actual phones and tablets across orientations, browsers, and throttled connections.

When should I use container queries instead of media queries?▼

Use container queries when a component should adapt based on its parent container's size rather than the viewport. This makes components reusable across different layout contexts without viewport-specific breakpoint logic.