← Previous49 / 50Next →

Logbook Login

LogbookMeet Logbook. Beat deadlines.

Design with AI

Create a new design inspired by Logbook Login, 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 546 words

# Design from Reference: Logbook Login

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

## Reference

- **Product:** Logbook
- **Category:** Login
- **Screenshot:** attached to this message (also available at https://media.saasframe.io/o/3e5cf298e96fa4ab4011.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:** Compact login on a white dotted-grid background.

### Page composition

- **Canvas:** 1440 × 821 screenshot px. Small centered logo and narrow control stack; password recovery sits separately near bottom and help at bottom right.

### Information hierarchy

- **Priority:** Google sign-in precedes divider, email/password, blue Login, and outlined Create account.

### Typography

- **Scale:** Approximate screenshot control text 14 px semibold; no large heading is visible. Sans serif family/CSS scale unverified.

### Colors & surfaces

- **Palette:** Sampled sRGB #FFFFFF, field #F3F1F1/#F4F2F2, and primary blue #3B65F9. Faint gray dots fade around the form.

### Components

- **Details:** Roughly 256 screenshot px stack width, 40 px controls, pill actions, rounded pale inputs, and outlined recovery button.

### Visual rhythm

- **Spacing:** Tight 8–10 px control gaps contrast with broad outer white space and distant recovery action.

### Responsive

- **Adaptation:** Mobile is not shown. Keep controls within side margins and move recovery into comfortable reach.

### Adaptation guidance

- **Transfer:** Preserve compact provider/manual login hierarchy and subtle background pattern. Use actual authentication options.

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