{"id":77031,"plugin_id":"plugins_6ab4123730588191bc9267b9458b2670","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-03T00:12:19.994Z","digest":"5dfa8f9f0f4e67f7b19cc41b115a6ef8bda9ce48aaf34aca08c540a5d47b6b82","against":null,"payload":{"description":"Design user journeys, information architecture, UX states and accessibility for web or native apps.","included_files":[],"name":"design-user-journey","skill_md_contents":"---\nname: design-user-journey\ndescription: Design user journeys, information architecture, UX states and accessibility for web or native apps.\n---\n\n# Design User Journey\n\n## When to use\nDesign user journeys, information architecture, UX states and accessibility for web or native apps.\n\n## Workflow\nTranslate product goals into primary jobs, navigation and ordered steps. Create a flow for the first-value experience, repeated use and important exception paths. Define loading, empty, validation, permission, offline, error and recovery states only where relevant. Define responsive and native platform behavior, keyboard/touch/accessibility and content priorities.\n\nOutput flow stages, screens or surfaces, inputs/actions, state table, usability risks and acceptance criteria. Use `../../references/ux-and-accessibility.md` and `../../templates/ux-flow.md`. Never use aesthetic trends as a substitute for interaction design.\n\n## Deliverable and truthfulness\nLead with the decision or result, then show supporting evidence, explicit assumptions, risks, and a concrete next step. Adapt depth to the user's ask. If required tools or source material are missing, disclose the limit; do not simulate inspection, implementation or research. Never write/modify/deploy without relevant authorization.\n\nRelevant reference: `../../references/ux-and-accessibility.md`.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}