Receber por email
← Voltar para o catálogo

ss-flow

Design user flows and navigation structure following proven UX patterns

555estrelas
Atualizado há 4 meses

Ver no GitHub ↗ Licença: MIT

Como adicionar

/plugin marketplace add bitjaru/styleseed

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/ss-flow/svg)](https://www.skillteca.com.br/skills/ss-flow)

Alerta por categoria

Receba novas skills de Design e Frontend toda segunda

1 email curto, só com as skills novas de Design e Frontend. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

UX Flow Designer

When NOT to use

  • For implementing a single page → use /ss-page after the flow is settled
  • For copy on each step → use /ss-copy after the structure is settled
  • For information architecture of an entire product — narrow scope to one flow first
  • For high-fidelity mockups — this produces a flow map, not pixel-perfect designs

Design a user flow: $0 Description: $ARGUMENTS

Instructions

  1. Read the design system reference:
  2. CLAUDE.md for component inventory
  3. DESIGN-LANGUAGE.md for layout patterns (sections 13-14, 19-20)
  4. components/patterns/ for available building blocks
  1. Apply these UX principles:

Information Architecture

  • Progressive Disclosure: Show only what's needed at each step. Hide complexity behind logical drill-downs.
  • Miller's Law: Chunk information into groups of 5-9 items maximum.
  • Hick's Law: Minimize choices per screen. Fewer options = faster decisions.

Navigation Patterns

  • Hub & Spoke: Dashboard → detail pages → back to dashboard (default for mobile apps)
  • Linear Flow: Step 1 → Step 2 → Step 3 (for forms, onboarding, checkout)
  • Tab Navigation: 3-5 top-level sections via BottomNav

Screen Flow Rules

  • Every flow must have a clear entry point and clear exit point
  • Maximum 3 taps to reach any key feature from the home screen
  • Back navigation must always be available (except root screens)
  • Error states must provide recovery paths (retry, go back, contact support)
  • Loading states must use skeleton screens (never spinners in cards)

Page Composition (from DESIGN-LANGUAGE.md)

  • Follow the Information Pyramid: Hero → KPI Grid → Details → Lists
  • Each screen should answer ONE primary question
  • Above the fold: the most important metric or action
  • Use the 4 section types: Full Card (A), Grid (B), Carousel (C), Hero (D)
  1. Output format:
  2. Flow diagram in ASCII showing screen connections
  3. Screen inventory listing each screen's purpose and key components
  4. Edge cases (empty states, errors, loading) for each screen
  5. Scaffolded pages using PageShell, TopBar, BottomNav patterns
  1. Generate the actual page files using /ss-page conventions.
Compartilhar X LinkedIn