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: Filterable Data Table.
Required content and structure
Provide column priorities, sorting, compound filters, row selection and pagination.
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
Define the record fields, priority columns, sorting rules, filter combinations and selection scope. Include long values, missing values and more records than one page.
Layout and behavior
Keep active filters and selection counts visible above the table. Preserve essential row identity on small screens and provide a deliberate way to reach secondary columns.
Task-specific acceptance check
- Keep filters and selected rows consistent across pages.
- Filter after selecting records and move between pages.
- Confirm whether selection applies to visible rows or all matching rows, and never silently clear or broaden it.
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 Filterable Data Table. 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: Provide column priorities, sorting, compound filters, row selection and pagination. Use the following task-specific layout guidance when translating the image into editable elements: Keep active filters and selection counts visible above the table. Preserve essential row identity on small screens and provide a deliberate way to reach secondary columns.
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: Provide column priorities, sorting, compound filters, row selection and pagination. Keep filters and selected rows consistent across pages. 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 Filterable Data Table Design Prompt
Use this filterable data table design prompt to provide column priorities, sorting, compound filters, row selection and pagination.
The reference is an AI-generated concept. The instructions below describe what to build and test; the image does not demonstrate working behavior.
Define Selection Across Pages
A filterable table needs an explicit relationship between filters, pagination and selected rows.
Otherwise a user can act on records they no longer realize are selected. Keep active filters and selection counts visible above the table. Preserve essential row identity on small screens and provide a deliberate way to reach secondary columns.
From the Prompt
Keep active filters and selection counts visible above the table.
Make It Your Own
Expose active [FILTERS], sort direction and the selected count. Distinguish selecting the visible page from selecting all matching records; describe what happens when filters change.
Prepare the Filterable Data Table Content
The table toolbar combines search with category, status, price and supplier filters, then repeats active constraints as removable chips. Define their combined query behavior and clear/reset actions.
Define the record fields, priority columns, sorting rules, filter combinations and selection scope. Include long values, missing values and more records than one page.
From the Prompt
Provide column priorities, sorting, compound filters, row selection and pagination.
Make It Your Own
For [PROJECT], use [APPROVED_CONTENT] as the source for this filterable data table. Define the record fields, priority columns, sorting rules, filter combinations and selection scope. Include long values, missing values and more records than one page. Identify missing inputs before replacing them with demonstration content.
Test a Hidden Selection
Checkboxes remain visible beside the result rows and a selection count appears near pagination. Test whether selection persists across pages and communicate that scope before bulk actions.
Select rows, move to another page and change a filter. The selection summary must still explain the scope before any bulk action becomes available. Filter after selecting records and move between pages. Confirm whether selection applies to visible rows or all matching rows, and never silently clear or broaden it.
From the Prompt
Keep filters and selected rows consistent across pages.
Make It Your Own
Review the filterable data table against this requirement: Keep filters and selected rows consistent across pages. Filter after selecting records and move between pages. Confirm whether selection applies to visible rows or all matching rows, and never silently clear or broaden it. Preserve approved content and revise only the parts that fail this check.
Review Your Filterable Data Table Result
A convincing screen is not a working backend. Test validation, permissions, persistence and failure behavior separately before connecting real data.
- Filter after selecting records and move between pages. Confirm whether selection applies to visible rows or all matching rows, and never silently clear or broaden it.
Follow-Up Prompt
Use this after the first result. It narrows the revision to the most important part of this task.
Refine the current filterable data table. Filter after selecting records and move between pages. Confirm whether selection applies to visible rows or all matching rows, and never silently clear or broaden it. Preserve the approved content and visual direction; change only the parts needed to resolve these issues.
