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: Checkout Review Interface.
Required content and structure
Summarize items, quantities, delivery details, discounts and final cost before confirmation.
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
Supply item prices, quantities, delivery options, discounts, tax rules and payment conditions. Use the actual pricing rules rather than deriving them from a visual example.
Layout and behavior
Group editable order details above a clearly reconciled total. Keep recurring charges, currency and delivery conditions close to the final confirmation action.
Task-specific acceptance check
- Make currency, taxes and recurring charges explicit using supplied rules.
- Change quantity, remove an item and apply an invalid discount.
- The displayed total must update consistently, and estimated taxes or shipping should not appear final before their inputs are known.
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 Checkout Review Interface. 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: Summarize items, quantities, delivery details, discounts and final cost before confirmation. Use the following task-specific layout guidance when translating the image into editable elements: Group editable order details above a clearly reconciled total. Keep recurring charges, currency and delivery conditions close to the final confirmation 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: Summarize items, quantities, delivery details, discounts and final cost before confirmation. Make currency, taxes and recurring charges explicit using supplied rules. 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 Checkout Review Interface Design Prompt
Use this checkout review interface design prompt to summarize items, quantities, delivery details, discounts and final cost before confirmation.
The reference is an AI-generated concept. The instructions below describe what to build and test; the image does not demonstrate working behavior.
Make the Final Commitment Legible
A checkout review should let someone verify the actual charge and delivery before confirming.
Discounts, taxes and recurring terms must not be buried beneath the action. Group editable order details above a clearly reconciled total. Keep recurring charges, currency and delivery conditions close to the final confirmation action.
From the Prompt
Group editable order details above a clearly reconciled total.
Make It Your Own
Summarize items, quantities, delivery and the final total in [CURRENCY]. Apply only supplied tax and discount rules and show recurring charges beside the confirmation action.
Prepare the Checkout Review Interface Content
The order review keeps item images, variants, quantities and prices above the delivery block. Prepare these fields as one consistent order record.
Supply item prices, quantities, delivery options, discounts, tax rules and payment conditions. Use the actual pricing rules rather than deriving them from a visual example.
From the Prompt
Summarize items, quantities, delivery details, discounts and final cost before confirmation.
Make It Your Own
For [PROJECT], use [APPROVED_CONTENT] as the source for this checkout review interface. Supply item prices, quantities, delivery options, discounts, tax rules and payment conditions. Use the actual pricing rules rather than deriving them from a visual example. Identify missing inputs before replacing them with demonstration content.
Change a Quantity
The summary lists discount, shipping and tax separately above Confirm and Pay. Recalculate the total and test failed payment states; the screenshot does not demonstrate a transaction.
Recalculate the item subtotal and final total together. The review must still show any recurring commitment and avoid presenting an estimate as a completed charge. Change quantity, remove an item and apply an invalid discount. The displayed total must update consistently, and estimated taxes or shipping should not appear final before their inputs are known.
From the Prompt
Make currency, taxes and recurring charges explicit using supplied rules.
Make It Your Own
Review the checkout review interface against this requirement: Make currency, taxes and recurring charges explicit using supplied rules. Change quantity, remove an item and apply an invalid discount. The displayed total must update consistently, and estimated taxes or shipping should not appear final before their inputs are known. Preserve approved content and revise only the parts that fail this check.
Review Your Checkout Review Interface Result
A convincing screen is not a working backend. Test validation, permissions, persistence and failure behavior separately before connecting real data.
- Change quantity, remove an item and apply an invalid discount. The displayed total must update consistently, and estimated taxes or shipping should not appear final before their inputs are known.
Follow-Up Prompt
Use this after the first result. It narrows the revision to the most important part of this task.
Refine the current checkout review interface. Change quantity, remove an item and apply an invalid discount. The displayed total must update consistently, and estimated taxes or shipping should not appear final before their inputs are known. Preserve the approved content and visual direction; change only the parts needed to resolve these issues.
