Plan the user experience

Install this skill

npx skills add StanfordSpezi/SpeziVibe --skill digital-health-ux-planning

Or install all skills: npx skills add StanfordSpezi/SpeziVibe --skill '*'. See the Getting Started guide for tool-specific options.

Explore this skill in browser chat. Each button opens a new conversation; bring any earlier briefs with you and save the results yourself.

Try in ClaudeTry in ChatGPT

Need to paste the prompt yourself?

Browser prompt for digital-health-ux-planning

Please act as the SpeziVibe `digital-health-ux-planning` skill and walk me through it interactively.

STEP 1 — Fetch the skill instructions from this URL and read them carefully:
https://raw.githubusercontent.com/StanfordSpezi/SpeziVibe/main/skills/digital-health-ux-planning/SKILL.md

If the skill references other files or other skills by name, fetch them from the same repository:
- Files inside this skill (e.g. `references/foo.md`): https://raw.githubusercontent.com/StanfordSpezi/SpeziVibe/main/skills/digital-health-ux-planning/<relative-path>
- Other skills (e.g. `biodesign-needs-finding`): https://raw.githubusercontent.com/StanfordSpezi/SpeziVibe/main/skills/<skill-name>/SKILL.md

STEP 3 — Walk me through the skill interactively. When a step would normally save a markdown file to a project, show the file content in a code block instead so I can copy it. Don't simulate my answers — wait for me to respond.

If you cannot fetch the skill instructions or their reference files, ask me to paste them before proceeding.
Ask me to paste or attach any existing briefs you need. Do not claim to have read files, run commands, created a project, or tested an integration from this chat. Help me prepare the decisions and instructions, then hand off file and code work to my coding tool.

If your chat can’t open the skill link, open the instructions in a new tab and paste them into the chat.

Plans user experience journeys for digital health products. Platform-agnostic — focuses on user goals and decision points, not specific screens.

What It Covers

• User segments with constraints (literacy, fatigue, accessibility)
• Core journeys (discover, enroll, learn, consent, first task, ongoing use, review progress)
• Onboarding strategy (what's necessary vs. what can wait)
• Day-to-day workflow design
• Engagement principles (notifications, streaks, feedback — balanced against burden)
• Accessibility and inclusion notes
• Unresolved UX risks

Output

Produces docs/planning/ux-brief.md.

Example

AI:   Who are the primary users, and what are their core jobs
      when using this app?

You:  Post-transplant patients tracking their meds, and
      transplant coordinators reviewing adherence.

AI:   What constraints should we design around? For example —
      health literacy, fatigue, accessibility needs?

You:  Many patients are older, some have low health literacy,
      and they're often fatigued post-surgery.

AI:   Here's an onboarding approach for the patient journey:

      1. Welcome — one sentence on what the app does
      2. Account setup — email/password only, no unnecessary fields
      3. Medication list — import from care plan or enter manually
      4. First check-in — mark today's meds as taken (immediate value)
      5. Permissions — notifications only, deferred to after first use

      I'd defer any health data permissions or detailed profile
      setup until the patient has used the app for a day or two.
      Thoughts?

Limitations

• Does not produce wireframes or UI mockups
• Does not assume mobile tabs, specific screens, or frameworks
• Raises clinical safety and compliance questions but defers to other skills