agentleFS
TheGoat395TheGoat395/Codex-Skills/skills/responsive-visual-polish-qa/SKILL.md

responsive-visual-polish-qa

Skill136 starsChanged 5 months agoMITView on GitHub

Verify composition across breakpoints.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read responsive visual polish qa guide for the selected workflow.

    line 18

≈ “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 Visual Polish QA

Purpose

Make cross-breakpoint behavior the quality gate. This skill owns responsive composition, not every category of frontend polish.

Scoped execution

Apply the shared web contract once when execution crosses phases; reuse it if already read. Load only the specialist guidance relevant to the requested surface and deliverable.

Detailed Guide

Read responsive visual polish qa guide for the selected workflow. Apply only the requested surface; review-only work reports findings, while authorized changes continue through implementation and relevant verification.

Scope and evidence

Own cross-breakpoint invariants: hierarchy, wrapping, grids, crops, navigation and interaction composition. Advisory/source-only review is allowed with visual limits. Reuse the browser evidence matrix; do not rerun all release checks.

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.