Make the first step obvious

# Design reference: Squoosh — Image compression
Source: https://squoosh.app/
Swipefile reference: https://swipefile.design/ref/squoosh-editor/
Captured: 2026-09-04. This is a dated reference, not a claim about the current live product.
Capture scope: a page excerpt. Do not infer unseen sections or interactions.

## Objective
Adapt the interaction and layout patterns below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

## Reference notes
- surface: Image compression
- nav: A small install action stays apart from the upload task.
- layout: Centered drop target above a row of supplied example images.
- density: Keep the working area large; use compact labels for controls without shrinking the editing text.
- color: Pink upload area, blue lower field, and a pale checkerboard background.
- typography: Use a clear type hierarchy for the page title, primary content, and supporting labels.
- pattern: Separate importing an image from the detailed comparison and compression controls that follow.
- states: Initial upload screen; no user image has been opened.
- dont: Do not copy brand assets or sample records. Preserve keyboard access and design empty, loading, and error states for the actual task.

Useful for: Separate importing an image from the detailed comparison and compression controls that follow.

## Acceptance criteria
- Existing project conventions, design tokens, working functionality, and unrelated changes are preserved.
- Two or three reference principles clearly support the user's task; conflicts are resolved in favor of usability and the existing product.
- Reusable components and semantic HTML express the interface. Available licensed assets are used; important UI text is never rendered as a bitmap.
- Every visible control has a defined behavior. Loading, empty, error, success, disabled, and long-content states are specified where relevant. Demo data is clearly labeled.
- Navigation and content adapt at 375px, 768px, and 1440px without horizontal page overflow. Keyboard use, visible focus, labeled inputs, at least 44px touch targets, readable contrast, and reduced motion are supported.
- Verification distinguishes rendered behavior from proposals and identifies anything still requiring a backend or external service.

## Quality bar
Clear hierarchy, consistent spacing, restrained surfaces, and purposeful motion. Avoid decorative gradients, excessive cards, placeholder buttons, and invented metrics unless the project calls for them. Do not claim a feature is connected or tested without evidence.

# Design reference: Photopea — Start screen
Source: https://www.photopea.com/
Swipefile reference: https://swipefile.design/ref/photopea-editor/
Captured: 2026-09-04. This is a dated reference, not a claim about the current live product.
Capture scope: a page excerpt. Do not infer unseen sections or interactions.

## Objective
Adapt the interaction and layout patterns below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

## Reference notes
- surface: Editor start screen
- nav: Desktop-style menus remain in the top bar; storage locations form a separate sidebar.
- layout: A start screen with file locations on the left and new/open actions in the center.
- density: Keep the working area large; use compact labels for controls without shrinking the editing text.
- color: Charcoal surfaces with white labels and a teal product mark.
- typography: Use a clear type hierarchy for the page title, primary content, and supporting labels.
- pattern: Keep new-document and open-file actions prominent while grouping remote and local file locations in a separate sidebar.
- states: Initial start screen after opening the editor; no document is loaded.
- dont: Do not copy brand assets or sample records. Preserve keyboard access and design empty, loading, and error states for the actual task.

Useful for: Keep new-document and open-file actions prominent while grouping remote and local file locations in a separate sidebar.

## Acceptance criteria
- Existing project conventions, design tokens, working functionality, and unrelated changes are preserved.
- Two or three reference principles clearly support the user's task; conflicts are resolved in favor of usability and the existing product.
- Reusable components and semantic HTML express the interface. Available licensed assets are used; important UI text is never rendered as a bitmap.
- Every visible control has a defined behavior. Loading, empty, error, success, disabled, and long-content states are specified where relevant. Demo data is clearly labeled.
- Navigation and content adapt at 375px, 768px, and 1440px without horizontal page overflow. Keyboard use, visible focus, labeled inputs, at least 44px touch targets, readable contrast, and reduced motion are supported.
- Verification distinguishes rendered behavior from proposals and identifies anything still requiring a backend or external service.

## Quality bar
Clear hierarchy, consistent spacing, restrained surfaces, and purposeful motion. Avoid decorative gradients, excessive cards, placeholder buttons, and invented metrics unless the project calls for them. Do not claim a feature is connected or tested without evidence.

