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: Team Invitation Flow.
Required content and structure
Invite collaborators by email with role selection, pending invitations and resend states.
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 invite permissions, available roles, duplicate-email handling and pending or expired states. Use sample addresses instead of sending actual invitations.
Layout and behavior
Keep each address paired with its role and validation message. Let users review invitations before sending, and show which individual requests succeeded or need correction.
Task-specific acceptance check
- Handle duplicate addresses and permission limits without losing entered values.
- Enter duplicates and invalid addresses in the same batch.
- Preserve valid entries after errors and avoid presenting resend or revoke actions to users who lack the required permission.
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 Team Invitation 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: Invite collaborators by email with role selection, pending invitations and resend states. Use the following task-specific layout guidance when translating the image into editable elements: Keep each address paired with its role and validation message. Let users review invitations before sending, and show which individual requests succeeded or need correction.
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: Invite collaborators by email with role selection, pending invitations and resend states. Handle duplicate addresses and permission limits without losing entered values. 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 Team Invitation Flow Design Prompt
Use this team invitation flow design prompt to invite collaborators by email with role selection, pending invitations and resend states.
The reference is an AI-generated concept. The instructions below describe what to build and test; the image does not demonstrate working behavior.
Track Each Invitation Separately
A team invitation flow needs to explain roles and delivery state for each address.
One invalid or duplicate address should not erase the rest of the entered list. Keep each address paired with its role and validation message. Let users review invitations before sending, and show which individual requests succeeded or need correction.
From the Prompt
Keep each address paired with its role and validation message.
Make It Your Own
Invite [EMAILS] with role selection, showing validation and permission limits per address. List pending invitations with resend and cancellation states while preserving valid entries.
Prepare the Team Invitation Flow Content
The form displays duplicate-email and capacity feedback near the affected rows; specify per-row validation and available-seat rules.
Define invite permissions, available roles, duplicate-email handling and pending or expired states. Use sample addresses instead of sending actual invitations.
From the Prompt
Invite collaborators by email with role selection, pending invitations and resend states.
Make It Your Own
For [PROJECT], use [APPROVED_CONTENT] as the source for this team invitation flow. Define invite permissions, available roles, duplicate-email handling and pending or expired states. Use sample addresses instead of sending actual invitations. Identify missing inputs before replacing them with demonstration content.
Include a Duplicate Address
Pending invitations are listed separately from new inputs; define resend, expiry and cancellation states.
Explain whether it is already a member or already invited without sending another invitation. Keep other entries and their selected roles intact. Enter duplicates and invalid addresses in the same batch. Preserve valid entries after errors and avoid presenting resend or revoke actions to users who lack the required permission.
From the Prompt
Handle duplicate addresses and permission limits without losing entered values.
Make It Your Own
Review the team invitation flow against this requirement: Handle duplicate addresses and permission limits without losing entered values. Enter duplicates and invalid addresses in the same batch. Preserve valid entries after errors and avoid presenting resend or revoke actions to users who lack the required permission. Preserve approved content and revise only the parts that fail this check.
Review Your Team Invitation Flow Result
A convincing screen is not a working backend. Test validation, permissions, persistence and failure behavior separately before connecting real data.
- Enter duplicates and invalid addresses in the same batch. Preserve valid entries after errors and avoid presenting resend or revoke actions to users who lack the required permission.
Follow-Up Prompt
Use this after the first result. It narrows the revision to the most important part of this task.
Refine the current team invitation flow. Enter duplicates and invalid addresses in the same batch. Preserve valid entries after errors and avoid presenting resend or revoke actions to users who lack the required permission. Preserve the approved content and visual direction; change only the parts needed to resolve these issues.
