Prompt 715 words Copy
# Design from Reference: Privy Blog
Create an original, high-fidelity visual design inspired by the reference. Prioritize composition, typography, colors, spacing, and component styling over technical implementation.
## Reference
- **Product:** Privy
- **Category:** Blog Feed
- **Screenshot:** attached to this message (also available at https://media.saasframe.io/v/ce1a41b9e3703b665911-1600.webp)
- **Source:** https://www.privy.io/blog
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
## Privy — shared visual language
- **Theme**: crisp light fintech site with soft lilac-to-violet gradient imagery, alternating with near-black (#010110 / #111117) sections for performance and security. A small "privy | a stripe company" lockup in the top bar.
- **Typography**: geometric grotesk display faces at weight 400: FFF Acid Grotesk for product pages (H1 58px/64px, -1.74px; H2 42px/48px, -1.26px) and ABC Favorit for campaign pages (H1 78px/78px, -4.68px; H2 56px/58px). Inter for UI and body (14–20px), small uppercase eyebrows in Inter 12px w600 with 1.2px tracking, #70707D.
- **Colors**: near-black #010110 text and primary buttons, white and #F8F9FC surfaces, grey #70707D secondary text; lilac/periwinkle gradients (#C4D4F6, violet, pink) inside product shots; coral as the brand accent in logo usage; customer cards in each customer's colour.
- **Components**: pill buttons 36px with 100px radius (black "Get started", outlined "Talk to sales"); product mockups (wallet balances, treasury dashboards, approvals) floating on gradient panels; metric rows ("200M+", "$25B+", "99.99%"); case-study cards with "Challenge / Solution"; FAQ lists; a five-column footer signed "Technical decisions are moral decisions."
- **Layout**: centred 1200px content; heroes either split (copy left, gradient visual right) or centred over a gradient product shot; feature rows alternate image and copy.
- **Tone**: calm and confident, infrastructure language ("Build products that hold, move, and grow digital assets").
### Overall aesthetic
- **Style:** light blog with templated violet covers and shelf rows.
### Page composition
- **Header:** H1, tabs, featured split.
- **Body:** shelves (Latest, Changelog, Case studies, Product and Engineering), list archive, load more, footer.
### Typography
- **H1:** FFF Acid Grotesk 78px/78px, -1.56px. **Shelf titles:** Inter 22px w600. **Card titles:** 13–15px w500; meta 12px #646464.
### Colors & surfaces
- **Covers:** violet, lilac and pink gradients with white logos; cards 10–12px radius.
### Components
- **Shelf:** title, arrows, "View all", three cards.
- **Changelog card:** date pill, title, short text on a dotted timeline.
### Responsive
- **Mobile:** shelves scroll horizontally; archive rows wrap.
### Adaptation guidance
- **Lesson:** co-branded covers (your logo + partner's) make case studies recognisable at a glance.
## 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.
SaaSFrame
