Turn a feature idea into a low-fidelity wireframe blueprint

See it in action

What this prompt produces with example details filled in:

## Assumptions / Clarifying questions
The brief is workable, so I'm proceeding with these assumptions:
- Users already save articles elsewhere in the app; this feature adds organizing saved items into lists.
- "Read Later" is the default list every saved item lands in.
- Lists are private in v1 — no sharing or collaboration.

## Screen & state inventory
1. Saved home — lists + recently saved (default, empty, loading)
2. List detail — articles inside one list (default, empty)
3. Add-to-list sheet — bottom sheet launched from a saved article (default, create-new inline)
4. Create/rename list — small modal

## Wireframes

Saved home (default):
```
┌─────────────────────────────┐
│ ‹ Back      Saved      ＋New │  top bar · +New = create list
├─────────────────────────────┤
│ [ Search your saved items ] │  search field
├─────────────────────────────┤
│  Lists                       │  section label
│  ┌────────┐ ┌────────┐       │
│  │📁 Read │ │📁 Work │       │  list cards → tap opens List detail
│  │  12    │ │  8     │       │  count = items in list
│  └────────┘ └────────┘       │
│  ┌────────┐ ┌────────┐       │
│  │＋ New  │ │📁 …    │       │
│  └────────┘ └────────┘       │
├─────────────────────────────┤
│  Recently saved              │
│  ▭  [Article title, 2 lines] │  saved row → tap opens article
│      Source · 6 min          │
│  ▭  [Article title, 1 line]  │
│      Source · 4 min          │
├─────────────────────────────┤
│   🏠        🔖(active)   👤  │  bottom nav
└─────────────────────────────┘
```

Add-to-list sheet:
```
┌─────────────────────────────┐
│            ▁▁▁▁              │  drag handle
│  Add to list                 │
│  "[Title of saved article]"  │  context: what's being filed
├─────────────────────────────┤
│  ☑ 📁 Read Later             │  default, pre-checked
│  ☐ 📁 Work                   │
│  ☐ 📁 Design                 │
│  ─────────────────────────   │
│  ＋ Create new list          │  expands an inline text field
├─────────────────────────────┤
│  [        Done        ]      │  primary, full-width
└─────────────────────────────┘
```

## Content hierarchy (Saved home)
1. Search — power users have long backlogs; finding beats browsing.
2. Lists grid — the organizing payoff, kept above the fold.
3. Recently saved — reassurance that the last save landed safely.
4. Bottom nav — persistent, lowest attention.

## Responsive reflow
iOS mobile, single column. List cards are a 2-up grid that never widens past two on phone. Primary actions (＋New, Done) sit in thumb reach — top-right and bottom. On very small devices the "Recently saved" preview trims to two rows; the rest lives inside a list.

## Key states
- Empty (no lists yet): Lists grid replaced by a single centered block — "[No lists yet]" + [＋ Create your first list]. Recently saved still shows if any items exist.
- Loading: list cards and rows render as gray skeleton blocks, same shapes, no text.
- Error (fetch failed): inline banner "[Couldn't load your saved items]" + [Retry]; keeps last cached list visible if available.

## Annotations
- [＋New] and the "＋ New" card are the same action, duplicated so creation is reachable whether the user thinks "add" from the header or from the grid.
- ☑ Read Later is pre-checked so a one-tap save always has a home; users file into a specific list only if they choose to.
- Save row count and reading time set expectations before the user commits a tap.

## User flow
Save an article → toast "Saved to Read Later · Move?" → tap Move → Add-to-list sheet → check a list or ＋ Create new list → Done → returns to the article, now filed.

## Handoff notes
- Reuses the existing article-row and bottom-nav components — no new primitives needed except the list card.
- Open question: cap on number of lists, or unlimited? Affects grid vs. scrolling list.
- Out of scope for v1: reordering lists, drag-to-file, and sharing — noted for a later pass.