Install any skill in seconds. Free to start, no credit card required.
Get Started Free →educlopez/adapt
Responsive layout pass covering breakpoints, touch targets, safe areas, and fluid type.
Passed 4 of 10 test cases with the skill, and 5 of 10 without it.
and 1 more in the full report
3 fixed5 passed either way9 still failing5 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
We just finished updating `src/components/CheckoutForm.tsx` for responsive breakpoints. What post-refactor verification tool or step should be run next to validate accessibility, performance, and touch target sizing?
| Checked | Without skill | With skill |
|---|---|---|
| The response explicitly names /audit as the next step. | Missed | Passed |
The instructions your model reads when the skill loads.
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:
sm md lg xl; CSS: container queries preferred over media queries for components). No magic widths.min-h-11 min-w-11). Touch zones don't overlap. touch-action: manipulation on interactive elements.padding-top: env(safe-area-inset-top) etc. on fixed headers/footers/FAB. Check iOS notch and Android gesture bar.clamp(1rem, 0.9rem + 0.5vw, 1.125rem) for body where scale matters; fixed px for small UI text (labels, captions).@container over viewport media queries for component-level responsiveness. Components that live in sidebars and main content behave differently at the same viewport width.@media (hover: hover) to scope desktop-only effects.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)).aspect-ratio set; srcset + sizes for different viewports; loading="lazy" below the fold; fetchpriority="high" on hero.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).
test cases passed, vs 5 / 10 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.