← ClaudeAtlas

astra-uxlisted

Capture the owner's user journeys before any spec is written: who the actors are, what each one does on which surface, what they must see, and the states a surface can be in. Writes journeys UJ-n and actors into the project's PRD so the Shaper and every ticket use the same names. Use in the pane where the owner speaks (BA or Thomas) when an effort changes a surface someone looks at. Captures, never authors.
thientranhung/astragentic · ★ 4 · Web & Frontend · score 70
Install: claude install-skill thientranhung/astragentic
# UX: journeys from the owner's mouth Journeys are **captured, not authored**. The owner narrates a real session; you structure it. Never volunteer colours, patterns or a direction. A screenshot of the product as it runs today is a fact you may take; a sketch of what it should become is the owner's to give. ## When to run, when to skip Run when the effort changes a surface a person looks at and the PRD has no journey for it, or has one that no longer matches what the owner describes. Skip only when the owner says the surface is an internal single-operator tool and names that operator; write that line in the PRD. ## Rounds Use the frontier rounds of `astra-grill-with-docs`: ask the whole frontier, numbered, each with a recommended reading of what the owner just said, so "yes" confirms it. Facts are yours (what the code renders today, which routes exist); decisions are the owner's. 1. **Who.** Each actor by the name the project already uses. A new actor gets a name here and nowhere else; more than four is a sign of persona theatre, ask which two matter. 2. **The session.** "Tell me about the last time <actor> did this": entry state, the path in three to five beats, the climax (the moment the job is done or fails), the resolution. Persona context lives inline at the beats where it matters, never in a separate section. 3. **Form factor and stakes.** Desktop, mobile, extension, print; hobby, internal, launch, regulated. This decides how heavy the PRD gets. 4. **W