← Previous18 / 24Next →

Albato Setup Trigger

AlbatoNo-code automation

Design with AI

Create a new design inspired by Albato Setup Trigger, 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 644 words

# Design from Reference: Albato Setup Trigger

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

## Reference

- **Product:** Albato
- **Category:** Add & Edit
- **Screenshot:** attached to this message (also available at https://media.saasframe.io/v/fd93cf60202ec75a195c-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:** Clean automation-builder dialog over a dimmed workspace, with coral actions and restrained blue-gray helper text.

### Page composition

- **Canvas:** 2880 × 1772 screenshot pixels; CSS estimates assume approximately 2× capture scale.
- **Structure:** Centered white modal about 800px CSS wide, above a gray scrim. Builder navigation and bottom test/start bar remain visible behind it.

### Information hierarchy

- **Priority:** Set up a trigger heading and explanatory line, App selector, Event selector, then right-aligned Add a trigger action.
- **Support:** Each selector has a small contextual helper sentence; close/utility icons sit at the upper right.

### Typography

- **Family:** Neutral sans-serif; exact family is unverified.
- **Scale:** Estimated CSS heading 20px bold, body/labels 16px, helper text 12px and button 14px bold.

### Colors & surfaces

- **Sampled palette:** White #FFFFFF; dimmed background #B2B2B2 and #ACACAD; coral #FFA995; pale surface #FAFAFB; muted text #747E91; peripheral violet #5856DD.
- **Treatment:** Thin pale selector borders and dark heading preserve a calm form hierarchy.

### Components

- **Controls:** Two full-width rounded dropdowns with right chevrons, approximately 48px CSS high and 12px radii.
- **Modal:** Estimated 16px radius and 48px padding; coral action approximately 40px high with 8px radius.
- **Peripheral:** Vertical How it works tab and orange chat launcher remain visible outside the modal.

### Visual rhythm

- **Spacing:** About 24px separates selector groups; a larger 40px gap precedes the bottom action.

### Responsive

- **Guidance:** Mobile is not shown. Use a near-full-width modal, wrap helper copy and ensure dismissal and submission remain reachable.

### Adaptation guidance

- **Transfer:** Retain app/event dependency and contextual help. Replace service examples with target automation concepts.

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