agentleFS
joaoajmatosjoaoajmatos/ze/.claude/skills/ze-web-verify/SKILL.md

ze-web-verify

Skill2 starsChanged 47 days agoUnlicenseView on GitHub

Verifies a ze-web change in the agent's own Maestri portal, with a screenshot, before it goes to review. Use when finishing or reviewing any change under apps/ze-web, packages/ze-ui or packages/ze-client, or when asked to check that a web page renders.

  • Reads credentials

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 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.

  • 2

    Very specific

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

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

    Run the printed maestri portal create ...

    line 14
  2. Distinctive:

    Put the screenshot paths and what you checked in your Handoffs note.

    line 18
  3. Very specific:

    Stop the server when done: scripts/process/web_portal.sh --stop <PORT>.

    line 21

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

Verify web changes in your own portal

Not "should render": snapshot it. Run the steps in order.

  1. Serve your checkout on your assigned port (the Maestro assigns ports from 5192 up): scripts/process/web_portal.sh <PORT> "<Name> Web" It starts vite from this checkout with --strictPort, finds a Node 20+, waits for 200, and prints the portal command.
  2. Prove it answers: scripts/process/web_portal.sh --check <PORT> must exit 0.
  3. Run the printed maestri portal create ... command. For phone checks, add a second portal with --size 390x844.
  4. Backend is the shared test API at http://127.0.0.1:8010 (DB ze_e2e_web). On the setup screen use that Server URL and the ZE_API_KEY from ~/coding/ze/apps/ze-api/.env. Never paste the key into commits, notes or handoffs. If 8010 is down, tell the Maestro. Never start an API on 8000 or touch DB ze.
  5. For each story: maestri portal navigate, snapshot, click/fill, logs-start then logs (no console errors), screenshot.
  6. Hand the screenshot to the gate: make process-ready PORTAL_SHOT=<path to png>. The receipt records it.
  7. Put the screenshot paths and what you checked in your Handoffs note. Reviewers re-check in their own portal.
  8. Reply to the Maestro with portal ok <PORT> plus the maestri portal info line.

Stop the server when done: scripts/process/web_portal.sh --stop <PORT>.

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.