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: Data Import Mapping.
Required content and structure
Preview imported columns, map fields, validate rows and review errors before import.
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 a sample file, destination schema, required fields, validation rules and duplicate handling. Include invalid rows and columns with similar names.
Layout and behavior
Separate preview, field mapping, validation and final import. Keep row counts visible so users know how many records would succeed, fail or be skipped.
Task-specific acceptance check
- Separate preview from final import and show how many rows would be skipped.
- Remap a required field, correct a bad row and cancel before import.
- Previewing data must not create records, and the final result should reconcile with the reviewed counts.
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 Data Import Mapping. 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: Preview imported columns, map fields, validate rows and review errors before import. Use the following task-specific layout guidance when translating the image into editable elements: Separate preview, field mapping, validation and final import. Keep row counts visible so users know how many records would succeed, fail or be skipped.
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: Preview imported columns, map fields, validate rows and review errors before import. Separate preview from final import and show how many rows would be skipped. 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 Data Import Mapping Design Prompt
Use this data import mapping design prompt to preview imported columns, map fields, validate rows and review errors before import.
The reference is an AI-generated concept. The instructions below describe what to build and test; the image does not demonstrate working behavior.
Show What the Import Will Do
An import mapping dashboard translates source columns into destination fields.
A sample preview and row-level errors help the user judge the mapping before committing data. Separate preview, field mapping, validation and final import. Keep row counts visible so users know how many records would succeed, fail or be skipped.
From the Prompt
Separate preview, field mapping, validation and final import.
Make It Your Own
Map [SOURCE_COLUMNS] to [DESTINATION_FIELDS], showing sample values and required-field errors. Summarize valid, invalid and skipped rows before the final Import action.
Prepare the Data Import Mapping Content
Mapping selectors appear above a sample data table. Supply source columns and destination-field types, and make the preview reflect the current mapping.
Supply a sample file, destination schema, required fields, validation rules and duplicate handling. Include invalid rows and columns with similar names.
From the Prompt
Preview imported columns, map fields, validate rows and review errors before import.
Make It Your Own
For [PROJECT], use [APPROVED_CONTENT] as the source for this data import mapping. Supply a sample file, destination schema, required fields, validation rules and duplicate handling. Include invalid rows and columns with similar names. Identify missing inputs before replacing them with demonstration content.
Check a Misleading Sample
The right rail separates valid rows, errors and skipped records, with counts repeated near Continue to Import. Check that these counts reconcile and that invalid rows cannot be silently accepted.
Include a date or number format that changes later in the file. Validation should expose the affected rows rather than approving the whole column from its first value. Remap a required field, correct a bad row and cancel before import. Previewing data must not create records, and the final result should reconcile with the reviewed counts.
From the Prompt
Separate preview from final import and show how many rows would be skipped.
Make It Your Own
Review the data import mapping against this requirement: Separate preview from final import and show how many rows would be skipped. Remap a required field, correct a bad row and cancel before import. Previewing data must not create records, and the final result should reconcile with the reviewed counts. Preserve approved content and revise only the parts that fail this check.
Review Your Data Import Mapping Result
A convincing screen is not a working backend. Test validation, permissions, persistence and failure behavior separately before connecting real data.
- Remap a required field, correct a bad row and cancel before import. Previewing data must not create records, and the final result should reconcile with the reviewed counts.
Follow-Up Prompt
Use this after the first result. It narrows the revision to the most important part of this task.
Refine the current data import mapping. Remap a required field, correct a bad row and cancel before import. Previewing data must not create records, and the final result should reconcile with the reviewed counts. Preserve the approved content and visual direction; change only the parts needed to resolve these issues.
