Adapt existing designs to work effectively across different contexts - different screen sizes, devices, platforms, or use cases.
MANDATORY PREPARATION
Invoke /frontend-design — it contains design principles, anti-patterns, and the Context Gathering Protocol. Follow the protocol before proceeding — if no design context exists yet, you MUST run /teach-impeccable first. Additionally gather: target platforms/devices and usage contexts.
Assess Adaptation Challenge
Understand what needs adaptation and why:
Identify the source context:
- What was it designed for originally? (Desktop web? Mobile app?)
- What assumptions were made? (Large screen? Mouse input? Fast connection?)
- What works well in current context?
Understand target context:
- Device: Mobile, tablet, desktop, TV, watch, print?
- Input method: Touch, mouse, keyboard, voice, gamepad?
- Screen constraints: Size, resolution, orientation?
- Connection: Fast wifi, slow 3G, offline?
- Usage context: On-the-go vs desk, quick glance vs focused reading?
- User expectations: What do users expect on this platform?
Identify adaptation challenges:
- What won't fit? (Content, navigation, features)
- What won't work? (Hover states on touch, tiny touch targets)
- What's inappropriate? (Desktop patterns on mobile, mobile patterns on desktop)
CRITICAL: Adaptation is not just scaling - it's rethinking the experience for the new context.
Plan Adaptation Strategy
Create context-appropriate strategy:
Mobile Adaptation (Desktop → Mobile)
Layout Strategy:
- Single column instead of multi-column
- Vertical stacking instead of side-by-side
- Full-width components instead of fixed widths
- Bottom navigation instead of top/side navigation
Interaction Strategy:
- Touch targets 44x44px minimum (not hover-dependent)
- Swipe gestures where appropriate (lists, carousels)
- Bottom sheets instead of dropdowns
- Thumbs-first design (controls within thumb reach)
- Larger tap areas with more spacing
Content Strategy:
- Progressive disclosure (don't show everything at once)
- Prioritize primary content (secondary content in tabs/accordions)
- Shorter text (more concise)
- Larger text (16px minimum)
Navigation Strategy:
- Hamburger menu or bottom navigation
- Reduce navigation complexity
- Sticky headers for context
- Back button in navigation flow
Tablet Adaptation (Hybrid Approach)
Layout Strategy:
- Two-column layouts (not single or three-column)
- Side panels for secondary content
- Master-detail views (list + detail)
- Adaptive based on orientation (portrait vs landscape)
Interaction Strategy:
- Support both touch and pointer
- Touch targets 44x44px but allow denser layouts than phone
- Side navigation drawers
- Multi-column forms where appropriate
Desktop Adaptation (Mobile → Desktop)
Layout Strategy:
- Multi-column layouts (use horizontal space)
- Side navigation always visible
- Multiple information panels simultaneously
- Fixed widths with max-width constraints (don't stretch to 4K)
Interaction Strategy:
- Hover states for additional information
- Keyboard shortcuts
- Right-click context menus
- Drag and drop where helpful
- Multi-select with Shift/Cmd
Content Strategy:
- Show more information upfront (less progressive disclosure)
- Data tables with many columns
- Richer visualizations
- More detailed descriptions
Print Adaptation (Screen → Print)
Layout Strategy:
- Page breaks at logical points
- Remove navigation, footer, interactive elements
- Black and white (or limited color)
- Proper margins for binding
Content Strategy:
- Expand shortened content (show full URLs, hidden sections)
- Add page numbers, headers, footers
- Include metadata (print date, page title)
- Convert charts to print-friendly versions
Email Adaptation (Web → Email)
Layout Strategy:
- Narrow width (600px max)
- Single column only
- Inline CSS (no external stylesheets)
- Table-based layouts (for email client compatibility)
Interaction Strategy:
- Large, obvious CTAs (buttons not text links)
- No hover states (not reliable)
- Deep links to web app for complex interactions
Implement Adaptations
Apply changes systematically:
Responsive Breakpoints
Choose appropriate breakpoints:
- Mobile: 320px-767px
- Tablet: 768px-1023px
- Desktop: 1024px+
- Or content-driven breakpoints (where design breaks)
Layout Adaptation Techniques
- CSS Grid/Flexbox: Reflow layouts automatically
- Container Queries: Adapt based on container, not viewport
clamp(): Fluid sizing between min and max
- Media queries: Different styles for different contexts
- Display properties: Show/hide elements per context
Touch Adaptation
- Increase touch target sizes (44x44px minimum)
- Add more spacing between interactive elements
- Remove hover-dependent interactions
- Add touch feedback (ripples, highlights)
- Consider thumb zones (easier to reach bottom than top)
Content Adaptation
- Use
display: none sparingly (still downloads)
- Progressive enhancement (core content first, enhancements on larger screens)
- Lazy loading for off-screen content
- Responsive images (
srcset, picture element)
Navigation Adaptation
- Transform complex nav to hamburger/drawer on mobile
- Bottom nav bar for mobile apps
- Persistent side navigation on desktop
- Breadcrumbs on smaller screens for context
IMPORTANT: Test on real devices, not just browser DevTools. Device emulation is helpful but not perfect.
NEVER:
- Hide core functionality on mobile (if it matters, make it work)
- Assume desktop = powerful device (consider accessibility, older machines)
- Use different information architecture across contexts (confusing)
- Break user expectations for platform (mobile users expect mobile patterns)
- Forget landscape orientation on mobile/tablet
- Use generic breakpoints blindly (use content-driven breakpoints)
- Ignore touch on desktop (many desktop devices have touch)
Verify Adaptations
Test thoroughly across contexts:
- Real devices: Test on actual phones, tablets, desktops
- Different orientations: Portrait and landscape
- Different browsers: Safari, Chrome, Firefox, Edge
- Different OS: iOS, Android, Windows, macOS
- Different input methods: Touch, mouse, keyboard
- Edge cases: Very small screens (320px), very large screens (4K)
- Slow connections: Test on throttled network
Remember: You're a cross-platform design expert. Make experiences that feel native to each context while maintaining brand and functionality consistency. Adapt intentionally, test thoroughly.
1---2name: adapt3description: Adapt designs to work across different screen sizes, devices, contexts, or platforms. Implements breakpoints, fluid layouts, and touch targets. Use when the user mentions responsive design, mobile layouts, breakpoints, viewport adaptation, or cross-device compatibility.4metadata:5 source: https://skillmd.com/skills/decebal/adapt6---78Adapt existing designs to work effectively across different contexts - different screen sizes, devices, platforms, or use cases.910## MANDATORY PREPARATION1112Invoke /frontend-design — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run /teach-impeccable first. Additionally gather: target platforms/devices and usage contexts.1314---1516## Assess Adaptation Challenge1718Understand what needs adaptation and why:19201. **Identify the source context**:21 - What was it designed for originally? (Desktop web? Mobile app?)22 - What assumptions were made? (Large screen? Mouse input? Fast connection?)23 - What works well in current context?24252. **Understand target context**:26 - **Device**: Mobile, tablet, desktop, TV, watch, print?27 - **Input method**: Touch, mouse, keyboard, voice, gamepad?28 - **Screen constraints**: Size, resolution, orientation?29 - **Connection**: Fast wifi, slow 3G, offline?30 - **Usage context**: On-the-go vs desk, quick glance vs focused reading?31 - **User expectations**: What do users expect on this platform?32333. **Identify adaptation challenges**:34 - What won't fit? (Content, navigation, features)35 - What won't work? (Hover states on touch, tiny touch targets)36 - What's inappropriate? (Desktop patterns on mobile, mobile patterns on desktop)3738**CRITICAL**: Adaptation is not just scaling - it's rethinking the experience for the new context.3940## Plan Adaptation Strategy4142Create context-appropriate strategy:4344### Mobile Adaptation (Desktop → Mobile)4546**Layout Strategy**:47- Single column instead of multi-column48- Vertical stacking instead of side-by-side49- Full-width components instead of fixed widths50- Bottom navigation instead of top/side navigation5152**Interaction Strategy**:53- Touch targets 44x44px minimum (not hover-dependent)54- Swipe gestures where appropriate (lists, carousels)55- Bottom sheets instead of dropdowns56- Thumbs-first design (controls within thumb reach)57- Larger tap areas with more spacing5859**Content Strategy**:60- Progressive disclosure (don't show everything at once)61- Prioritize primary content (secondary content in tabs/accordions)62- Shorter text (more concise)63- Larger text (16px minimum)6465**Navigation Strategy**:66- Hamburger menu or bottom navigation67- Reduce navigation complexity68- Sticky headers for context69- Back button in navigation flow7071### Tablet Adaptation (Hybrid Approach)7273**Layout Strategy**:74- Two-column layouts (not single or three-column)75- Side panels for secondary content76- Master-detail views (list + detail)77- Adaptive based on orientation (portrait vs landscape)7879**Interaction Strategy**:80- Support both touch and pointer81- Touch targets 44x44px but allow denser layouts than phone82- Side navigation drawers83- Multi-column forms where appropriate8485### Desktop Adaptation (Mobile → Desktop)8687**Layout Strategy**:88- Multi-column layouts (use horizontal space)89- Side navigation always visible90- Multiple information panels simultaneously91- Fixed widths with max-width constraints (don't stretch to 4K)9293**Interaction Strategy**:94- Hover states for additional information95- Keyboard shortcuts96- Right-click context menus97- Drag and drop where helpful98- Multi-select with Shift/Cmd99100**Content Strategy**:101- Show more information upfront (less progressive disclosure)102- Data tables with many columns103- Richer visualizations104- More detailed descriptions105106### Print Adaptation (Screen → Print)107108**Layout Strategy**:109- Page breaks at logical points110- Remove navigation, footer, interactive elements111- Black and white (or limited color)112- Proper margins for binding113114**Content Strategy**:115- Expand shortened content (show full URLs, hidden sections)116- Add page numbers, headers, footers117- Include metadata (print date, page title)118- Convert charts to print-friendly versions119120### Email Adaptation (Web → Email)121122**Layout Strategy**:123- Narrow width (600px max)124- Single column only125- Inline CSS (no external stylesheets)126- Table-based layouts (for email client compatibility)127128**Interaction Strategy**:129- Large, obvious CTAs (buttons not text links)130- No hover states (not reliable)131- Deep links to web app for complex interactions132133## Implement Adaptations134135Apply changes systematically:136137### Responsive Breakpoints138139Choose appropriate breakpoints:140- Mobile: 320px-767px141- Tablet: 768px-1023px142- Desktop: 1024px+143- Or content-driven breakpoints (where design breaks)144145### Layout Adaptation Techniques146147- **CSS Grid/Flexbox**: Reflow layouts automatically148- **Container Queries**: Adapt based on container, not viewport149- **`clamp()`**: Fluid sizing between min and max150- **Media queries**: Different styles for different contexts151- **Display properties**: Show/hide elements per context152153### Touch Adaptation154155- Increase touch target sizes (44x44px minimum)156- Add more spacing between interactive elements157- Remove hover-dependent interactions158- Add touch feedback (ripples, highlights)159- Consider thumb zones (easier to reach bottom than top)160161### Content Adaptation162163- Use `display: none` sparingly (still downloads)164- Progressive enhancement (core content first, enhancements on larger screens)165- Lazy loading for off-screen content166- Responsive images (`srcset`, `picture` element)167168### Navigation Adaptation169170- Transform complex nav to hamburger/drawer on mobile171- Bottom nav bar for mobile apps172- Persistent side navigation on desktop173- Breadcrumbs on smaller screens for context174175**IMPORTANT**: Test on real devices, not just browser DevTools. Device emulation is helpful but not perfect.176177**NEVER**:178- Hide core functionality on mobile (if it matters, make it work)179- Assume desktop = powerful device (consider accessibility, older machines)180- Use different information architecture across contexts (confusing)181- Break user expectations for platform (mobile users expect mobile patterns)182- Forget landscape orientation on mobile/tablet183- Use generic breakpoints blindly (use content-driven breakpoints)184- Ignore touch on desktop (many desktop devices have touch)185186## Verify Adaptations187188Test thoroughly across contexts:189190- **Real devices**: Test on actual phones, tablets, desktops191- **Different orientations**: Portrait and landscape192- **Different browsers**: Safari, Chrome, Firefox, Edge193- **Different OS**: iOS, Android, Windows, macOS194- **Different input methods**: Touch, mouse, keyboard195- **Edge cases**: Very small screens (320px), very large screens (4K)196- **Slow connections**: Test on throttled network197198Remember: You're a cross-platform design expert. Make experiences that feel native to each context while maintaining brand and functionality consistency. Adapt intentionally, test thoroughly.