`experience-design` — guides

Use this pack to move from an understood user need to design decisions a builder can implement and an independent reviewer can assess. Start with the job in your own words: “Map what a new customer goes through, turn the painful step into screens, and tell me which design decision comes next.” You receive durable design artifacts and an explicit next step; the pack does not write frontend code or choose the product bet for you.

Choose by job

Understand what happens. Use journey-mapping for the customer’s path, service-blueprint for the people and systems behind it, process-mapping for an internal operation, and experience-status to orient to existing design artifacts.

Turn intent into a screen experience. Use design-principles for durable arbitration rules, user-flow for screen sequence and edge paths, information-architecture for hierarchy and wayfinding, and interaction-design for behavior within a screen or component.

Set direction and assess the result. Use creative-direction for visual goals, design-system for the token taxonomy, content-design for the surface’s message and narrative structure, and design-review for an authoring-time critique. Copy has four distinct layers: tone-of-voice owns the brand register; content-design owns what a surface must communicate; copy-direction owns copy goals for one acquisition surface; ux-writing in product engineering owns product UI strings.

Match the surface genre. Use conversion-design for marketing, documentation-design for docs and help, analytical-design for dashboards, informational-design for editorial reading, marketplace-design for multi-party exchange, and workspace-design for sustained professional work.

That is the complete 20-skill inventory. Every skill ships a portable method, not framework code, styling syntax, values tables, or pixel comps.

Leave the pack at the discipline boundary

• Market, audience, positioning, adoption, and organization-level direction belong to product strategy.
• Framing, appetite, risks, scope, solution options, and bet commitment belong to product-engineering shaping.
• HTML, CSS, components, data bindings, and build evidence belong to frontend engineering after the design is approved.

Read The experience thread for the mental model, or Thread a feature from journey to screens to run the connective path end to end.

Explanation

• The experience thread — the connective
  • craft skills, why the discipline is framework-agnostic, the shared quality floor, the macro/micro carve, and how design intent feeds the build.

How-to

• Thread a feature from journey to screens — map the journey, derive the screen flow and per-screen briefs, blueprint the services, design and critique each screen, and get an independent review.
• Route copy work across content-design, copy-direction, ux-writing, and tone-of-voice — which skill owns what across the four-way copy boundary.

Reference

• The skills, the reviewer, and the quality-floor — what each skill and the experience-reviewer agent trigger on, what they produce, the [design] layout, and the shared floor they all clear.

---

Installing and upgrading live in ../_shared/.