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: Bulk Edit Review Flow.
Required content and structure
Show selected records, proposed changes, exceptions and a final change summary.
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
Define selectable records, editable fields, permission constraints and the rules for exceptions. Supply sample records that include both eligible and ineligible items.
Layout and behavior
Keep the selected count visible and show a before-and-after summary before applying changes. Explain whether exceptions are skipped or prevent the entire operation.
Task-specific acceptance check
- Make the affected count explicit and offer a safe cancel path.
- Test selection across pages, a record that becomes unavailable and partial failure.
- The confirmation must name the affected scope, and cancel must leave records unchanged.
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 Bulk Edit Review 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 selected records, proposed changes, exceptions and a final change summary. Use the following task-specific layout guidance when translating the image into editable elements: Keep the selected count visible and show a before-and-after summary before applying changes. Explain whether exceptions are skipped or prevent the entire operation.
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 selected records, proposed changes, exceptions and a final change summary. Make the affected count explicit and offer a safe cancel path. 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 Bulk Edit Review Flow Design Prompt
Use this bulk edit review flow design prompt to show selected records, proposed changes, exceptions and a final change summary.
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 Change Set Inspectable
A bulk edit review is a comparison between existing and proposed values.
Put the affected records and exceptions ahead of the confirmation action so the user can catch an overly broad selection. Keep the selected count visible and show a before-and-after summary before applying changes. Explain whether exceptions are skipped or prevent the entire operation.
From the Prompt
Keep the selected count visible and show a before-and-after summary before applying changes.
Make It Your Own
Show [SELECTED_COUNT] records, old and proposed [FIELD] values, and a separate list of [EXCEPTIONS]. Require review of the final affected count before applying changes.
Prepare the Bulk Edit Review Flow Content
The selected-record table is followed by a separate proposed-changes strip. Supply old and new values so users can review the batch before applying it.
Define selectable records, editable fields, permission constraints and the rules for exceptions. Supply sample records that include both eligible and ineligible items.
From the Prompt
Show selected records, proposed changes, exceptions and a final change summary.
Make It Your Own
For [PROJECT], use [APPROVED_CONTENT] as the source for this bulk edit review flow. Define selectable records, editable fields, permission constraints and the rules for exceptions. Supply sample records that include both eligible and ineligible items. Identify missing inputs before replacing them with demonstration content.
Check Partial Eligibility
An exceptions table is separated from the apply action and summary. Check that excluded records remain unchanged and that the confirmed count matches the valid selection.
Include a record that cannot accept the change. Explain whether it will be skipped or block the operation, and update the affected count accordingly. Test selection across pages, a record that becomes unavailable and partial failure. The confirmation must name the affected scope, and cancel must leave records unchanged.
From the Prompt
Make the affected count explicit and offer a safe cancel path.
Make It Your Own
Review the bulk edit review flow against this requirement: Make the affected count explicit and offer a safe cancel path. Test selection across pages, a record that becomes unavailable and partial failure. The confirmation must name the affected scope, and cancel must leave records unchanged. Preserve approved content and revise only the parts that fail this check.
Review Your Bulk Edit Review Flow Result
A convincing screen is not a working backend. Test validation, permissions, persistence and failure behavior separately before connecting real data.
- Test selection across pages, a record that becomes unavailable and partial failure. The confirmation must name the affected scope, and cancel must leave records unchanged.
Follow-Up Prompt
Use this after the first result. It narrows the revision to the most important part of this task.
Refine the current bulk edit review flow. Test selection across pages, a record that becomes unavailable and partial failure. The confirmation must name the affected scope, and cancel must leave records unchanged. Preserve the approved content and visual direction; change only the parts needed to resolve these issues.
