← Previous4 / 32Next →

Frame User Settings

FrameUnified suite of collaboration apps for teams

Design with AI

Create a new design inspired by Frame User Settings, 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 575 words

# Design from Reference: Frame User Settings

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

## Reference

- **Product:** Frame
- **Category:** Team Members
- **Screenshot:** attached to this message (also available at https://media.saasframe.io/v/963294c7516f3a5031ba-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

- **Style:** Minimal white company-user settings with dark actions and pale selected navigation.

### Page composition

- **Canvas:** 2880 × 1630 image px; CSS estimates assume unverified 2×.
- **Structure:** Thin global header, approximately 320px CSS sidebar, Users heading, search/filter/invite panel with one member row.

### Information hierarchy

- **Primary:** Users heading and Invite.
- **Navigation:** Users highlighted under Company.
- **Row:** Avatar/name, email, role, ellipsis.

### Typography

- **Family:** Neutral sans serif; exact identity unverified.
- **Title:** Approximately 24px CSS semibold.
- **Navigation:** 16px; table 14px.
- **Precision:** Estimated under 2×.

### Colors & surfaces

- **Canvas/panel:** #FFFFFF.
- **Selection:** #F0F4F7.
- **Text/action:** #0F1829.
- **Borders:** #EEEEEE.
- **Header action:** #171717.
- **Precision:** Flat samples.

### Components

- **Panel:** Thin outline, approximately 8px radius.
- **Toolbar:** Wide search, outlined All filter, dark Invite.
- **Avatar:** Small circle.
- **Sidebar:** Group icons and disabled gray items.

### Visual rhythm

- **Whitespace:** Large empty lower canvas.
- **Alignment:** Toolbar and row share panel insets; role/menu form columns.

### Responsive

- **Observed:** Desktop only.
- **Recommendation:** Collapse sidebar and stack member metadata if necessary.

### Adaptation guidance

- **Preserve:** Quiet directory hierarchy and obvious invite.
- **Privacy:** Replace personal details.
- **Behavior:** Filters/menus unverified.

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