agentleFS
divyanshu-iitiandivyanshu-iitian/agent-website-design-skills/responsive-ui-qa/SKILL.md

responsive-ui-qa

Skill2 starsChanged 4 months agoMITView on GitHub

Inspect, diagnose, fix, and verify responsive frontend defects across routes, states, containers, and input modes. Use for mobile or desktop QA, overflow, overlap, broken navigation, unstable grids, clipped text, blank media, viewport regressions, screenshot comparison, and post-implementation visual verification.

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 9 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the repository's run and testing instructions.

    line 12
  2. Distinctive:

    default, loading, empty, error, long-content, and interactive states.

    line 15
  3. Distinctive:

    Test content stress: long labels, unbroken strings, localization expansion, missing/large media, validation text, and dynamic lists.

    line 24
  4. Distinctive:

    Test input and preference modes: keyboard, touch-sized targets, focus visibility, zoom when feasible, and reduced motion.

    line 25
  5. Very specific:

    Prefer intrinsic layout, wrapping, minmax(), min-width: 0, max-width, aspect-ratio, and container-aware rules.

    line 31
  6. Distinctive:

    Do not "fix" overflow by globally hiding it or shrinking text below readability.

    line 33
  7. Distinctive:

    Keep fixed or sticky UI from covering focused elements and anchored content.

    line 35
  8. Distinctive:

    Verify canvas, WebGL, video, charts, maps, and embeds by inspecting rendered pixels and resize behavior.

    line 36
  9. Distinctive:

    Evidence: - before/after screenshots or explicit browser observations.

    line 46
  10. Distinctive:

    Read references/qa-checklist.md for the final cross-viewport and interaction pass.

    line 51

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Responsive UI QA

Find root causes, not screenshot-specific patches. Produce evidence that the reported state works after the fix.

Workflow

  1. Read the repository's run and testing instructions. Start the app with its normal command.
  2. Build a compact test matrix:
    • critical routes or components;
    • default, loading, empty, error, long-content, and interactive states;
    • narrow mobile, mobile, tablet or narrow container, desktop, and wide desktop as relevant.
  3. Reproduce the exact reported defect before editing. Capture the viewport, route, state, and interaction.
  4. Inspect layout mechanics: containing block, grid/flex constraints, intrinsic size, min-width, wrapping, positioning, stacking, overflow, and fixed/sticky offsets.
  5. Classify severity:
    • Blocker - action or content is inaccessible;
    • Major - interaction or comprehension is materially impaired;
    • Minor - visible polish defect without task failure.
  6. Fix the underlying constraint with the smallest coherent change. Avoid viewport-specific offsets unless the design genuinely changes there.
  7. Test content stress: long labels, unbroken strings, localization expansion, missing/large media, validation text, and dynamic lists.
  8. Test input and preference modes: keyboard, touch-sized targets, focus visibility, zoom when feasible, and reduced motion.
  9. Re-run the failed case plus adjacent widths and states. Check that no new horizontal scroll or hidden content was introduced.
  10. Report evidence, remaining risks, and anything not testable locally.

Fix Rules

  • Prefer intrinsic layout, wrapping, minmax(), min-width: 0, max-width, aspect-ratio, and container-aware rules.
  • Change information architecture at breakpoints when reflow alone is insufficient.
  • Do not "fix" overflow by globally hiding it or shrinking text below readability.
  • Reserve fixed dimensions for controls and media with a real size contract.
  • Keep fixed or sticky UI from covering focused elements and anchored content.
  • Verify canvas, WebGL, video, charts, maps, and embeds by inspecting rendered pixels and resize behavior.
  • Preserve behavior at the exact state that triggered the bug.

Delivery Contract

Return:

  1. Matrix tested - route/state/viewport/input.
  2. Findings - severity, reproduction, and root cause.
  3. Fixes - files changed and why the constraint is correct.
  4. Evidence - before/after screenshots or explicit browser observations.
  5. Residual risk - untested browsers, data states, or environments.

Reference

Read references/qa-checklist.md for the final cross-viewport and interaction pass.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.