mcpField
A
adapt

adapt

github.com/educlopezDesign & UI407581 installsUpdated 2w ago
Repository

About adapt

adapt is a responsive-design sub-skill of ui-craft for developers adapting interfaces across devices. Its mobile-first checklist covers layout, touch, and navigation, and it directs the agent to edit code directly.

Key features

  1. 01Mobile-first adaptation workflow
  2. 02Breakpoint and container query guidance
  3. 03Touch target and safe-area checks
  4. 04Small-screen horizontal scroll checks
  5. 05Navigation and image adaptation rules

Use cases

  1. 01Adapt an existing interface for phones and tablets
  2. 02Check touch zones and device safe areas
  3. 03Adjust responsive behavior in sidebars and main content

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/educlopez/ui-craft --skill adapt

After installing, type/adaptin Claude Code to confirm it loaded.

Details

From the project README

Context: this sub-skill is one lens of the broader ui-craft skill. If the ui-craft skill is also installed, read its SKILL.md first for Discovery + Anti-Slop + Craft Test, then apply the specific lens below.

Adapt the UI at $ARGUMENTS across devices. Load the ui-craft skill and read references/responsive.md.

Work mobile-first. Don't shrink desktop; grow from mobile.

Checklist:

  1. Breakpoints — use project's existing system (Tailwind: sm md lg xl; CSS: container queries preferred over media queries for components). No magic widths.
  2. Touch — tap targets ≥ 44×44px (min-h-11 min-w-11). Touch zones don't overlap. touch-action: manipulation on interactive elements.
  3. Safe areas — padding-top: env(safe-area-inset-top) etc. on fixed headers/footers/FAB. Check iOS notch and Android gesture bar.
  4. No horizontal scroll at 320px. Test with devtools device mode.
  5. Fluid type — clamp(1rem, 0.9rem + 0.5vw, 1.125rem) for body where scale matters; fixed px for small UI text (labels, captions).
  6. Container queries — prefer @container over viewport media queries for component-level responsiveness. Components that live in sidebars and main content behave differently at the same viewport width.
  7. Hover-less devices — every hover affordance has a non-hover equivalent. @media (hover: hover) to scope desktop-only effects.
  8. Density shifts with viewport — honor VISUAL_DENSITY differently per breakpoint:
    • VISUAL_DENSITY ≤ 3 → fewer columns and wider spacing even at desktop widths.
    • VISUAL_DENSITY 8+ → honor dashboard density, but still respect touch/hover distinctions (touch targets stay ≥ 44px on mobile, hover affordances gated behind @media (hover: hover)).
    • Mobile always trends toward 1 column and wider spacing regardless of the knob value.
  9. Images — aspect-ratio set; srcset + sizes for different viewports; loading="lazy" below the fold; fetchpriority="high" on hero.
  10. Nav pattern — desktop horizontal → mobile collapses (sheet, drawer, or bottom tabs). Never a hamburger on desktop unless the nav has > 7 top-level items.

Output: edit code directly. Print the Review Format table of changes. Flag any responsive bugs you can't fix without more info (missing design for a breakpoint, unclear nav pattern).

Next step: /audit — verify the responsive pass against a11y, performance and touch targets (rung 1).

Comments

Markdown supported