Produce the EdgeQuake WebUI UX/UI map one route at a time (capture screenshots, then immediately write per-page docs and per-page analysis requests). Use when asked to map UI, capture screens page-by-page, avoid agent memory saturation, or generate ux_ui_map artifacts.
79
100%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Use this skill when the user asks to:
ux_ui_map/ artifactsProcess exactly one route at a time:
ux_ui_map/pages/ux_ui_map/requests/Do not keep previous pages in working context.
Write these files as you go:
ux_ui_map/pages/{page}.md (page documentation)ux_ui_map/screenshots/{page}/...png (screenshots)ux_ui_map/requests/{page}.json (analysis request inputs)ux_ui_map/capture-index.jsonl (append-only log, one JSON object per captured route)Templates:
Helper script:
Scaffold the expected files/folders for one page:
node .github/skills/ux-ui-map-page-by-page/scripts/page_artifacts.mjs scaffold --page dashboard --route /
Validate that a page has its 3 required screenshots and docs:
node .github/skills/ux-ui-map-page-by-page/scripts/page_artifacts.mjs validate --page dashboard
{page} is a stable slug (e.g. dashboard, documents, query, graph, settings, api-explorer, login).desktop.png, tablet.png, mobile.png.ux_ui_map/pages/{page}.md created/updatedux_ui_map/requests/{page}.json created/updatedux_ui_map/capture-index.jsonlux_ui_map/ artifacts for all routes.”62e6adb
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.