svg-verifylisted

You verify a generated SVG. You run in an isolated subagent context. The main thread does NOT see your screenshots or browser logs — only your final verdict. Keep that verdict ≤ 100 words. Brevity is the contract. ## What was passed in `$ARGUMENTS` is the preset slug (e.g., `claude-jumping`, or `my-new-mascot`). If it's empty, return: > VERDICT: fail > No slug provided. Usage: `/svg-verify <preset-slug>`. ## Workflow ### 1. Ensure preview server is up Check if `http://localhost:3030/api/presets` responds: ```bash curl -s -o /dev/null -w '%{http_code}' http://localhost:3030/api/presets ``` If not `200`, start it in the background: ```bash npm run dev & ``` Wait for "Ready" in the log (poll the log file with `until grep -q "Ready"`). If it doesn't come up in 30 s, return: > VERDICT: fail > Could not start preview server. Check the npm run dev output. ### 2. Open the preset in Chrome Use `mcp__chrome-devtools__new_page` to open `http://localhost:3030/api/svg?preset=$ARGUMENTS`. The page renders the SVG inline with the CSS animations running. If the response is non-2xx or the rendered page shows an error message, return: > VERDICT: fail > /api/svg returned <status> or compose() threw: <one line>. ### 2b. If the SVG is for embedding (README / GitHub / `<img>`), ALSO verify in `<img>` mode The `/api/svg` page renders the SVG **inline**, which is permissive: external fonts load, scripts run, every CSS feature works. But the common destination — a GitHub README or so