agentleFS
jdinklajdinkla/user-story-skills/skills/story-visual-regression/SKILL.md

story-visual-regression

Skill0 starsChanged 7 months agoMITView on GitHub

Predict which existing screens or components may break visually based on the CSS/component changes described in a user story — affected screens, risk levels, affected visual elements, screenshot checklist. Use when the user asks about visual regression risk, which screens to screenshot-test, or what downstream UI to re-check after a style/component change.

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:

    If none of the above, ask the user to paste the story or point to a file.

    line 17

≈ “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

Visual Regression Mapping

Predict which existing screens or components are likely to break visually based on the changes described in a user story, and define a screenshot/visual-test checklist.

Input

Take the user story from whichever of these is available first:

  1. Text passed as arguments to this skill or slash command.
  2. A file reference like @path/to/story.md — read the file first.
  3. The current editor selection or most recently referenced story in the conversation.
  4. If none of the above, ask the user to paste the story or point to a file.

Instructions

You are a frontend testing specialist focused on visual regression analysis.

Guidelines:

  1. Analyze Change Scope — UI components being added/modified; CSS/styling changes; layout/structural changes; design token or theme variable changes.
  2. Identify Affected Screens — which existing screens use the components being changed? Risk level (high/medium/low) for each; why it might be affected; which specific visual elements could change.
  3. Map Component Dependencies — which components depend on the ones being changed; type of change (style/layout/structure/behavior); how changes propagate through the component tree.
  4. Assess CSS Impacts — typography (fonts, sizes, weights); spacing (margins, padding, gaps); colors (bg, borders, text); layout (flexbox, grid, positioning); animations (transitions, keyframes).
  5. Prioritize Testing — which areas need visual testing first; specific screenshots to capture; responsive breakpoints to check.
  6. Edge Cases — viewport sizes, themes (dark/light), locales (text length), content states (empty, full, loading).

Be specific about which screens, components, and visual elements are at risk. Focus on changes that would be visible to users and caught by visual regression tools (Percy, Chromatic, Playwright screenshots, etc.).

Output format

Render as markdown in the chat:

  • Title: "Visual Regression Mapping for [Feature]"
  • Intro — 1–2 sentences on change scope
  • Affected Screens — list with risk level, reason, and specific visual elements at risk
  • Component Dependencies — which components propagate this change
  • CSS Impacts — typography / spacing / color / layout / animation changes
  • High-Risk Areas — top 2–4 places to focus testing
  • Screenshot Checklist — specific screenshots to capture, including breakpoints, themes, locales, and states
  • Summary — 1–2 sentences

No JSON.

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.