← Previous11 / 28Next →

Phantombuster Automation Setup

Phantombusterphantombuster

Design with AI

Create a new design inspired by Phantombuster Automation Setup, with your own content.

1Content

2Fidelity to the reference

Keeps its visual language, rearranges freely around your content.

3Your brand Optional

Use the reference style

Brand nameColorsFontsGuidelines

4Output

Prompt 1,071 words

# Design from Reference: Phantombuster Automation Setup

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:** Add & Edit
- **Screenshot:** attached to this message (also available at https://media.saasframe.io/v/44203454e7411eb342ad-1600.webp)

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

### Overall aesthetic
- **Character:** Warm off-white automation wizard with a white task card, blue actions and a compact instructional rail.
- **Visual emphasis:** A small platform logo, vertical stepper and cyan information banner establish context before the main URL field.
- **Scale:** The source image is 2880 × 1642 px. Dimensions below estimate a 1440 × 821 CSS layout at 2× scale; device ratio and zoom are unverified.

### Page composition
- **Header:** Platform icon and automation category sit left above a bold editable title. Ellipsis, Save & close and circular close controls align right.
- **Step rail:** Four stages stack on the left, followed by a setup-video thumbnail and information link.
- **Task card:** A broad white rounded panel occupies the right, containing Tweets to scrape heading, cyan explanation, URL field, accepted-source guidance and collapsed spreadsheet settings.
- **Bottom actions:** Outlined Back and filled blue Save buttons align to the card's lower right.
- **Support:** A blue rounded support control floats at the bottom right of the viewport.

### Information hierarchy
- **Progress:** Connect to Twitter is completed with a green check; Tweets to scrape is current and bold, while later stages are muted.
- **Task:** The current heading and information bar explain the required profile list.
- **Input:** One prominent labeled URL field is followed by three compact accepted-format examples.
- **Advanced settings:** Spreadsheet Settings has a chevron and remains collapsed.
- **State:** The URL field is empty; no automation execution, scraping result or saved completion is shown.

### Typography
- **Family:** Rounded neutral sans-serif; exact identity is unverified.
- **Titles:** Automation and task headings are approximately 24–26 CSS px, bold.
- **Form label:** Around 16 px bold; body/banner text approximately 16 px with comfortable leading.
- **Helper:** Accepted-source guidance is smaller, around 12 px.
- **Stepper/actions:** Approximately 15–16 px, with bold current stage and regular inactive labels.

### Colors & surfaces
- **Measured canvas:** ICC-aware sRGB sampling yields #F6F1EE for the warm background and #FFFFFF for the main card.
- **Measured information fill:** #E7FBFF is the pale cyan banner surface.
- **Measured action:** #4874EF appears in blue controls.
- **Measured foreground:** #1E1E1E is a dark text tone.
- **Depth:** A soft shadow and roughly 14–16 px corners lift the main card; controls have fine warm-gray outlines.

### Components
- **Automation identity:** Circular platform logo precedes a small category label and bold title with pencil icon.
- **Stepper:** Thin vertical connectors link a completed check, blue current dot and pale future dots.
- **Info banner:** A full-width cyan rounded rectangle contains a small information icon and one-line guidance.
- **URL input:** A wide approximately 850 × 50 CSS px outlined field has rounded corners and italic light placeholder text.
- **Help video:** A small branded poster includes a blue play button and illustrated mascot; no playback is demonstrated.
- **Actions:** Back/Save are pill-shaped, approximately 128 × 40 px, with directional arrows; Save & close in the header is outlined.
- **Advanced row:** Bold Spreadsheet Settings text and down chevron indicate a collapsed section.

### Visual rhythm
- **Card inset:** About 24 px padding aligns heading, banner, field and settings.
- **Field spacing:** The information banner sits well above the input group; helper lines form a tighter cluster below.
- **Rail balance:** Stepper and video occupy the left third while the card dominates the right.
- **Footer space:** A substantial gap before the bottom action row separates configuration from progression.

### Responsive
- **Evidence limit:** Only desktop is shown; recommendations follow.
- **Wizard:** Collapse the step rail to a compact progress view and move help below the form.
- **Input:** Keep a fluid full-width URL field with readable helper text.
- **Actions:** Wrap header controls and maintain large touchable Back/Save targets.
- **Support:** Prevent the floating support button from covering form actions.

### Adaptation guidance
- **Reusable pattern:** Pair explicit stage progress, one required source field and optional advanced settings with concise help.
- **State clarity:** Validate accepted URL types and distinguish saving configuration from running automation.
- **Accessibility:** Label the field and collapsed settings, announce progress state and provide video alternatives.
- **Content truth:** Describe the captured setup only; do not imply any external collection was performed.

## 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 imageAttach it to your message: assistants can’t open image links.

Build it in

Opening a tool copies the screenshot so you can paste it with your prompt.