Generate a new design based on this screen, using your own content.
Preview the prompt
# Design from Reference: Phantombuster Templates Library
Create an original, high-fidelity visual design inspired by the reference. Prioritize composition, typography, colors, spacing and component styling over technical implementation.
## Reference
- **Product:** Phantombuster
- **Category:** Templates Library
- **Screenshot:** https://media.saasframe.io/o/755b739cce862435e33e.webp
Analyze the screenshot first. If you can’t access it, ask me for it rather than guessing.
## 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.
Preserve essential messaging and factual accuracy. Adapt structure and copy length for visual balance; never invent product claims.
## Visual design
Use this context to reproduce the reference’s visual language: layout, typography, colors, spacing, borders, radii and distinctive elements. The screenshot takes priority if descriptions conflict.
### Overall aesthetic
- **Character:** Warm neutral use-case catalog with clean white cards and blue functional accents.
### Page composition
- **Canvas:** 1440 × 1685 screenshot pixels; CSS estimates are near screenshot scale, with capture scale unverified.
- **Structure:** White navigation, cream catalog with left search/filter rail, four category shortcuts, three-column popular-use-case grid and white footer.
### Information hierarchy
- **Priority:** Use cases heading and introduction precede goal shortcuts and five popular cards.
- **Cards:** Service icons, bold title, short description and category tag repeat consistently.
### Typography
- **Family:** Rounded geometric sans-serif; exact font is unverified.
- **Scale:** Estimated CSS main title 36px, card titles 20px bold, body/filter text 15–16px and tags 12px.
### Colors & surfaces
- **Sampled palette:** Warm background #F5F1F0; white #FFFFFF; blue #5274E8; dark text #1E1E1E.
- **Categories:** Blue, mint, red and yellow distinguish goal shortcut labels.
### Components
- **Cards:** Flat white rounded panels, approximately 12px radius and 24px padding; small pale-blue category badges.
- **Search:** Outlined field and adjacent blue pill action. Footer has five navigation groups.
### Visual rhythm
- **Spacing:** Approximately 16px card gutters, 48–64px between catalog groups and generous lower whitespace.
### Responsive
- **Guidance:** Mobile is not shown. Collapse filters and stack cards while keeping search prominent.
### Adaptation guidance
- **Transfer:** Preserve goal/category filtering and compact card metadata. Use supported target workflows and service marks.
## 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.
## 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.
Deliver a polished, cohesive design with precise alignment, hierarchy and spacing. Produce the requested visual artifact, not just a description. If unsupported, explain the limitation.
SaaSFrame
