Use the Prompt
Add Your Brief
Add your context below. It will be included with the prompt when you copy or download.
Create an interactive frontend prototype using the existing project stack and explicitly labeled demo data for [PROJECT] and [AUDIENCE]. The task is: Media Upload Flow.
Required content and structure
Show file selection, format guidance, upload progress, errors and retry controls.
Use [APPROVED_CONTENT] as the source of names, dates, figures, claims and destinations. List missing inputs before substituting anything. If a demonstration is needed, label its content as fictional. Do not invent customer quotes, rankings, partner logos or product capabilities.
Design direction
Use [BRAND_RULES] and the design system already selected in the project. If no system is supplied, start with this direction: warm white, ink text and restrained mint selected states; generous spacing and simple controls. Keep type, spacing and color roles consistent. Prioritize the task over decorative elements and avoid a generic collection of unrelated cards.
Content preparation
Define file limits, supported formats, progress events, cancellation and retry rules. Include a mixed batch where some files succeed and others fail.
Layout and behavior
Show each file's state separately, with a batch summary that reflects actual progress. Keep successful files available while giving failed files a clear recovery action.
Task-specific acceptance check
- Handle partial failures and allow cancellation without hiding successful uploads.
- Cancel one upload, retry another and select an unsupported format.
- Do not erase successful uploads when a single file fails or invent progress while waiting for real events.
Implementation and review
Keep text editable. Use semantic structure, descriptive controls, visible keyboard focus and appropriate empty/error states. Check narrow and wide layouts. Respect reduced-motion preferences. Preserve any existing project framework and dependencies; do not silently replace the stack. Return the editable files and explain any incomplete behavior or unsupported inputs. Review this specific task before proposing extra features.
Reference attachment and reconstruction goal
Attach reference.webp from this prompt’s download bundle alongside this prompt in OpenDesign. Build an editable result with a similar composition and hierarchy; do not embed the whole reference image as the finished interface. Preserve approved project content and brand rules if they conflict with fictional sample labels. If the image is missing or unreadable, ask for it instead of claiming visual fidelity.
Reference composition and content
Use the attached reference.webp as the visual reference for Media Upload Flow. Before building, identify the major regions from top to bottom, their relative widths and heights, alignment, spacing, typography hierarchy, surface colors, borders, imagery and repeated components. Preserve those relationships rather than substituting a generic template. Required task content: Show file selection, format guidance, upload progress, errors and retry controls. Use the following task-specific layout guidance when translating the image into editable elements: Show each file's state separately, with a batch summary that reflects actual progress. Keep successful files available while giving failed files a clear recovery action.
Visual direction from the example brief
warm white, ink text and restrained mint selected states; generous spacing and simple controls.
Interaction specification
The reference is a static concept: the behavior below is a requirement to implement, not proof that the picture already works. Copy the customized prompt into your working project. Start with the core task: Show file selection, format guidance, upload progress, errors and retry controls. Handle partial failures and allow cancellation without hiding successful uploads. For each visible control, specify its trigger, affected state and feedback; implement local changes with consistent state across related views. Give search and filters real results, selection controls an explicit active state, and save actions visible pending/success/failure feedback where relevant. Do not add unrelated workflows. Use proper links for navigation, buttons for actions and accessible names for icon controls. Do not imply a backend operation succeeded when only a local demo changed.
Visual comparison and delivery
- Compare the result with the attached image at matching proportions. Review major region placement, relative image sizes, line breaks, spacing, typography hierarchy, contrast, active states and content density before polishing decorative details.
- Then test the narrow layout without squeezing desktop text into tiny labels.
- Keep logos, photos and icons as separate assets and all meaningful labels editable. List any unavailable fonts/assets and any intentional departures. Return the working files plus a concise account of implemented behavior and remaining integrations; do not promise a pixel-identical result from the prompt alone.
Download Prompt + Image
Includes the complete prompt and full-size reference image. Attach both in OpenDesign to guide the layout.
How to Write a Media Upload Flow Design Prompt
Use this media upload flow design prompt to show file selection, format guidance, upload progress, errors and retry controls.
The reference is an AI-generated concept. The instructions below describe what to build and test; the image does not demonstrate working behavior.
Track Each File Independently
A media upload flow needs to preserve successful files when another upload fails.
File-level status is more useful than a single progress bar for a mixed batch. Show each file's state separately, with a batch summary that reflects actual progress. Keep successful files available while giving failed files a clear recovery action.
From the Prompt
Show each file's state separately, with a batch summary that reflects actual progress.
Make It Your Own
Show selected [FILES], format guidance and per-file queued, uploading, complete or failed states. Allow cancellation and retry only the affected files.
Prepare the Media Upload Flow Content
The upload area sits beside supported formats and size limits. Validate the same constraints for chosen and dropped files, with clear rejection messages.
Define file limits, supported formats, progress events, cancellation and retry rules. Include a mixed batch where some files succeed and others fail.
From the Prompt
Show file selection, format guidance, upload progress, errors and retry controls.
Make It Your Own
For [PROJECT], use [APPROVED_CONTENT] as the source for this media upload flow. Define file limits, supported formats, progress events, cancellation and retry rules. Include a mixed batch where some files succeed and others fail. Identify missing inputs before replacing them with demonstration content.
Fail One File in a Batch
The queue shows completed, active and failed files separately. Test independent retry and cancellation so one failure does not discard successful uploads.
Completed files should remain available and failed files should retain their identity and recovery action. Retrying should not upload successful files again without a reason. Cancel one upload, retry another and select an unsupported format. Do not erase successful uploads when a single file fails or invent progress while waiting for real events.
From the Prompt
Handle partial failures and allow cancellation without hiding successful uploads.
Make It Your Own
Review the media upload flow against this requirement: Handle partial failures and allow cancellation without hiding successful uploads. Cancel one upload, retry another and select an unsupported format. Do not erase successful uploads when a single file fails or invent progress while waiting for real events. Preserve approved content and revise only the parts that fail this check.
Review Your Media Upload Flow Result
A convincing screen is not a working backend. Test validation, permissions, persistence and failure behavior separately before connecting real data.
- Cancel one upload, retry another and select an unsupported format. Do not erase successful uploads when a single file fails or invent progress while waiting for real events.
Follow-Up Prompt
Use this after the first result. It narrows the revision to the most important part of this task.
Refine the current media upload flow. Cancel one upload, retry another and select an unsupported format. Do not erase successful uploads when a single file fails or invent progress while waiting for real events. Preserve the approved content and visual direction; change only the parts needed to resolve these issues.
