agentleFS
fimokleifimoklei/maestro/.claude/skills/verify-ui/SKILL.md

verify-ui

Skill1 starsChanged 47 days agoMITView on GitHub

Browser check of a cockpit change in `pnpm smoke` and Storybook — screenshots per state and theme, narrow width, 200% zoom, the primary flow. Use before calling any change to what `packages/web` renders done, or before committing it.

9 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use cut-release, write-tests and 1 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MicrosoftSkill

    cut-release

    Use this skill to cut an APM release from the current worktree: assess whether the cycle since the last tag warrants a patch or minor bump (semver discipline against the merged-since-last-tag diff), sanitize the [Unreleased] CHANGELOG block into a dated version block with one concise "so what" entry per merged PR (drop internal-only churn, consolidate duplicates), bump pyproject.toml + uv.lock, run the CI-mirror lint chain, and open the release PR. Activate on "ship a release", "cut v0.x", "release prep", "bump and PR", "open release PR", "what kind of release do we need", or any phrasing that ends in opening a release PR -- even when the user does not say "skill". Stops BEFORE tagging; tagging stays a human gate that triggers the release workflow. Refuses to bump to a major (>= 1.0.0) version without explicit operator confirmation.

    Also in 3 projects that use this

  • SentrySkill

    write-tests

    Write tests following project conventions. Use when adding new tests or modifying existing ones.

    Also in 3 projects that use this

  • MicrosoftSkill

    handoff

    Compact the current conversation into a handoff document for another agent to pick up.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run every step for a change that alters what packages/web renders.

    line 8
  2. Very specific:

    Start pnpm smoke in the background: this worktree's own ports, sandbox config, connect gate.

    line 12
  3. Distinctive:

    Read changed copy at a narrow width and at 200% zoom, in one theme.

    line 40
  4. Very specific:

    Run the verify-in-smoke checks before treating the screenshot as proof.

    line 45
  5. Very specific:

    Stop the run with pnpm smoke:stop and stop Storybook.

    line 50

“Common” is measured: kept by at least 6 in 10 of the 7 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

Verify a cockpit change

Run every step for a change that alters what packages/web renders. The check is done when step 8's commit-body list names every screen, state, theme, width and zoom the change touches, and each state you could not reach.

  1. Start pnpm smoke in the background: this worktree's own ports, sandbox config, connect gate.
    • A first-run screen → stop here.
    • A connected screen → pnpm smoke:ready; a deploy, Harness, Prompts or category state → --scenario <name>[,<name>] (each scenario and what it seeds: pnpm smoke:ready --list). Every scenario's Harness holds three released prompts, one with an Example and one in a category.
    • smoke:ready waits up to 60 s for the cockpit and prints its URL: run it straight after pnpm smoke, with no wait loop.
    • A newer or older release after seeding → pnpm smoke:release <tag> (v1.0.0, v1.1.0, v2.0.0).
    • In smoke, gh reads reach GitHub and its pull-request writes stop in the sandbox (scripts/smoke-gh.mjs), so a proposal opens no pull request.
  2. Screenshot the changed UI with agent-browser --session maestro-<worktree folder>, in each theme. Repeat it through a function, ab(){ agent-browser --session maestro-<worktree folder> "$@"; }, never a variable. Read a region as text with pnpm cockpit:snapshot "<selector>" [path], never a bare agent-browser snapshot. Open a hover card with ab mouse move <x> <y> on the badge's pixel position, read from a screenshot; take screen paths from packages/web/src/shell/screens.tsx.
  3. Screenshot every state the change touches (loading, empty, failure, disabled, selected, the longest realistic name) in the changed component's stories, in each theme. Add a missing state as a story (frontend.md → Stories). A state only the data-fetching screen shows: screenshot it in smoke, or name it as not reached. Start Storybook with pnpm --filter @maestro/web storybook --ci --no-open in the background and take the URL from its Local: line; open <url>/iframe.html?id=<story id>&viewMode=story&globals=theme:dark (story ids: <url>/index.json).
  4. Read changed copy at a narrow width and at 200% zoom, in one theme.
  5. Compare against the design source (design.md → Sources), then judge hierarchy, density, alignment and consistency. Fix each mismatch and screenshot again; done when a fresh screenshot shows none.
  6. Click through the screen's primary flow once in smoke.
  7. Run the verify-in-smoke checks before treating the screenshot as proof.
  8. Save each screenshot under ~/Pictures/maestro/<branch>/. In chat, give each as a full file:///Users/… link on its own line, without backticks. In the commit body, list what the check covered: each screen, state, theme, width and zoom. Name each state you could not reach.
  9. Stop the run with pnpm smoke:stop and stop Storybook.

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.