journey

Designs end-to-end user flows, screen sequences, and multi-channel journey maps.

Updated Jul 21, 2026
One-click install
npx skills add https://github.com/rakedzior/rootine --skill journey-rakedzior
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: journey
Source: https://github.com/rakedzior/rootine/tree/main/agent/skills/journey
Command: npx skills add https://github.com/rakedzior/rootine --skill journey-rakedzior

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Designing coherent user experiences across screens, devices, and channels is hard: flows break at decision points, users abandon mid-task, and cross-channel handoffs lose context. This Skill structures the end-to-end design of any user journey so friction, edge cases, and variations are addressed before implementation. ## Core Features & Use Cases - End-to-End Flow Mapping: Designs complete journeys from entry point to outcome, including decision branches, error recovery paths, and re-entry after interruption. - Device & Context Variants: Adapts flows for mobile, web, TV, and embedded contexts, plus variations by user type, entry point, and market. - Visualization Output: Produces flow diagrams as self-contained HTML, Figma frames via MCP, or pencil.dev documents using a consistent design-token system. - Use Case: A product manager asks how new users should complete onboarding. The Skill maps the screen-by-screen flow, specifies copy and interaction states, defines success metrics, and renders an HTML diagram of the journey. ## Quick Start Ask the assistant to design the user flow for a specific task, such as "Design the onboarding flow for a new user signing up on mobile."

Frequently Asked Questions about journey

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a user onboarding flow?

Define the user's goal, entry point, and success metric first, then map each screen with its copy, CTAs, and error states. This Skill produces screen-by-screen flows with interaction specs, device variants, and an optional HTML or Figma diagram.

What tool can map multi-step user flows with decision branches?

This Skill maps complete journeys including decision gates, branch conditions, and error recovery paths. It outputs a structured markdown deliverable plus a visual diagram in self-contained HTML, Figma via MCP, or pencil.dev.

Does the journey skill support mobile and TV flow design?

Yes, it designs device-aware variants for mobile, web, TV, and embedded contexts. Each variant explains what changes and why, such as thumb-friendly layouts on mobile or 10-foot UI constraints on TV.

Can I get a Figma diagram of a user flow?

Yes, when you choose Figma output the Skill loads the figma-use skill and creates frames, connectors, and decision gates via the Figma MCP. HTML is the default format if no preference is stated.

What are the limitations of flow mapping without user research?

Flows designed without research rest on assumptions about user behavior and mental models. The Skill flags open questions for investigation and explicitly calls out assumptions rather than presenting untested flows as validated.