← Previous6 / 25Next →

Superlist Integration Connected

SuperlistHome to all your lists

Design with AI

Create a new design inspired by Superlist Integration Connected, 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,211 words

# Design from Reference: Superlist Integration Connected

Create an original, high-fidelity visual design inspired by the reference. Prioritize composition, typography, colors, spacing, and component styling over technical implementation.

## Reference

- **Product:** Superlist
- **Category:** Integrations
- **Screenshot:** attached to this message (also available at https://media.saasframe.io/v/524135b631a8359ba5fa-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:** A soft lavender productivity-app settings screen uses layered rounded panels, dark purple text and restrained colorful service icons.
- **Capture scale:** The screenshot is 2880 × 1630 image pixels. Approximate CSS dimensions assume a 1440 × 815 viewport at 2× density; the scale is unverified.
- **Tone:** Pale fills, small pill tabs and compact controls create a calm, friendly configuration environment.

### Page composition

- **Navigation rail:** A roughly 260px CSS-wide left sidebar lists main destinations, recent/list labels and grouped personal/work lists, with a small avatar near the bottom.
- **Settings panel:** A central rounded pane around 630px wide contains the large title, four tabs and a vertically scrolling integration list.
- **Detail panel:** A roughly 530px-wide right pane shows the selected Gmail integration, connected-account state and configuration options.
- **Viewport boundary:** Lower integration entries and a task-summarization section are partially cropped at the bottom; their full content is not visible.

### Information hierarchy

- **Settings context:** The large Settings title and selected Integrations pill establish the current section.
- **List selection:** The Gmail row has a pale selected background and a narrow warm-colored right border; connected status appears in green.
- **Detail status:** A Gmail icon, title and small connected-account count sit above explanatory text and a connected-account card.
- **Configuration:** A bold account-settings heading leads to a rounded panel containing three task-creation rules.
- **Visible toggles:** The starred-email rule is on in green; the important-email and label-based rules are off in muted purple-gray.

### Typography

- **Family:** A rounded interface sans-serif is visible; exact font identity is unverified.
- **Main title:** Approximately 40px CSS, bold, with around 48px line-height.
- **Section headings:** Approximately 26–28px semibold for Integrations and Gmail; detail subheadings around 20px.
- **List roles:** Integration names are around 16px semibold; descriptions and status lines around 14px with 20px line-height.
- **Controls:** Pill tabs and explanatory text are approximately 14–16px; small Pro labels use compact text around 12px.
- **Tracking:** Display and heading text is slightly tight; body copy uses normal tracking.

### Colors & surfaces

- **Main pane:** Sampled #FAFAFC forms the near-white settings and detail surfaces.
- **Layered lavender:** Sampled #EEEEF5, #E9E9F1 and #E7E6F1 form the outer frame, selected row and rounded internal cards.
- **Primary text:** Sampled #26253D supplies the deep purple-gray heading and label color.
- **Secondary text:** Sampled #72718C supplies muted descriptions and inactive controls.
- **Blue accent:** Sampled #1D87FC appears in the Google connection action and related link styling.
- **Status accents:** Green identifies connected accounts and the enabled toggle; small warm red icons and selection markers add navigation emphasis.

### Components

- **Settings tabs:** Four compact rounded pills use thin pale borders; the selected Integrations pill has a filled lavender background.
- **Integration rows:** Each row combines a roughly 40px circular service-icon backing, bold name, descriptive/status line and optional small Pro badge.
- **Detail header:** A pale block contains a close-circle control, service identity, connected count and a blue Google connection pill aligned upper right.
- **Account card:** A wide pale rounded rectangle includes a colored avatar, account identifier and circular disconnect icon. Personal account text is not needed to reproduce the design.
- **Rule panel:** A large rounded pale card contains a semibold introductory label and three icon/text/switch rows.
- **Toggles:** Small pill switches place a white thumb to the right when enabled and left when disabled.
- **Panel geometry:** Main panes use roughly 12–14px radii; internal account and rule cards use larger radii around 20–24px.

### Visual rhythm

- **Panel gutters:** Narrow lavender gutters around 10px separate sidebar, settings and detail panes.
- **Main padding:** The central title and text are inset roughly 52px; the detail content uses similar left/right padding.
- **List cadence:** Integration rows repeat at roughly 72px vertical intervals, with icons aligned to a common column.
- **Section spacing:** Around 32–40px separates explanatory text, account details and settings groups.
- **Density:** The navigation rail is compact, while the detail pane leaves more space between task-oriented groups.

### Responsive

- **Evidence limit:** Only the desktop split-pane state is observed; scrolling, mobile transitions and connection flows are unverified.
- **Pane recommendation:** Show the integration list and selected details as separate navigable views on narrow screens.
- **Navigation recommendation:** Collapse list navigation into a drawer while preserving the current selection.
- **Control recommendation:** Allow rule labels to wrap and keep toggle touch targets generous; avoid truncating account controls.
- **Header recommendation:** Reflow the connection action below the service heading if the right pane narrows.

### Adaptation guidance

- **State clarity:** Preserve distinct selected-row, connected-account and enabled-switch treatments, each with text or semantic state beyond color.
- **Component system:** Reuse icon-backed integration rows, pill tabs and rounded settings groups with consistent spacing.
- **Privacy:** Use representative account data in mockups and accessible labels for disconnect and close icons.
- **Interaction:** Implement keyboard-accessible tabs and switches, announce connection status and confirm the intended effect of account-disconnection actions.
- **Scope:** Reproduce only the visible rule and list structure; the cropped lower sections do not establish their full settings.

## 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.