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: Subscription Billing Settings.
Required content and structure
Show plan, billing period, invoices, payment method and change-plan flow.
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: light neutral canvas, graphite text, cobalt accent and precise hairline separators; dense but legible hierarchy. Keep type, spacing and color roles consistent. Prioritize the task over decorative elements and avoid a generic collection of unrelated cards.
Content preparation
Supply the current plan, billing period, invoices, payment method display rules and plan-change calculations. Distinguish actual payments from estimates.
Layout and behavior
Show the current subscription before offering changes. Keep a plan-change review beside the projected charge, effective date and any prorating explanation provided by the business rules.
Task-specific acceptance check
- Separate estimated future charges from completed payments.
- Test a pending change, failed payment and annual billing.
- Estimated amounts must remain labeled, and a completed invoice should not be confused with a future renewal charge.
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 Subscription Billing Settings. 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 plan, billing period, invoices, payment method and change-plan flow. Use the following task-specific layout guidance when translating the image into editable elements: Show the current subscription before offering changes. Keep a plan-change review beside the projected charge, effective date and any prorating explanation provided by the business rules.
Visual direction from the example brief
light neutral canvas, graphite text, cobalt accent and precise hairline separators; dense but legible hierarchy.
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 plan, billing period, invoices, payment method and change-plan flow. Separate estimated future charges from completed payments. 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 Subscription Billing Settings Design Prompt
Use this subscription billing settings design prompt to show plan, billing period, invoices, payment method and change-plan flow.
The reference is an AI-generated concept. The instructions below describe what to build and test; the image does not demonstrate working behavior.
Separate the Next Bill from Past Payments
A subscription billing page needs to clarify current terms and the effect of a plan change.
Estimates of future charges should not look like completed invoices. Show the current subscription before offering changes. Keep a plan-change review beside the projected charge, effective date and any prorating explanation provided by the business rules.
From the Prompt
Show the current subscription before offering changes.
Make It Your Own
Show [PLAN], billing period, payment method and invoice history. Preview supplied change-plan costs separately from completed payments, including when the new terms take effect.
Prepare the Subscription Billing Settings Content
The billing view separates future charges from completed payments; use actual dates, currency and billing status.
Supply the current plan, billing period, invoices, payment method display rules and plan-change calculations. Distinguish actual payments from estimates.
From the Prompt
Show plan, billing period, invoices, payment method and change-plan flow.
Make It Your Own
For [PROJECT], use [APPROVED_CONTENT] as the source for this subscription billing settings. Supply the current plan, billing period, invoices, payment method display rules and plan-change calculations. Distinguish actual payments from estimates. Identify missing inputs before replacing them with demonstration content.
Review a Mid-Period Change
The plan chooser explains what happens next before review; specify proration and effective date before allowing a consequential change.
The user should see the applicable supplied billing assumptions before confirming. Do not invent proration or mark a future charge as already paid. Test a pending change, failed payment and annual billing. Estimated amounts must remain labeled, and a completed invoice should not be confused with a future renewal charge.
From the Prompt
Separate estimated future charges from completed payments.
Make It Your Own
Review the subscription billing settings against this requirement: Separate estimated future charges from completed payments. Test a pending change, failed payment and annual billing. Estimated amounts must remain labeled, and a completed invoice should not be confused with a future renewal charge. Preserve approved content and revise only the parts that fail this check.
Review Your Subscription Billing Settings Result
A convincing screen is not a working backend. Test validation, permissions, persistence and failure behavior separately before connecting real data.
- Test a pending change, failed payment and annual billing. Estimated amounts must remain labeled, and a completed invoice should not be confused with a future renewal charge.
Follow-Up Prompt
Use this after the first result. It narrows the revision to the most important part of this task.
Refine the current subscription billing settings. Test a pending change, failed payment and annual billing. Estimated amounts must remain labeled, and a completed invoice should not be confused with a future renewal charge. Preserve the approved content and visual direction; change only the parts needed to resolve these issues.
