Can users find their way around — on desktop and on a phone?
Free & open · no signup · read-only — every stage ends by asking · nothing leaves your machine
Can a user find their way around? Map the navigation and menus, check what wins the eye on every screen, and confirm it all still works on a phone.
The conductor fetches each brief in turn and writes its report before moving on — later briefs can build on earlier findings. Or copy any single stage to run it alone.
4 reports in reports/, plus the run's own INDEX.md: NAVIGATION.md, MENUS.md, HIERARCHY.md, MOBILE.md. Feed them to the optional Studio to turn findings into commits, or run 28 · Roadmap Synthesis to merge them into one plan.
Copy the conductor into your agent inside the repo you want checked. It runs each Goal Prompt in sequence, honoring each one's ask-first rule.
The three questions every screen owes a user — where am I, where can I go, how do I get back — plus the nav that hides, the dead ends, and the jargon labels.
Menus, dropdowns, context menus, and command palettes — do they reveal what is inside, work by keyboard and thumb, and still find things as the list grows?
Where the eye actually goes versus where it should — focal points, size and weight and contrast doing real work, and the screens where everything shouts at once.
The product on a phone — whether layouts, touch targets, and performance hold up on small screens and real devices, or quietly assume a desktop.