UX UI Analyze Single Page
Designux-ui-analyze-single-pageUX UI Analyze Single Page is an Agent Skill for design published in the raphaelmansuy/edgequake repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Analyze exactly one captured UI page (from ux_ui_map screenshots + request JSON) and immediately write/update ux_ui_map/pages/{page}.md in neutral descriptive language. Use when asked to analyze screenshots, rewrite corresponding analysis immediately, or avoid memory/context saturation.
QUICK START
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/raphaelmansuy/edgequake/blob/HEAD/.github/skills/ux-ui-analyze-single-page/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/ux-ui-analyze-single-page, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Single-Page UI Analysis (Write Immediately)
When to use
Use this skill when:
- screenshots already exist and need describing
- the user wants analysis written out immediately after each page capture
- you must avoid carrying multi-page context
Inputs
ux_ui_map/requests/{page}.jsonux_ui_map/screenshots/{page}/desktop.pngux_ui_map/screenshots/{page}/tablet.pngux_ui_map/screenshots/{page}/mobile.png
Output
ux_ui_map/pages/{page}.md(created/updated immediately)
Rules
- Descriptive only: do not judge, do not recommend, do not assign severity.
- Focus on the hierarchy: page → regions → containers → components → elements.
- If information is uncertain from the screenshot, say so plainly (e.g., “Text is not legible at this resolution”).
- Do not reference previous pages unless explicitly asked.
Procedure
- Load the request JSON to confirm route and expected screenshot paths.
- Inspect desktop screenshot first (structure), then tablet/mobile (responsive changes).
- Write/update the page doc using the template at
ux_ui_map/pages/{page}.md:- Overview (route/title)
- ASCII layout diagram (approximate)
- Screenshot table
- Regions/containers/components
- Stop after writing this one page.
Example prompt that should trigger this skill
- “Analyze the dashboard screenshots and write the page doc now.”
- “Rewrite the corresponding analysis immediately for /documents.”