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
In this repository43 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- system-one-modelsSkill
- animateSkill
- animation-performanceSkill
- animation-vocabularySkill
- apple-designSkill
- break-uiSkill
- codebase-designSkill
- correctSkill
- diagram-designSkill
- doc-styleSkill
- domain-modelingSkill
- emil-design-engSkill
- find-animation-opportunitiesSkill
- grillingSkill
- impeccableSkill
- improve-animationsSkill
- improve-codebase-architectureSkill
- pick-ui-librarySkill
- prototypeSkill
- researchSkill
- review-animationsSkill
- speckit-analyzeSkill
- speckit-checklistSkill
- speckit-clarifySkill
- speckit-constitutionSkill
- speckit-convergeSkill
- speckit-implementSkill
- speckit-planSkill
- speckit-process-after-implementSkill
- speckit-process-after-tasksSkill
- speckit-specifySkill
- speckit-tasksSkill
- speckit-taskstoissuesSkill
- design-taste-frontendSkill
- ui-ux-pro-maxSkill
- ze-advisorSkill
- ze-continueSkill
- ze-land-floorSkill
- ze-pauseSkill
- ze-recruitSkill
- ze-request-reviewSkill
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
- Very specific: line 14
Run the printed maestri portal create ...
- Distinctive: line 18
Put the screenshot paths and what you checked in your Handoffs note.
- Very specific: line 21
Stop the server when done: scripts/process/web_portal.sh --stop <PORT>.
≈ “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.
Files
Verify web changes in your own portal
Not "should render": snapshot it. Run the steps in order.
- 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. - Prove it answers:
scripts/process/web_portal.sh --check <PORT>must exit 0. - Run the printed
maestri portal create ...command. For phone checks, add a second portal with--size 390x844. - Backend is the shared test API at
http://127.0.0.1:8010(DBze_e2e_web). On the setup screen use that Server URL and theZE_API_KEYfrom~/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 DBze. - For each story:
maestri portal navigate,snapshot,click/fill,logs-startthenlogs(no console errors),screenshot. - Hand the screenshot to the gate:
make process-ready PORTAL_SHOT=<path to png>. The receipt records it. - Put the screenshot paths and what you checked in your Handoffs note. Reviewers re-check in their own portal.
- Reply to the Maestro with
portal ok <PORT>plus themaestri portal infoline.
Stop the server when done: scripts/process/web_portal.sh --stop <PORT>.
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.

