← ClaudeAtlas

codoop-ux-walkthroughlisted

Simulate a real task from a chosen user persona and write an evidence-backed, non-blocking experience report. Use after building a user-facing feature, when reviewing a runnable product flow, or when product owners want user-perspective improvement ideas without changing code automatically.
Codoop/codoop-flow · ★ 4 · Web & Frontend · score 77
Install: claude install-skill Codoop/codoop-flow
# User Experience Walkthrough Run a qualitative, first-person walkthrough of a real product task. This skill produces hypotheses and improvement ideas for human review; it does **not** approve or reject a release, edit code, or create follow-up tickets. ## Core Rules - Read `$SKILL/../_shared/agents/persona-walkthrough.md` and use it as the persona prompt without changing its contents. - Distinguish what was observed from what was inferred. This is a qualitative simulation, not user research or statistical evidence. - Ground every finding in an actual screen, interaction, log, or explicitly stated limitation. Never invent product behavior or user feedback. - Keep the persona independent. The product's stated user role, goal, and acceptance criteria constrain the task being tested; they do not force the persona's identity. - Never change source code, tests, tickets, or scope as a result of this report. A human decides whether an idea becomes a later ticket. ## Inputs Gather the smallest useful context: 1. **Persona profile** — use one supplied by the user, or propose a concrete profile and label it as an assumption. It may be a core, adjacent, or stress-test user, but must plausibly use the product. 2. **Task contract** — when a ticket exists, read `module_prd.md` for its user role, goal, scope, and acceptance criteria. Otherwise ask for the task the persona should accomplish and what success means. 3. **Runnable evidence** — use the live app, bro