Axure Prototype Requirements Review

Problem to Solve

Axure prototypes often contain PRD content, but page drawings do not fully specify field defaults, empty states, permission boundaries, or state transitions. Manual review tends to miss unstated rules and may flag project conventions as defects.

How It Works

The skill connects to an already open local Axure prototype URL through chrome-devtools, avoiding a new agent-browser session. It extracts the site map, switches pages by setting iframe.src, reads visible text, and writes a page inventory to page-inventory.json. It then checks each page against layered rules for fields, empty states, interaction feedback, timing rules, data sources, business rules, and triggers. Next, it compares cross-page states, terminology, role permissions, first-release scope, and boundary conditions, then summarizes findings.jsonl into a Markdown recommendations report.

Scope and Caveats

It is intended for current p1 functionality; p2/p3 pages are recorded only, and deprecated directories are excluded. The review respects date markers and system conventions such as the edu administrator role, so project-specific rules are not treated as defects. Findings should be falsifiable, point to specific pages and fields, and carry High, Medium, or Low severity handling advice.