agentleFS
SebastianKuehnauSebastianKuehnau/sandbox-demo/.claude/skills/visual-verification/SKILL.md

visual-verification

Skill0 starsChanged 3 months agoUnlicenseView on GitHub

Visually verify an implemented use case using Playwright MCP. Use after implementing UI changes.

6 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions6 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 6

    1. poooi/poi★ 1.8ksame name
    2. nahid-sparktales/agent-dispatcher★ 59same name
    3. AkshitIreddy/agent-skills★ 1same name
    4. imMamdouhaboammar/Mimera★ 1same name
    5. HeyEddi-com/heyeddi-skills★ 0same name
    6. LucaDominici/arbiter★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository3 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 5

    Distinctive

    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:

    Use Playwright MCP to visually validate the implemented use case.

    line 8
  2. Distinctive:

    All the steps listed here must be done and all details are important.

    line 14
  3. Distinctive:

    Ensure the application is running

    line 16
  4. Distinctive:

    All text is clearly readable against its background (titles, labels, values, badges)

    line 35
  5. Distinctive:

    No backgrounds swallow their content text

    line 38

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “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 Verification

Use Playwright MCP to visually validate the implemented use case.

Unless the use case specifies a particular resolution, use 1920x1080 as the browser resolution.

Steps

All the steps listed here must be done and all details are important. The goal is to be thorough instead of quick.

  1. Ensure the application is running
  2. Navigate to every route defined in the use case's UI/Routes section
  3. Perform each step from the use case's main flow
  4. Take screenshots of key interaction points
  5. Validate the visual appearance according to the validation rules below
  6. Record results -- note any visual issues in the per-use-case checklist below

Validating Visual Appearance

The most important part is to verify what the user sees, i.e. a screenshot. DOM, CSS rules etc can be used as helpers but the screenshot is what really matters.

  1. Layout matches expectations (spacing, alignment, sizing)
  2. Spacing & padding are consistent -- content has appropriate breathing room, no cramped or excessively spaced areas. Verify that nested layouts (e.g., AppLayout > VerticalLayout > card) don't double-up padding or collapse it. Compare padding between similar views (e.g., all admin views should have the same content padding).
  3. Typography is readable and consistent
  4. Interactive elements are clearly identifiable
  5. Responsive behaviour works at common breakpoints (mobile, tablet, desktop)
  6. Text contrast and readability
  • All text is clearly readable against its background (titles, labels, values, badges)
  • Colored text (warning/error values, status badges) has sufficient contrast
  • Elements that inherit from a different color scheme (e.g., dark sidebar vs light content) render correctly -- CSS custom properties like var(--vaadin-background-color) may resolve differently depending on the inherited color scheme
  • No backgrounds swallow their content text

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.