journey

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

Updated May 5, 2026
One-click install
npx skills add https://github.com/TheGeekosaurus/blogging-platform-2 --skill journey-thegeekosaurus
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: journey
Source: https://github.com/TheGeekosaurus/blogging-platform-2/tree/main/.agents/skills/journey
Command: npx skills add https://github.com/TheGeekosaurus/blogging-platform-2 --skill journey-thegeekosaurus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Designing coherent user experiences across screens, devices, and channels is hard to do systematically. This Skill structures the design of any user-facing flow — from signup to checkout to error recovery — so friction points, decision branches, and state transitions are explicitly mapped rather than improvised. ## Core Features & Use Cases - End-to-End Flow Mapping: Define complete journeys from entry point to outcome, including decision gates, error recovery paths, and re-entry after interruption. - Cross-Platform & Multi-Channel Design: Adapt flows for mobile, web, TV, and embedded contexts, and map journeys that span email, push, app, and support channels. - Visual Diagram Output: Produce flow diagrams as self-contained HTML, Figma frames via MCP, or pencil.dev documents. - Use Case: A product team asks how a new user should move from a marketing email through onboarding to their first published post. The Skill maps each screen, its copy direction, interaction specs, device variants, and success metrics, then renders the flow as an HTML diagram. ## Quick Start Ask the assistant to design the user journey for your onboarding flow, including screen-by-screen steps, decision points, and an HTML flow diagram.

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?▼

Map the journey from entry point to first success: define the user's goal, list each screen with its single primary message, add decision gates and error recovery paths, and specify progress indicators. The Skill structures this as a screen-by-screen flow with copy and interaction specs.

What is the best way to map a multi-channel user journey?▼

Identify every channel transition point — email to app, app to web, self-service to support — and document what state must persist across each handoff. Design each touchpoint for its channel's constraints rather than forcing one pattern everywhere.

Can this skill generate flow diagrams in Figma?▼

Yes. When you choose Figma output, the Skill loads the figma-use skill and calls the Figma MCP tool to create frames for flow nodes, connector lines for arrows, and rotated diamonds for decision gates. HTML and pencil.dev outputs are also supported.

How do I design flows differently for mobile versus web?▼

Mobile flows need thumb-friendly targets, single-column layouts, and tolerance for interruptions and unreliable networks. Web flows can use larger targets, keyboard shortcuts, and multi-step layouts that breathe across width. The Skill specifies device variants side-by-side with rationale.

What are the limitations of journey mapping without user research?▼

Flows designed from assumptions risk solving the wrong problem or smoothing over real behavioral variance. The Skill explicitly flags assumptions and hands off to research-oriented skills when evidence about actual user behavior is missing.

How should a flow handle users who leave mid-process?▼

Design save-and-resume behavior: persist progress automatically, provide re-entry points via email or drafts, and show returning users a summary of previous choices. Define expiration policies for incomplete state so abandoned flows clean up gracefully.