Run any Skill in Manus with one click

adapt

Stars207

Forks8

UpdatedJuly 4, 2026 at 21:55

"Responsive layout pass covering breakpoints, touch targets, safe areas, and fluid type. Use when the UI has layout or touch issues on mobile/tablet, when adding a new screen that hasn't been tested across viewports, or when the user says "make it responsive" / "fix mobile layout". Invoke when the user asks for adapt on their UI, or mentions 'adapt' alongside design / UI / frontend work."

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

educlopez

educlopez/ui-craft

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Web and Digital Interface DesignersComputer and Mathematical Occupations·SOC 15-1255

SKILL.md

readonly

name	adapt
description	"Responsive layout pass covering breakpoints, touch targets, safe areas, and fluid type. Use when the UI has layout or touch issues on mobile/tablet, when adding a new screen that hasn't been tested across viewports, or when the user says "make it responsive" / "fix mobile layout". Invoke when the user asks for adapt on their UI, or mentions 'adapt' alongside design / UI / frontend work."

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 the target the user described across devices. Load the ui-craft skill and read references/responsive.md.

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

Checklist:

Breakpoints — use project's existing system (Tailwind: sm md lg xl; CSS: container queries preferred over media queries for components). No magic widths.
Touch — tap targets ≥ 44×44px (min-h-11 min-w-11). Touch zones don't overlap. touch-action: manipulation on interactive elements.
Safe areas — padding-top: env(safe-area-inset-top) etc. on fixed headers/footers/FAB. Check iOS notch and Android gesture bar.
No horizontal scroll at 320px. Test with devtools device mode.
Fluid type — clamp(1rem, 0.9rem + 0.5vw, 1.125rem) for body where scale matters; fixed px for small UI text (labels, captions).
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.
Hover-less devices — every hover affordance has a non-hover equivalent. @media (hover: hover) to scope desktop-only effects.
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.
Images — aspect-ratio set; srcset + sizes for different viewports; loading="lazy" below the fold; fetchpriority="high" on hero.
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).

More from this repository

same repository

ui-craft

educlopez/ui-craft

Use for UI design and implementation work to avoid generic AI-looking interfaces. Provides anti-slop rules, a required discovery phase before coding, and guidance for layout, typography, color, motion, accessibility, dashboards, tables, landing pages, theming, and polish. Trigger when editing UI code or reviewing and refining components, pages, screens, layouts, animations, responsive behavior, or design systems.

2026-07-15207

bolder

educlopez/ui-craft

"Amplify personality — raises layout variance and motion, strengthens typography and one signature detail, without slop. Use when the UI works but feels safe, flat, or "template-y", or when the user says "bolder", "more personality", "more creative", or "make it pop" (still professional). Invoke when the user asks for bolder on their UI, or mentions 'bolder' alongside design / UI / frontend work."

2026-07-05207

brief

educlopez/ui-craft

Write or update the project's durable design brief at .ui-craft/brief.md. Invoke when the user asks for brief on their UI, or mentions 'brief' alongside design / UI / frontend work.

2026-07-05207

craft

educlopez/ui-craft

"One-shot build pipeline for a complete surface from an outcome recipe — inputs (or defaults) → composition → theme → build order → acceptance bar. Use when the user asks for a whole surface ("build me a dashboard", "hazme un dashboard") and expects a shippable result, not component-level help. Invoke when the user asks for craft on their UI, or mentions 'craft' alongside design / UI / frontend work."

2026-07-05207

finalize

educlopez/ui-craft

Pre-ship gate — runs detector, verifies brief and tokens, applies the 10-pass finish bar, ranks findings by feedback hierarchy. Use when the user wants to ship, merge, or finalize a surface and needs a verdict (READY / NOT READY / BLOCKED) before committing. Invoke when the user asks for finalize on their UI, or mentions 'finalize' alongside design / UI / frontend work.

2026-07-05207

polish

educlopez/ui-craft

"Final craft pass applying the compound details from the polish checklist — micro-typography, spacing rhythm, hover states, and a signature detail — directly to code. Use when the surface is functionally complete but feels unfinished, or when the user says "polish this" / "it looks generic" / "add the final touches". Invoke when the user asks for polish on their UI, or mentions 'polish' alongside design / UI / frontend work."

2026-07-05207

name	adapt
description	"Responsive layout pass covering breakpoints, touch targets, safe areas, and fluid type. Use when the UI has layout or touch issues on mobile/tablet, when adding a new screen that hasn't been tested across viewports, or when the user says "make it responsive" / "fix mobile layout". Invoke when the user asks for adapt on their UI, or mentions 'adapt' alongside design / UI / frontend work."

Adapt the UI at the target the user described across devices. Load the ui-craft skill and read references/responsive.md.

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

Checklist:

Breakpoints — use project's existing system (Tailwind: sm md lg xl; CSS: container queries preferred over media queries for components). No magic widths.
Touch — tap targets ≥ 44×44px (min-h-11 min-w-11). Touch zones don't overlap. touch-action: manipulation on interactive elements.
Safe areas — padding-top: env(safe-area-inset-top) etc. on fixed headers/footers/FAB. Check iOS notch and Android gesture bar.
No horizontal scroll at 320px. Test with devtools device mode.
Fluid type — clamp(1rem, 0.9rem + 0.5vw, 1.125rem) for body where scale matters; fixed px for small UI text (labels, captions).
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.
Hover-less devices — every hover affordance has a non-hover equivalent. @media (hover: hover) to scope desktop-only effects.
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.
Images — aspect-ratio set; srcset + sizes for different viewports; loading="lazy" below the fold; fetchpriority="high" on hero.
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).