Skip to content

mattgierhart/PRD-driven-context-engineering / .claude/skills/prd-v04-screen-flow-definition

prd-v04-screen-flow-definition

Verified

Connect user journeys to screens, defining the UI structure and navigation paths during PRD v0.4 User Journeys. Triggers on requests to define screens, design screen flows, map UI structure, plan navigation, or when user asks "what screens do we need?", "define screens", "screen flow", "UI structure", "information architecture", "navigation design", "wireframe planning". Consumes UJ- (User Journey Mapping), FEA- (Feature Value Planning), BR- (constraints). Outputs SCR- entries for screens and DES- entries for design system elements. Feeds v0.5 Red Team Review.

FileKindSize
SKILL.mdskill md11.1 KB
assets/des.mdmarkdown1.1 KB
assets/scr.mdmarkdown1.1 KB
references/design-brief-guidance.mdmarkdown4.2 KB
references/design-tool-examples.mdmarkdown10.0 KB
references/examples.mdmarkdown4.2 KB
references/navigation-patterns.mdmarkdown6.1 KB

references/navigation-patterns.md

View on GitHub
# Navigation Patterns Guide

## Pattern Overview

| Pattern | Structure | Best For |
|---------|-----------|----------|
| **Hub & Spoke** | Central hub, navigate out and back | Dashboard apps, CRMs |
| **Linear Flow** | Step 1 → Step 2 → Step 3 | Onboarding, Checkout |
| **Hierarchical** | Category → Subcategory → Item | Content apps, Documentation |
| **Flat** | All screens peer-level | Simple tools, Utilities |

---

## Hub & Spoke

```
          ┌─────────────┐
          │  Dashboard  │ ← Hub (always accessible)
          │   (Hub)     │
          └──────┬──────┘
       ┌─────────┼─────────┐
       ▼         ▼         ▼
┌──────────┐ ┌──────────┐ ┌──────────┐
│ Reports  │ │  Data    │ │ Settings │ ← Spokes
│ (Spoke)  │ │ (Spoke)  │ │ (Spoke)  │
└──────────┘ └──────────┘ └──────────┘
```

**When to use:**
- User needs quick access to multiple features
- No strict sequence required
- Dashboard provides orientation/status

**Implementation:**
- Persistent nav bar with hub access
- Each spoke has "back to dashboard" path
- Spokes can link to each other (not required)

---

## Linear Flow

```
┌──────────┐   ┌──────────┐   ┌──────────┐   ┌──────────┐
│  Step 1  │ → │  Step 2  │ → │  Step 3  │ → │ Complete │
│  (Info)  │   │ (Config) │   │ (Review) │   │ (Success)│
└──────────┘   └──────────┘   └──────────┘   └──────────┘
     ↑              ↑              ↑
     └──────────────┴──────────────┘
              (Back navigation)
```

**When to use:**
- Tasks with required sequence
- Onboarding flows
- Checkout/purchase flows
- Setup wizards

**Implementation:**
- Progress indicator showing current step
- Back button at each step
- "Skip" option only if step is optional
- Exit with confirmation ("Are you sure?")

---

## Hierarchical

```
┌─────────────────────────────────────────┐
│               Categories                │
│  [Docs]  [API]  [Guides]  [Support]     │
└────────────────────┬────────────────────┘
                     ▼
┌─────────────────────────────────────────┐
│          Docs → Subcategories           │
│  [Getting Started]  [Advanced]  [FAQ]   │
└────────────────────┬────────────────────┘
                     ▼
┌─────────────────────────────────────────┐
│     Getting Started → Articles          │
│  [Install]  [First Steps]  [Config]     │
└────────────────────┬────────────────────┘
                     ▼
┌─────────────────────────────────────────┐
│           Article Detail                │
│  [Content...]                           │
└─────────────────────────────────────────┘
```

**When to use:**
- Content-heavy applications
- Documentation sites
- E-commerce catalogs
- File managers

**Implementation:**
- Breadcrumb navigation
- Sidebar showing hierarchy
- Parent/child relationships clear
- Search as escape hatch

---

## Flat

```
┌──────────┐   ┌──────────┐   ┌──────────┐
│ Screen A │ ↔ │ Screen B │ ↔ │ Screen C │
└──────────┘   └──────────┘   └──────────┘
      ↑              ↑              ↑
      └──────────────┴──────────────┘
           (All screens peer-level)
```

**When to use:**
- Simple single-purpose tools
- Few screens (3-5)
- No natural hierarchy
- Quick utilities

**Implementation:**
- Tab bar or simple toggle
- All screens equally accessible
- Minimal navigation chrome

---

## Hybrid Patterns

Most products combine patterns:

```
Hub & Spoke (main app)
    │
    ├── Dashboard (hub)
    │       ├── Reports (spoke)
    │       ├── Settings (spoke)
    │       └── Data (spoke)
    │
    └── Linear Flow (onboarding)
            ├── Step 1: Account
            ├── Step 2: Connect Data
            └── Step 3: First Report
```

**Rule**: Use linear for sequences, hub & spoke for daily use.

---

## Navigation Elements

| Element | Purpose | When to Use |
|---------|---------|-------------|
| **Top Nav** | Global navigation | Hub access, user menu |
| **Sidebar** | Section navigation | Hierarchical, many options |
| **Tabs** | In-page navigation | Related content, same level |
| **Breadcrumbs** | Location + back navigation | Hierarchical depth |
| **Back Button** | Previous screen | Linear flows, detail views |
| **Bottom Nav** | Mobile primary actions | Mobile apps, 3-5 items |

---

## Anti-Patterns

| Anti-Pattern | Problem | Fix |
|--------------|---------|-----|
| **Hamburger everything** | Hides important nav | Use visible nav for key items |
| **No breadcrumbs in hierarchy** | User gets lost | Add breadcrumbs for depth >2 |
| **Linear without progress** | User doesn't know how long | Show step indicator |
| **Dead-end screens** | Can't navigate away | Always provide escape path |
| **Inconsistent nav location** | User relearns each page | Keep nav in same position |
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 322kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 198kUpdated Claude CodeCodexVerifiedInstall