adapt

Adapt designs across screen sizes, devices, and contexts for usability.

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/HAR5HA-7663/Claude-Skills --skill adapt-har5ha-7663
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adapt
Source: https://github.com/HAR5HA-7663/Claude-Skills/tree/main/adapt
Command: npx skills add https://github.com/HAR5HA-7663/Claude-Skills --skill adapt-har5ha-7663

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Adapt existing designs to work effectively across different contexts - different screen sizes, devices, platforms, or use cases.

Core Features & Use Cases

  • Mobile-first adaptation guidance for breakpoints and touch targets.
  • Context gathering and target platform identification to inform design decisions.
  • Use cases include mobile, tablet, desktop, print adaptations and accessibility considerations.

Quick Start

Invoke the Context Gathering Protocol to collect target platforms, contexts, and constraints, and apply the adaptation strategy accordingly.

Frequently Asked Questions about adapt

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I adapt an existing design for responsive redesign across different screen sizes?

To adapt an existing design for responsive redesign, you gather target platforms, contexts, and constraints, then apply a defined adaptation strategy to plan breakpoints and document the changes for implementation. This maintains usability across screen sizes.

What is the best way to plan breakpoints for mobile-first cross-device design?

Planning breakpoints for mobile-first cross-device design involves identifying target contexts and constraints, then defining a protocol for breakpoint planning and touch target sizing to guide implementation and maintain usability.

How does context gathering work for cross-device layout planning?

Context gathering for cross-device layout planning works by invoking a protocol to collect target platforms, device contexts, and usage constraints, which directly informs the adaptation strategy and subsequent design decisions.

Can I use this approach for print adaptations and accessibility conformance reviews?

Yes, you can use this approach for print adaptations and accessibility conformance reviews. The adaptation strategy explicitly covers mobile, tablet, desktop, and print adaptations alongside accessibility considerations to ensure effective context-aware design.

Do I need specific design components to maintain usability across different platforms?

You do not need specific design components to maintain usability across different platforms. The process relies on a context gathering protocol and adaptation documentation to guide implementation rather than requiring external dependencies or component libraries.

When should I not use a context-aware adaptation strategy for layout planning?

You should not use a context-aware adaptation strategy when your project requires a single, fixed layout without cross-device responsiveness, or when you need to generate production-ready code rather than defining adaptation protocols and documentation.