agentsclimarketplace
Sign in

Frontend responsive

Skill tmj-90/gaffer/runner/skills/frontend-responsive

Use when a ticket requires a layout to work across screen sizes — mobile/tablet/desktop, fluid typography, breakpoint behaviour, or fixing overflow and touch-target issues. Invoke for "make X responsive", "fix the mobile layout", "support tablet", or when adding any layout that must adapt.From its SKILL.md

Install
npx -y skills add tmj-90/gaffer --skill frontend-responsive

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.4 KB, 470 tokens by cl100k_base, as published. Nobody here has run it

Make the layout responsive

Make the affected UI adapt cleanly from small to large viewports with no overflow, readable type at every size, and touch-friendly targets.

Steps

  1. Read the lore first. Call search_lore (Memory MCP) for the repo's breakpoint scale, spacing tokens, and responsive conventions (container queries, grid system, mobile-first vs desktop-first).
  2. Work mobile-first. Start from the smallest target and layer enhancements up through the repo's existing breakpoints — don't invent new ones.
  3. Prefer fluid layout primitives (flex/grid, clamp() type and spacing, intrinsic sizing) over fixed pixel widths and one-off media queries.
  4. Kill overflow. Constrain media and long text (max-width, min-width: 0, wrapping); verify no horizontal scroll at any width.
  5. Size for touch. Interactive targets ≥ 44×44px on touch; verify tap spacing.
  6. Verify across widths. Check the breakpoints the repo cares about (e.g. 320, 375, 768, 1024, 1440); confirm no overflow and that content reflows sensibly.
  7. Evidence. Record the verification (screenshots or assertions) via the record-evidence skill, run tests + lint, and submit for review.

Rules

  • Mobile-first; reuse the repo's breakpoint scale and tokens — no magic pixel values.
  • No horizontal overflow at any supported width.
  • Fluid primitives over a thicket of fixed media queries.
  • Pair with frontend-a11y so responsive changes keep focus order and labels intact.

Capture lore

This skill is one of the places durable, reusable knowledge naturally surfaces: A responsive convention this repo follows — its breakpoint scale, a layout primitive it prefers, or a fluid-sizing rule. That kind of fact is lore. Capture it via the lore-capture protocol in your brief (CLAUDE.factory.md, step 11 "Memory contribution"): call the Memory MCP suggest_lore once at the close of your work — reusable conventions, gotchas, decisions, and boundaries only, never per-ticket trivia.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most design frontend skills give in 470 tokens

Counted across 1,169 of the 1,878 authors here whose files we hold, read 2026-08-07

  • Use CSS variables for color consistencyin 72 of 1169, across 23 files
  • Commit to one bold aesthetic direction before codingin 72 of 1169, across 27 files
  • Match implementation complexity to the aesthetic visionin 70 of 1169, across 20 files
  • Add atmospheric background effects and texturesin 57 of 1169, across 9 files
  • Use unexpected spatial compositions and layoutsin 56 of 1169, across 8 files
  • Implement real working codein 55 of 1169, across 7 files
  • Vary themes and aesthetics across different designsin 48 of 1169, across 7 files
  • Launch chromium in headless modein 47 of 1169, across 4 files
  • Close the browser when donein 47 of 1169, across 4 files
  • Run provided scripts with help flag firstin 47 of 1169, across 4 files
  • Wait for network idle statein 47 of 1169, across 4 files
  • Use descriptive selectors for elementsin 47 of 1169, across 4 files

Said here and by no other author read

  • search lore for existing breakpoint conventions
  • prefer fluid layout primitives over fixed widths
  • constrain media and text to prevent overflow
  • record verification evidence
  • pair changes with accessibility checks
  • suggest reusable responsive conventions as lore

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,506. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.