← Previous9 / 19Next →

Fellow Sign Up Flow

FellowGreat Meetings Start Here

Design with AI

Create a new design inspired by Fellow Sign Up Flow, 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 598 words

# Design from Reference: Fellow Sign Up Flow

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

## Reference

- **Product:** Fellow
- **Category:** Account Setup
- **Screenshot:** attached to this message (also available at https://media.saasframe.io/o/22a4fb2cbcbc8a739012.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:** Friendly profile-setup step with personalized avatar, pale illustrated sidebar and mint progression controls.

### Page composition

- **Capture:** 1440 × 820 screenshot pixels; estimated CSS scale approximately 1×.
- **Structure:** Left 40% identity panel displays avatar/name and organization; right form contains title/photo action, name, management question, count stepper, update checkbox and Continue.

### Information hierarchy

- **Priority:** Full name establishes identity; management yes/no choice reveals a count control. Continue closes the sequence.

### Typography

- **Family:** Rounded sans serif; exact family unverified.
- **Estimated CSS sizes:** Heading 28px, field labels 18px, helper 16px and Continue 20px.

### Colors & surfaces

- **Measured palette:** White #FFFFFF, sidebar #F5F6F9 with #F5F6FA/#F6F6FA variations, avatar pink #E84991 and mint #68D6B7.

### Components

- **Elements:** Circular initial avatar, add-photo link, name input with clear icon, segmented No/Yes pill, minus/count/plus stepper and checked updates option.
- **Estimated geometry:** Form width 448px, 60px input, 48px pill controls, 4px button radius and 120px large avatar.

### Visual rhythm

- **Spacing:** Broad vertical gaps separate identity, role and communication preferences; organization identity anchors the left panel bottom.

### Responsive

- **Suggested adaptation:** Collapse illustrated panel into a compact identity summary and stack long questions above their controls. Mobile behavior is unverified.

### Adaptation guidance

- **Transfer:** Preserve clear personalization and conditional role details. Keep optional updates distinct from required account setup.

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