# Design reference: iLovePDF — Merge PDF
Source: https://www.ilovepdf.com/merge_pdf
Swipefile reference: https://swipefile.design/ref/ilovepdf-merge/
Captured: 2026-09-04. This is a dated reference, not a claim about the current live product.
Capture scope: a page excerpt. Do not infer unseen sections or interactions.

## Objective
Adapt the interaction and layout patterns below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

## Reference notes
- surface: Merge PDF
- nav: Other document tools stay in the header while import choices remain beside the main action.
- layout: A centered file-selection action sits below a short tool explanation.
- density: A deliberately sparse first step gives the main action or result priority.
- color: Very light background and a red primary file-selection button.
- typography: Use a clear type hierarchy for the page title, primary content, and supporting labels.
- pattern: Reduce the first step to choosing the documents before exposing detailed controls.
- states: Initial merge screen before choosing any documents.
- dont: Do not copy brand assets or sample records. Preserve keyboard access and design empty, loading, and error states for the actual task.

Useful for: Reduce the first step to choosing the documents before exposing detailed controls.

## Acceptance criteria
- Existing project conventions, design tokens, working functionality, and unrelated changes are preserved.
- Two or three reference principles clearly support the user's task; conflicts are resolved in favor of usability and the existing product.
- Reusable components and semantic HTML express the interface. Available licensed assets are used; important UI text is never rendered as a bitmap.
- Every visible control has a defined behavior. Loading, empty, error, success, disabled, and long-content states are specified where relevant. Demo data is clearly labeled.
- Navigation and content adapt at 375px, 768px, and 1440px without horizontal page overflow. Keyboard use, visible focus, labeled inputs, at least 44px touch targets, readable contrast, and reduced motion are supported.
- Verification distinguishes rendered behavior from proposals and identifies anything still requiring a backend or external service.

## Quality bar
Clear hierarchy, consistent spacing, restrained surfaces, and purposeful motion. Avoid decorative gradients, excessive cards, placeholder buttons, and invented metrics unless the project calls for them. Do not claim a feature is connected or tested without evidence.

# Design reference: Wormhole — Send files
Source: https://wormhole.app/
Swipefile reference: https://swipefile.design/ref/wormhole-send/
Captured: 2026-09-04. This is a dated reference, not a claim about the current live product.
Capture scope: a page excerpt. Do not infer unseen sections or interactions.

## Objective
Adapt the interaction and layout patterns below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

## Reference notes
- surface: Send files
- nav: Secondary product links sit above the main panel; supporting links sit below.
- layout: A drop zone and transfer explanation share one centered panel.
- density: A deliberately sparse first step gives the main action or result priority.
- color: Purple photographic background, dark translucent panel, and pale action button.
- typography: Use a clear type hierarchy for the page title, primary content, and supporting labels.
- pattern: Make the upload action and transfer expectations visible before selecting files.
- states: Initial file-sharing screen; no transfer has been created.
- dont: Do not copy brand assets or sample records. Preserve keyboard access and design empty, loading, and error states for the actual task.

Useful for: Make the upload action and transfer expectations visible before selecting files.

## Acceptance criteria
- Existing project conventions, design tokens, working functionality, and unrelated changes are preserved.
- Two or three reference principles clearly support the user's task; conflicts are resolved in favor of usability and the existing product.
- Reusable components and semantic HTML express the interface. Available licensed assets are used; important UI text is never rendered as a bitmap.
- Every visible control has a defined behavior. Loading, empty, error, success, disabled, and long-content states are specified where relevant. Demo data is clearly labeled.
- Navigation and content adapt at 375px, 768px, and 1440px without horizontal page overflow. Keyboard use, visible focus, labeled inputs, at least 44px touch targets, readable contrast, and reduced motion are supported.
- Verification distinguishes rendered behavior from proposals and identifies anything still requiring a backend or external service.

## Quality bar
Clear hierarchy, consistent spacing, restrained surfaces, and purposeful motion. Avoid decorative gradients, excessive cards, placeholder buttons, and invented metrics unless the project calls for them. Do not claim a feature is connected or tested without evidence.