← Previous13 / 19Next →

Fernand Domain authenticated

FernandThe fast, calm customer support platform for SaaS

Design with AI

Create a new design inspired by Fernand Domain authenticated, 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 665 words

# Design from Reference: Fernand Domain authenticated

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

## Reference

- **Product:** Fernand
- **Category:** Settings
- **Screenshot:** attached to this message (also available at https://media.saasframe.io/o/b45c8fde9ced75d252ea.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:** Dense but orderly domain-configuration dialog with pale technical surfaces, monospaced DNS values and a blue verification action.

### Page composition

- **Canvas:** 1440 × 910 screenshot px.
- **Structure:** Large centered white panel above dimmed settings navigation; title, two numbered setup sections, redirect mapping, three DNS cards and a pale footer action bar.

### Information hierarchy

- **Priority:** Numbered instructions separate email redirect from domain ownership. Column headers and red status labels make configuration requirements explicit.

### Typography

- **Family:** Neutral sans serif for instructions; monospace for addresses/DNS values; exact fonts unverified.
- **Scale:** Estimated screenshot title 24 px, section headings 16 px, body 15 px and technical values 12–13 px; uppercase table labels approximately 11 px with tracking.

### Colors & surfaces

- **Sampled palette:** White #FFFFFF; dimmed surround #ECEFF2/#E8ECEF; footer #F7FAFC; pale rules #DFE8F0.
- **Accents:** Bright blue Verify button and pale-red unconfigured status badges; muted navy headings and gray-blue body.

### Components

- **DNS cards:** Three outlined rounded rectangles with Type, Key and Value columns, status badge upper right and approximately 20 px padding.
- **Redirect mapping:** Two-column From/To area with thin horizontal divider.
- **Footer:** Blue Verify button alongside subdued outlined Skip and do later; panel has subtle shadow and approximately 4 px corners.

### Visual rhythm

- **Spacing:** Approximately 28–44 screenshot px between instruction sections; 16 px between DNS cards. Repeated columns support technical scanning.

### Responsive

- **Observed:** Desktop setup dialog only.
- **Adaptation:** Use horizontally scrollable or stacked labeled DNS values, preserve copyability and avoid truncating hostnames. Keep footer actions visible.

### Adaptation guidance

- **Preserve:** Numbered setup sequence, aligned technical values and per-record status feedback.
- **Replace:** Use generated DNS records for the actual domain; never reuse the screenshot's addresses, keys or values.

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