ux-flow

Plan structured user journeys with StyleSeed UX patterns.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/anonymouswhite07/Portfolio-v1 --skill ux-flow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ux-flow
Source: https://github.com/anonymouswhite07/Portfolio-v1/tree/main/.agents/skills/ux-flow
Command: npx skills add https://github.com/anonymouswhite07/Portfolio-v1 --skill ux-flow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

StyleSeed UX patterns help teams translate complex product ideas into clean, navigable flows, ensuring consistent journeys before screens are built.

Core Features & Use Cases

  • Flow mapping: define entry points, exits, screen inventory, and navigation structure.
  • Pattern-guided planning: apply hub-and-spoke, progressive disclosure, and information pyramids to reduce cognitive load.
  • Use Case: plan onboarding, multi-step checkout, or account management flows with clear navigation paths.

Quick Start

Provide a model task or user goal and outline the main screens, entry points, and exits using the hub-and-spoke pattern.

Frequently Asked Questions about ux-flow

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

FAQPage Schema
How do I plan clear user journeys for multi-screen flows?

Plan user journeys by defining entry points, exits, and screen inventories using structured UX patterns. This approach reduces cognitive load and ensures consistent navigation paths across complex flows before any screens are built.

What is the best way to structure navigation for a complex product dashboard?

Structure product navigation using the hub-and-spoke pattern and information pyramids. This method organizes main screens and navigation paths to reduce cognitive load and guide users smoothly through account management or dashboard interfaces.

How do I map out onboarding and multi-step checkout flows effectively?

Map onboarding and checkout flows by applying progressive disclosure and hub-and-spoke patterns. This outlines clear entry points, screen inventories, and exits, ensuring users experience a structured and navigable journey.

When do I need explicit information architecture for UX design?

Explicit information architecture is needed when translating complex product ideas into navigable flows. It ensures clear state transitions and screen inventories are defined, satisfying structural requirements before screen development begins.

Can I use these UX patterns for account management and multi-screen flows?

Yes, these UX patterns apply directly to account management, onboarding, and multi-screen flows. They guide the planning of entry points, navigation structures, and exits to ensure consistent user journeys across various product scenarios.