journey

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

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/danieliudi/trackforge-os --skill journey-danieliudi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: journey
Source: https://github.com/danieliudi/trackforge-os/tree/main/.cursor/skills/journey
Command: npx skills add https://github.com/danieliudi/trackforge-os --skill journey-danieliudi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Designing user experiences often happens screen-by-screen without a coherent view of the full journey, leading to friction, drop-offs, and flows that ignore device, context, and channel differences. This Skill structures the end-to-end design of any user flow so every screen, decision point, and recovery path is intentional. ## Core Features & Use Cases - End-to-End Flow Mapping: Design complete journeys from entry point to outcome, including decision branches, error recovery, and save-and-resume states. - Context & Device Variants: Adapt flows across mobile, web, TV, and embedded contexts, and across user types, entry points, and markets. - Visualization Output: Render the flow as a self-contained HTML diagram, a Figma file via MCP, or a pencil.dev document. - Use Case: A product designer asks how a new user should move from a marketing email through signup to first value; the Skill maps each screen, its copy direction, interaction specs, and the cross-channel handoffs, then outputs an HTML flow diagram. ## Quick Start Ask the assistant to design the onboarding flow for your app, including screen-by-screen steps, error states, and an HTML diagram of the journey.

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, CTA, and error states. This Skill structures that process and can output the flow as an HTML diagram, Figma file, or markdown spec.

How to map a user journey across multiple channels?

Identify channel transition points, what state must persist across them, and each channel's constraints such as SMS character limits or email's asynchronous nature. The Skill maps these handoffs explicitly so the journey feels continuous rather than fragmented.

What formats can the journey visualization be exported to?

Three formats are supported: a self-contained HTML file with inline CSS and dark mode, a Figma file created via MCP, or a pencil.dev document. HTML is the default when no preference is stated.

Does this skill handle mobile versus web flow differences?

Yes, it designs device-aware variants for mobile, web, TV, and embedded contexts. Mobile flows account for thumb zones and interruptions, while TV uses 10-foot UI conventions and remote control constraints.

When should I not use a journey mapping skill?

Avoid it for information architecture and taxonomy decisions, detailed wireframe layout, or backend system design. Those belong to complementary skills like organize, wireframe, and blueprint, which this Skill hands off to explicitly.