agentleFS
Sign inStart free
rengwurengwu/wayfinder-maps/.claude/skills/verify/SKILL.md

verify

Skill137 starsChanged 4 months agoMITView on GitHub

Build, launch and drive wayfinder-maps to verify a change end-to-end (server + headless browser).

  • Installs packages

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 167 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Wait ~4s after goto: the constellation fades in over 2.2s (a plain --screenshot --virtual-time-budget capture shows HUD but NO stars — …

    line 44
  2. Distinctive:

    NOT reachable headlessly — manual Safari checklist:

    line 66

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

Verifying wayfinder-maps

Build & fixture

go build -o /tmp/wayfinder-maps ./cmd/wayfinder-maps

There is no sample map in the repo. Create an effort dir with map.md + tickets/NN-slug.md. Ticket format: YAML frontmatter (type:, blocked_by: [01], claimed_by:, undermined_by: [NN]) then # Title, ## Question; a ## Answer section with prose = resolved, ## Ruled out = out_of_scope. Map format: # Name, ## Destination, and fog under ## Not yet specified as - **Title.** clears-with: NN. Sanity-check the fixture with wayfinder-maps status <effort-dir>.

Launch

PORT=78xx /tmp/wayfinder-maps serve <effort-dir>   # pick a fresh port EVERY time

Gotcha: the user often has an instance (binary wm) already listening; a bind failure only shows in the log while curl happily talks to the OLD server — check the serve log says "serving", don't trust the port being answerable.

Dev mode: WAYFINDER_DEV=cmd/wayfinder-maps/web (path to web/ from cwd) serves the frontend from disk with Cache-Control: no-store instead of the go:embed copy.

Drive (GUI surface)

Playwright's cached headless shell works without a full playwright install:

cd <scratch> && npm i playwright-core
# executablePath: ~/Library/Caches/ms-playwright/chromium_headless_shell-*/chrome-headless-shell-mac-arm64/chrome-headless-shell
  • Wait ~4s after goto: the constellation fades in over 2.2s (a plain --screenshot --virtual-time-budget capture shows HUD but NO stars — artifact, not a bug).
  • App state is inside ES modules (not on window). To click a specific star, find it by pixel colour on the canvas (frontier glow is gold) — layout is deterministic (fixed PRNG seed), so positions repeat across runs.
  • Live-reload probe: append ## Answer\ntext to a ticket while the map is open; the 1.5s poller updates the HUD counts in ~2-3s.
  • Recents on the splash come from the user's real config — don't dismiss entries.

Flows worth driving: map render (all statuses + fog + edges), click star → panel markdown, data-goto cross-ticket link, Escape closes, wheel zoom (labels thin out), back button → splash/maplist.

WebKit

npx playwright-core install webkit (~77MB, cached in ms-playwright) then require("playwright-core").webkit.launch() — no executablePath needed. Covered headlessly: full map render, the label-alpha fade workaround (capture a frame ~600ms into loadMap: labels must be dim WITH the stars, not opaque over them), touch tap via a hasTouch context, wheel zoom, panel markdown.

NOT reachable headlessly — manual Safari checklist:

  • Trackpad pinch zooms the map, not the page (gesture* events; Playwright's WebKit cannot construct GestureEvent, and Chromium never fires them).
  • Touch pan/pinch on a real iOS device or simulator.

Download now (ZIP)

  • Other versions188 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 188

    1. react/react★ 252ksame name
    2. facebook/react★ 252ksame name
    3. garrytan/gstack★ 139ksame name
    4. oven-sh/bun★ 96ksame name
    5. anthropics/financial-services★ 41ksame name
    6. anthropics/financial-services-plugins★ 41ksame name
    7. Yeachan-Heo/oh-my-claude-sisyphus★ 40ksame name
    8. Yeachan-Heo/oh-my-claudecode★ 40ksame name
    9. anthropics/claude-quickstarts★ 19ksame name
    10. NVIDIA-NeMo/NeMo★ 19ksame name

    178 more not listed

    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.

  • Used alongsideProjects with it also use build-fix, external-context and 10 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.
    • diego-tobalinaSkill

      build-fix

      Fix build and compilation errors systematically. Run when build fails.

      Also in 6 projects that use this

    • Jurel89Skill

      external-context

      Invoke parallel document-specialist agents for external web searches and documentation lookup

      Also in 3 projects that use this

    • TheKREATORSSkill

      instinct-export

      Export instincts from project/global scope to a file

      Also in 3 projects that use this

    • TheKREATORSSkill

      instinct-import

      Import instincts from file or URL into project/global scope

      Also in 3 projects that use this

    • AviadPSkill

      risk-assess

      Assess the risk and blast radius of a proposed code change before implementing it. Evaluates CI impact, framework-wide vs localized scope, rollback path, and identifies blindspots. Use when user says "what's the risk", "is this safe", "assess the impact", "risk assess", "blast radius", or before applying framework-wide or CI-affecting changes. Do NOT use for code quality review (use code-quality) or plan validation (use design-validator).

      Also in 3 projects that use this

    • Jurel89Skill

      configure-notifications

      Wire Telegram / Discord / Slack notifications for copilot-omni run events (start, progress, completion, error)

      Also in 3 projects that use this

    • +2 more from Jurel89
  • In this repository13 other files it gives its agents.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

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.

Check your setup, free