adapt

Name: adapt
Author: educlopez

102installs8forks

How to install adapt?

educlopez/ui-craft/adapt

$npx -y skills add educlopez/ui-craft --skill adapt

Installs into the current project.

Summary

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"

Files · 1

View on GitHub

SKILL.md

1	<!-- HARNESS MIRROR — do not edit here. Canonical source: skills/ or commands/. After editing source, copy into cli/assets/<harness>/ and repo-root harness mirrors. -->
2
3	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.
4
5	Adapt the UI at the target the user described across devices. Load the `ui-craft` skill and read `references/responsive.md`.
6
7	Work mobile-first. Don't shrink desktop; grow from mobile.
8
9	Checklist:
10
11	1. Breakpoints — use project's existing system (Tailwind: `sm md lg xl`; CSS: container queries preferred over media queries for components). No magic widths.
12	2. Touch — tap targets ≥ 44×44px (`min-h-11 min-w-11`). Touch zones don't overlap. `touch-action: manipulation` on interactive elements.
13	3. Safe areas — `padding-top: env(safe-area-inset-top)` etc. on fixed headers/footers/FAB. Check iOS notch and Android gesture bar.
14	4. No horizontal scroll at 320px. Test with devtools device mode.
15	5. Fluid type — `clamp(1rem, 0.9rem + 0.5vw, 1.125rem)` for body where scale matters; fixed px for small UI text (labels, captions).
16	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.
17	7. Hover-less devices — every hover affordance has a non-hover equivalent. `@media (hover: hover)` to scope desktop-only effects.
18	8. Density shifts with viewport — honor `VISUAL_DENSITY` differently per breakpoint:
19	- `VISUAL_DENSITY ≤ 3` → fewer columns and wider spacing even at desktop widths.
20	- `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)`).
21	- Mobile always trends toward 1 column and wider spacing regardless of the knob value.
22	9. Images — `aspect-ratio` set; `srcset` + `sizes` for different viewports; `loading="lazy"` below the fold; `fetchpriority="high"` on hero.
23	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.
24
25	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).

People who liked this also viewed

6 picks

Type

adapt

102installs8forks

View on GitHub

How to install adapt?

educlopez/ui-craft/adapt

$npx -y skills add educlopez/ui-craft --skill adapt

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	<!-- HARNESS MIRROR — do not edit here. Canonical source: skills/ or commands/. After editing source, copy into cli/assets/<harness>/ and repo-root harness mirrors. -->
2
3	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.
4
5	Adapt the UI at the target the user described across devices. Load the `ui-craft` skill and read `references/responsive.md`.
6
7	Work mobile-first. Don't shrink desktop; grow from mobile.
8
9	Checklist:
10
11	1. Breakpoints — use project's existing system (Tailwind: `sm md lg xl`; CSS: container queries preferred over media queries for components). No magic widths.
12	2. Touch — tap targets ≥ 44×44px (`min-h-11 min-w-11`). Touch zones don't overlap. `touch-action: manipulation` on interactive elements.
13	3. Safe areas — `padding-top: env(safe-area-inset-top)` etc. on fixed headers/footers/FAB. Check iOS notch and Android gesture bar.
14	4. No horizontal scroll at 320px. Test with devtools device mode.
15	5. Fluid type — `clamp(1rem, 0.9rem + 0.5vw, 1.125rem)` for body where scale matters; fixed px for small UI text (labels, captions).
16	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.
17	7. Hover-less devices — every hover affordance has a non-hover equivalent. `@media (hover: hover)` to scope desktop-only effects.
18	8. Density shifts with viewport — honor `VISUAL_DENSITY` differently per breakpoint:
19	- `VISUAL_DENSITY ≤ 3` → fewer columns and wider spacing even at desktop widths.
20	- `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)`).
21	- Mobile always trends toward 1 column and wider spacing regardless of the knob value.
22	9. Images — `aspect-ratio` set; `srcset` + `sizes` for different viewports; `loading="lazy"` below the fold; `fetchpriority="high"` on hero.
23	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.
24
25	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).

People who liked this also viewed

6 picks

Type