Experience Design

Experience Design helps product teams turn an understood user need into a coherent, reviewable design before frontend implementation. Start naturally: “Map what a new customer goes through, turn the painful step into screens, and show me what still needs design.” You get durable design artifacts and an explicit next design decision, not framework code or a finished implementation.

Understand the experience

Map the customer’s end-to-end path, connect it to backstage services, document an internal operation, or orient to the design work that already exists. The result is evidence and structure the team can design from.

Turn intent into screens

Derive principles, screen sequence, hierarchy, behavior, and edge paths. The result is a connected set of screen-level decisions that can survive a handoff.

Set the creative and content direction

Name the visual direction and token taxonomy. Decide the surface’s message, brand register, and acquisition-copy goals, then critique the rendered design against the shared quality floor. Copy routes by altitude: brand register → surface message and structure → acquisition-surface copy goals → product UI strings.

Design for the surface you actually have

Choose the matching method for a marketing page, documentation system, dashboard, editorial page, marketplace, or sustained-work workspace instead of applying one generic page recipe.

Know when to leave this pack

• Product strategy: which market, audience, positioning, adoption hypothesis, or organization-level direction to pursue.
• Product-engineering shaping: framing, appetite, risks, scope, solution options, or a committed bet.
• Frontend engineering: approved design that is ready for HTML, CSS, components, data bindings, or build evidence.

A forked-context experience-reviewer supplies the independent design pass; it is an agent, not a twenty-first skill.

agentbundle install --pack experience-design --scope user

claude plugin install experience-design@agent-ready-repo