Adapt existing designs to work effectively across different contexts - different screen sizes, devices, platforms, or use cases.
MANDATORY PREPARATION
Invoke /impeccable — 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 /impeccable teach 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: ui-responsive3description: >-4 Makes an existing UI responsive for phones, tablets, print or email: breakpoints, fluid layouts,5 touch targets, and mobile patterns for wide tables and hover tooltips. Use when a page was built6 desktop-only, the user asks for mobile-friendly or responsive design, mentions breakpoints, a7 375px screen, touch or tablet support. Not for building a new page (use impeccable).8version: 2.1.19user-invocable: true10argument-hint: "[target] [context (mobile, tablet, print...)]"11metadata:12 source: https://skillmd.com/skills/the-utopia-studio/ui-responsive13---1415Adapt existing designs to work effectively across different contexts - different screen sizes, devices, platforms, or use cases.1617## MANDATORY PREPARATION1819Invoke /impeccable — 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 /impeccable teach first. Additionally gather: target platforms/devices and usage contexts.2021---2223## Assess Adaptation Challenge2425Understand what needs adaptation and why:26271. **Identify the source context**:28 - What was it designed for originally? (Desktop web? Mobile app?)29 - What assumptions were made? (Large screen? Mouse input? Fast connection?)30 - What works well in current context?31322. **Understand target context**:33 - **Device**: Mobile, tablet, desktop, TV, watch, print?34 - **Input method**: Touch, mouse, keyboard, voice, gamepad?35 - **Screen constraints**: Size, resolution, orientation?36 - **Connection**: Fast wifi, slow 3G, offline?37 - **Usage context**: On-the-go vs desk, quick glance vs focused reading?38 - **User expectations**: What do users expect on this platform?39403. **Identify adaptation challenges**:41 - What won't fit? (Content, navigation, features)42 - What won't work? (Hover states on touch, tiny touch targets)43 - What's inappropriate? (Desktop patterns on mobile, mobile patterns on desktop)4445**CRITICAL**: Adaptation is not just scaling - it's rethinking the experience for the new context.4647## Plan Adaptation Strategy4849Create context-appropriate strategy:5051### Mobile Adaptation (Desktop → Mobile)5253**Layout Strategy**:54- Single column instead of multi-column55- Vertical stacking instead of side-by-side56- Full-width components instead of fixed widths57- Bottom navigation instead of top/side navigation5859**Interaction Strategy**:60- Touch targets 44x44px minimum (not hover-dependent)61- Swipe gestures where appropriate (lists, carousels)62- Bottom sheets instead of dropdowns63- Thumbs-first design (controls within thumb reach)64- Larger tap areas with more spacing6566**Content Strategy**:67- Progressive disclosure (don't show everything at once)68- Prioritize primary content (secondary content in tabs/accordions)69- Shorter text (more concise)70- Larger text (16px minimum)7172**Navigation Strategy**:73- Hamburger menu or bottom navigation74- Reduce navigation complexity75- Sticky headers for context76- Back button in navigation flow7778### Tablet Adaptation (Hybrid Approach)7980**Layout Strategy**:81- Two-column layouts (not single or three-column)82- Side panels for secondary content83- Master-detail views (list + detail)84- Adaptive based on orientation (portrait vs landscape)8586**Interaction Strategy**:87- Support both touch and pointer88- Touch targets 44x44px but allow denser layouts than phone89- Side navigation drawers90- Multi-column forms where appropriate9192### Desktop Adaptation (Mobile → Desktop)9394**Layout Strategy**:95- Multi-column layouts (use horizontal space)96- Side navigation always visible97- Multiple information panels simultaneously98- Fixed widths with max-width constraints (don't stretch to 4K)99100**Interaction Strategy**:101- Hover states for additional information102- Keyboard shortcuts103- Right-click context menus104- Drag and drop where helpful105- Multi-select with Shift/Cmd106107**Content Strategy**:108- Show more information upfront (less progressive disclosure)109- Data tables with many columns110- Richer visualizations111- More detailed descriptions112113### Print Adaptation (Screen → Print)114115**Layout Strategy**:116- Page breaks at logical points117- Remove navigation, footer, interactive elements118- Black and white (or limited color)119- Proper margins for binding120121**Content Strategy**:122- Expand shortened content (show full URLs, hidden sections)123- Add page numbers, headers, footers124- Include metadata (print date, page title)125- Convert charts to print-friendly versions126127### Email Adaptation (Web → Email)128129**Layout Strategy**:130- Narrow width (600px max)131- Single column only132- Inline CSS (no external stylesheets)133- Table-based layouts (for email client compatibility)134135**Interaction Strategy**:136- Large, obvious CTAs (buttons not text links)137- No hover states (not reliable)138- Deep links to web app for complex interactions139140## Implement Adaptations141142Apply changes systematically:143144### Responsive Breakpoints145146Choose appropriate breakpoints:147- Mobile: 320px-767px148- Tablet: 768px-1023px149- Desktop: 1024px+150- Or content-driven breakpoints (where design breaks)151152### Layout Adaptation Techniques153154- **CSS Grid/Flexbox**: Reflow layouts automatically155- **Container Queries**: Adapt based on container, not viewport156- **`clamp()`**: Fluid sizing between min and max157- **Media queries**: Different styles for different contexts158- **Display properties**: Show/hide elements per context159160### Touch Adaptation161162- Increase touch target sizes (44x44px minimum)163- Add more spacing between interactive elements164- Remove hover-dependent interactions165- Add touch feedback (ripples, highlights)166- Consider thumb zones (easier to reach bottom than top)167168### Content Adaptation169170- Use `display: none` sparingly (still downloads)171- Progressive enhancement (core content first, enhancements on larger screens)172- Lazy loading for off-screen content173- Responsive images (`srcset`, `picture` element)174175### Navigation Adaptation176177- Transform complex nav to hamburger/drawer on mobile178- Bottom nav bar for mobile apps179- Persistent side navigation on desktop180- Breadcrumbs on smaller screens for context181182**IMPORTANT**: Test on real devices, not just browser DevTools. Device emulation is helpful but not perfect.183184**NEVER**:185- Hide core functionality on mobile (if it matters, make it work)186- Assume desktop = powerful device (consider accessibility, older machines)187- Use different information architecture across contexts (confusing)188- Break user expectations for platform (mobile users expect mobile patterns)189- Forget landscape orientation on mobile/tablet190- Use generic breakpoints blindly (use content-driven breakpoints)191- Ignore touch on desktop (many desktop devices have touch)192193## Verify Adaptations194195Test thoroughly across contexts:196197- **Real devices**: Test on actual phones, tablets, desktops198- **Different orientations**: Portrait and landscape199- **Different browsers**: Safari, Chrome, Firefox, Edge200- **Different OS**: iOS, Android, Windows, macOS201- **Different input methods**: Touch, mouse, keyboard202- **Edge cases**: Very small screens (320px), very large screens (4K)203- **Slow connections**: Test on throttled network204205Remember: 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.