Prompt 704 words Copy
# Design from Reference: Prelude Verify Overview Dashboard
Create an original, high-fidelity visual design inspired by the reference. Prioritize composition, typography, colors, spacing, and component styling over technical implementation.
## Reference
- **Product:** Prelude
- **Category:** Analytics
- **Screenshot:** attached to this message (also available at https://media.saasframe.io/v/f347505258e60ce57d32-1600.webp)
- **Source:** https://app.prelude.so/02j52yr8yd9pp9th0qn6xj5nvw/verify/phone
Analyze the attached screenshot first. If no image is attached, open the screenshot link; if neither is accessible, ask for it rather than guessing.
## Visual Design Context
### Brand
Prelude sells onboarding and trust infrastructure (verification, anti-fraud, auth, telco intel, messaging) to developers. Calm, technical, European.
### Website
Light grey and white sections with faint grids, black hero and closing bands. Each product has its own color, reused on chips, tabs and cards: Verify lime green, Watch purple, Auth yellow, Intel pink, Notify blue. Large semibold sans headlines with tight tracking, monospaced numbers and code samples, pill buttons (black primary, white outline secondary), compliance badges as small pills.
### Product (app.prelude.so)
Geist for text and Geist Mono for every number (KPIs, prices, codes). Background #F9F9FB, white panels with thin borders and 8 to 12px radii, text #1F1F24 and greys #605F6A / #84848F, near-black #1F1F24 primary buttons 32px tall. Top bar with org / app / product breadcrumbs and a Phone / Email switch, credit balance in red with a Top Up button, second bar of tabs (Overview, Verifications, Routes, Configure) and a ⌘K search. Settings use a grouped left menu. Status badges in pastel green #D2FFB5 and pink #FECBCC, blue #C1DCFF pills. Empty states use a small line icon, a title and one grey sentence.
### Tone
Short, factual copy in title case for labels; numbers and units always visible.
### Overall aesthetic
Dense but airy analytics page, light grey with white panels and monospaced numbers.
### Page composition
Collapsible checklist card, section title with emoji globe and filters, KPI tab row over a line chart with side legend, world map card, spending KPI row with its own chart.
### Typography
Geist 18px section titles, 12px KPI labels, Geist Mono 24px values.
### Colors & surfaces
White panels on #F9F9FB, green top border on the active KPI tab, purple and red legend dots, hatched grey map.
### Components
KPI tabs with comparison chips, dropdown filters, download icon button, map with legend.
### Responsive
KPI rows wrap to two columns; legend moves above the chart.
### Adaptation guidance
Use KPIs as chart tabs so one chart serves several metrics.
## Content
**Instructions:**
Generate realistic example content that fits the selected design reference.
Create appropriate headlines, descriptions, labels, buttons, and supporting copy based on the type of interface being designed.
If a product or business description is provided, use it to guide the content.
Otherwise, invent a plausible fictional SaaS product appropriate for the reference.
Keep the content concise, coherent, and visually balanced.
Do not present fictional statistics, customer names, or testimonials as verified facts.
## Design Direction
**Instructions:**
Use the reference screenshot as the main source of visual inspiration rather than a strict layout template.
Preserve its most distinctive design characteristics, such as typography, visual rhythm, color relationships, component treatments, and overall aesthetic.
Feel free to modify section arrangements, proportions, spacing, and individual components to better suit my content.
Introduce original design decisions where they improve usability, composition, or brand consistency.
The result should clearly reflect the reference's visual language without looking like a direct reproduction.
Follow the visual identity of the reference design.
Use its typography, color palette, component styling, and overall aesthetic as the primary design direction.
Do not introduce an unrelated visual identity.
## Output
**Instructions:**
Generate a high-fidelity visual mockup of the requested interface.
Present the design as a polished, realistic website or product UI screenshot.
Prioritize visual composition, typography, spacing, colors, alignment, and component details.
Use the available image-generation or visual-design capabilities.
Do not replace the mockup with source code, a written design specification, or a textual description.
If direct visual generation is unavailable, clearly explain the limitation.
## Constraints
- Use the actual screenshot as the primary visual reference.
- Preserve essential messaging and factual accuracy.
- Prioritize visual quality and consistency.
- Do not invent unsupported product claims.
- Adapt structure and copy length for visual balance. Reference image Attach it to your message: assistants can’t open image links. Open in ChatGPT ↗ Open in Claude ↗
Build it in Lovable ↗ v0 ↗ Figma Make ↗
Opening a tool copies the screenshot so you can paste it with your prompt.