# Cycle 01 — create flow

Built-in imagegen used the actual 1440 × 1000 desktop and 390 × 844 mobile screenshots.
The original mobile page measured 447 px wide at a 390 px viewport. All step labels had
computed font-size 0 px. The generated concept is a visual proposal, not validation.

## Adopt

- Group the holdings and wallet state into a bordered panel with a useful sample-data entry.
- Wrap mobile header controls into two intentional rows; keep Positions visible.
- Show a readable current-step label on mobile, with a compact progress rail.
- Increase supporting-text contrast, control sizes and keyboard-focus visibility.
- Use the desktop width for a review card plus a distinct next-action panel; stack them on mobile.
- Keep exact values readable and let technical details expand on request.

## Adapt or reject

- Keep token addresses visible. The generated concept's symbols/logos alone cannot identify an asset.
- Keep direct Positions access instead of introducing the proposed hamburger menu for a tiny navigation set.
- Do not show generated USD values as real data. Samples stay explicitly labelled and isolated from wallets.
- Avoid repeating Connect and Explore buttons in several places.
- Preserve the release deposit hold; a polished proposal cannot grant admission.
- Use real HTML/CSS, not the generated raster as a functional UI.

## Validation targets

No page-level horizontal overflow at 390 px and 320 px; readable step names; 44 px primary
touch controls; keyboard focus visible; review values/disabled actions preserved; demo uses no wallet or RPC.