Advisory
council
Get independent expert views and an evidence-based synthesis on a consequential decision; advisory only.
Say “ask the council”
Advisory · Portable skill
Walk a working product as its user would and report observed friction with evidence; read-only.
npx skills add gaboesquivel/flow-skills -s experienceNatural language is the interface. Any of these, or your own words, reach the skill.
A walk of a running product as its user, with reproduction steps, impact, and confidence for each friction found (decision 0068). Writes nothing.
The authoritative, versioned instruction your agent follows, from skills/experience/SKILL.md.
What is it like to use this? Follow a real journey through a running product and report what a user would meet. This is observation, never repair: visual direction is design, correctness against intent is review, outcomes and direction are align, delivery is ship.
Name the user and one journey (from PRODUCT.md, DESIGN.md, the request, or your best guess, stated). Find something running: a preview URL, a local dev server, or the app in a simulator. Use the host's own browser, screenshot, or recording tools; add no dependency. With nothing to run, say so, and limit the report to what code and docs support, labeled that way.
Start from a realistic state: seeded or test data, never a production account or live mutation. Skip anything that sends, pays, or deletes real data.
Follow the journey as the user would: first load, the main task, then the states around it (loading, empty, error, slow, small screen, keyboard). At each step note what you saw, what you expected from the product and DESIGN.md, and any hesitation a person would have. Look at the result you report; when you cannot see it, say so.
Lead with the journey and the state you started from. Then findings, highest user impact first, each with:
Keep observations, hypotheses, and limits apart, and say what the walk did not cover. Include no praise padding and no finding you cannot reproduce. End by naming the skill that would act (build, design) and wait.
Read-only: never edit files, fix, install tools, or change data. It is not a metrics analysis, a code review, or a test suite, and nothing requires it.
Advisory
Get independent expert views and an evidence-based synthesis on a consequential decision; advisory only.
Say “ask the council”