adapt

Adapt UI designs across screen sizes using breakpoints, Grid/Flexbox, and container queries.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/jcdiv47/cool-paper --skill adapt-jcdiv47
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adapt
Source: https://github.com/jcdiv47/cool-paper/tree/main/.agents/skills/adapt
Command: npx skills add https://github.com/jcdiv47/cool-paper --skill adapt-jcdiv47

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps designers and product teams adapt existing interfaces so they remain usable, accessible, and consistent across different screen sizes, input methods, and platforms, preventing layout breakage and interaction failures.

Core Features & Use Cases

  • Context analysis: Guiding questions to identify source assumptions, target devices, input methods, connection constraints, and user expectations.
  • Adaptation strategies: Concrete layout, interaction, content, and navigation patterns for mobile, tablet, desktop, print, and email transitions.
  • Implementation techniques: Recommendations for breakpoints, CSS Grid/Flexbox, container queries, touch target sizing, progressive disclosure, and testing on real devices.
  • Use Case: Rework a desktop dashboard into a mobile-first single-column experience with prioritized content, bottom navigation, and larger tap targets.

Quick Start

Use the adapt skill to convert a desktop checkout flow into a mobile-first single-column layout with larger tap targets and simplified 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 layout for mobile and tablet screens?

To adapt a desktop layout for mobile and tablet screens, apply responsive design techniques like CSS Grid and Flexbox. Transform multi-column layouts into prioritized single-column experiences with adjusted navigation and larger touch targets.

What are the best practices for responsive design breakpoints and touch target sizing?

Responsive design breakpoints and touch target sizing best practices involve using container queries for component-level flexibility and ensuring tap targets meet accessibility standards. Testing requirements on real devices validate these adaptation patterns for usability.

When do I need container queries instead of CSS Grid for responsive adaptation?

You need container queries for responsive adaptation when components must respond to their parent container size rather than the viewport. CSS Grid handles overall page layout structure, while container queries enable modular, independent component adaptation.

How do I rework a desktop checkout flow into a mobile-first single-column layout?

Reworking a desktop checkout flow into a mobile-first single-column layout requires simplifying navigation and prioritizing content. Implement progressive disclosure and larger tap targets to maintain usability and consistency across mobile devices.

Does this responsive design approach work for print and email adaptation contexts?

Yes, this responsive design approach works for print and email adaptation contexts. It provides concrete layout, interaction, and content navigation patterns to transition interfaces across mobile, tablet, desktop, print, and email platforms.

Why does my responsive layout break when adapting to different screen sizes?

Your responsive layout breaks when adapting to different screen sizes due to incorrect breakpoint usage or lack of context analysis. Evaluating source assumptions, target devices, and input methods prevents interaction failures and maintains accessibility.