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: Invoice Builder.
Required content and structure
Create line items, quantities, tax rules, payment details and a readable document preview.
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
Provide line items, quantities, currency, tax rules, discounts, payment details and rounding behavior. Treat legal or tax text as supplied content, not a design decision.
Layout and behavior
Keep editing and document preview synchronized. Show subtotal, adjustments and final amount in an order that can be checked against the line items.
Task-specific acceptance check
- Reconcile totals and do not infer tax rules from the design.
- Change quantities, add a discount and test long item descriptions.
- Reconcile totals with the stated rules, and keep a draft invoice visibly distinct from an issued or paid one.
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 Invoice Builder. 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: Create line items, quantities, tax rules, payment details and a readable document preview. Use the following task-specific layout guidance when translating the image into editable elements: Keep editing and document preview synchronized. Show subtotal, adjustments and final amount in an order that can be checked against the line items.
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: Create line items, quantities, tax rules, payment details and a readable document preview. Reconcile totals and do not infer tax rules from the design. 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 an Invoice Builder Design Prompt
Use this invoice builder design prompt to create line items, quantities, tax rules, payment details and a readable document preview.
The reference is an AI-generated concept. The instructions below describe what to build and test; the image does not demonstrate working behavior.
Make Totals Traceable
An invoice builder connects editable line items to a document someone may send.
Each total needs a visible path back to quantity, unit price and the supplied adjustment rules. Keep editing and document preview synchronized. Show subtotal, adjustments and final amount in an order that can be checked against the line items.
From the Prompt
Keep editing and document preview synchronized.
Make It Your Own
Edit [LINE_ITEMS] alongside a matching invoice preview. Display subtotal, supplied tax treatment, discounts and total in [CURRENCY], and keep payment terms separate from paid status.
Prepare the Invoice Builder Content
The editor groups customer details, invoice dates and item rows above tax and payment settings. Supply actual quantities, rates and tax rules so totals can be calculated.
Provide line items, quantities, currency, tax rules, discounts, payment details and rounding behavior. Treat legal or tax text as supplied content, not a design decision.
From the Prompt
Create line items, quantities, tax rules, payment details and a readable document preview.
Make It Your Own
For [PROJECT], use [APPROVED_CONTENT] as the source for this invoice builder. Provide line items, quantities, currency, tax rules, discounts, payment details and rounding behavior. Treat legal or tax text as supplied content, not a design decision. Identify missing inputs before replacing them with demonstration content.
Reconcile After Editing
The right-hand preview repeats the entered information and emphasizes the total. Test synchronization, rounding and validation before sending or exporting the invoice.
Change a quantity and remove a line. Both preview and totals should update together; no tax rate should be inferred merely from an address or visual template. Change quantities, add a discount and test long item descriptions. Reconcile totals with the stated rules, and keep a draft invoice visibly distinct from an issued or paid one.
From the Prompt
Reconcile totals and do not infer tax rules from the design.
Make It Your Own
Review the invoice builder against this requirement: Reconcile totals and do not infer tax rules from the design. Change quantities, add a discount and test long item descriptions. Reconcile totals with the stated rules, and keep a draft invoice visibly distinct from an issued or paid one. Preserve approved content and revise only the parts that fail this check.
Review Your Invoice Builder Result
A convincing screen is not a working backend. Test validation, permissions, persistence and failure behavior separately before connecting real data.
- Change quantities, add a discount and test long item descriptions. Reconcile totals with the stated rules, and keep a draft invoice visibly distinct from an issued or paid one.
Follow-Up Prompt
Use this after the first result. It narrows the revision to the most important part of this task.
Refine the current invoice builder. Change quantities, add a discount and test long item descriptions. Reconcile totals with the stated rules, and keep a draft invoice visibly distinct from an issued or paid one. Preserve the approved content and visual direction; change only the parts needed to resolve these issues.
