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
- crsmithdev/alephtheir own version, first seen Nov 16, 2026
- zillydev/claude-code-managertheir own version, first seen Nov 15, 2026
- whyashthakker/estacktheir own version, first seen Nov 8, 2026
- rpraharaj/ai-sdlctheir own version, first seen Nov 1, 2026
- rpraharaj/ai-engineertheir own version, first seen Nov 1, 2026
- jonmumm/skillstheir own version, first seen Oct 21, 2026
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.
MicrosoftSkillcut-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
SentrySkillwrite-tests
Write tests following project conventions. Use when adding new tests or modifying existing ones.
Also in 3 projects that use this
MicrosoftSkillhandoff
Compact the current conversation into a handoff document for another agent to pick up.
Also in 3 projects that use this
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 9
- ThisIsSadeghi/KMPilot★ 56same name
- oliver-kriska/prmarmot★ 10same name
- zillydev/claude-code-manager★ 4same name
- jonmumm/skills★ 3same name
- rpraharaj/ai-engineer★ 1same name
- ThisIsSadeghi/Loupe★ 1same name
- crsmithdev/aleph★ 0same name
- rpraharaj/ai-sdlc★ 0same name
- whyashthakker/estack★ 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 repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- worktreeSkill
- find-duplicate-abstractionsSkill
- verify-in-smokeSkill
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
- Very specific: line 8
Run every step for a change that alters what packages/web renders.
- Very specific: line 12
Start pnpm smoke in the background: this worktree's own ports, sandbox config, connect gate.
- Distinctive: line 40
Read changed copy at a narrow width and at 200% zoom, in one theme.
- Very specific: line 45
Run the verify-in-smoke checks before treating the screenshot as proof.
- Very specific: line 50
Stop the run with pnpm smoke:stop and stop Storybook.
“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.
Files
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.
- Start
pnpm smokein 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:readywaits up to 60 s for the cockpit and prints its URL: run it straight afterpnpm 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,
ghreads reach GitHub and its pull-request writes stop in the sandbox (scripts/smoke-gh.mjs), so a proposal opens no pull request.
- 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 withpnpm cockpit:snapshot "<selector>" [path], never a bareagent-browser snapshot. Open a hover card withab mouse move <x> <y>on the badge's pixel position, read from a screenshot; take screen paths frompackages/web/src/shell/screens.tsx. - 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 withpnpm --filter @maestro/web storybook --ci --no-openin the background and take the URL from itsLocal:line; open<url>/iframe.html?id=<story id>&viewMode=story&globals=theme:dark(story ids:<url>/index.json). - Read changed copy at a narrow width and at 200% zoom, in one theme.
- 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. - Click through the screen's primary flow once in smoke.
- Run the
verify-in-smokechecks before treating the screenshot as proof. - Save each screenshot under
~/Pictures/maestro/<branch>/. In chat, give each as a fullfile:///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. - Stop the run with
pnpm smoke:stopand stop Storybook.
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
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.

