← Previous3 / 17Next →

Assembly Connect Twitter

AssemblyMarketing calendar with superpowers

Design with AI

Create a new design inspired by Assembly Connect Twitter, 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 841 words

# Design from Reference: Assembly Connect Twitter

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

## Reference

- **Product:** Assembly
- **Category:** Integrations
- **Screenshot:** attached to this message (also available at https://media.saasframe.io/v/ad730390a7b0c621e365-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:** An extremely sparse integration settings page uses white space, black headings and one deep-green action.
- **Restraint:** A narrow navigation column and a short explanatory block leave most of the screen intentionally empty.

### Page composition

- **Capture scale:** The original is 2880 × 1642 pixels. A 2× capture is plausible but unverified; dimensions below estimate CSS pixels at half source resolution.
- **Sidebar:** An approximately 200-pixel-wide Settings column contains title/close, integration group, scheduling services and general settings.
- **Main:** A large Twitter Integration heading sits above a small bird icon/subheading, one-line explanation and connect button.
- **Support:** A green chat bubble with red count badge occupies the lower-right corner.

### Information hierarchy

- **Page title:** Large black text identifies the integration.
- **Explanation:** A smaller subheading and muted sentence clarify the connection purpose.
- **Action:** The only filled button stands immediately beneath the explanatory text.
- **Navigation:** Twitter is bold within the service list, showing the active page.

### Typography

- **Family:** A clean sans serif is visible; exact identity is unverified.
- **Title:** Approximately 36 pixels, medium/semibold.
- **Subheading:** Around 16 pixels, regular.
- **Descriptions/navigation:** Approximately 14 pixels; sidebar group labels are smaller uppercase gray text.
- **Button:** Compact uppercase text, approximately 12–14 pixels, with a monospaced appearance that is unverified.

### Colors & surfaces

- **Measured canvas:** White #FFFFFF dominates.
- **Measured action:** Deep green #01584C supplies the connect button.
- **Measured ink:** Black #000000 provides headings and navigation contrast.
- **Measured soft tones:** #FEFEFE, #FDFDFD and #FAFAFA occur in near-white details.
- **Accent relationships:** The blue service icon and mint button label add small brand/status accents.

### Components

- **Connect button:** Approximately 168 × 40 estimated CSS pixels, deep green with a small radius.
- **Sidebar divider:** A fine pale vertical line separates navigation from content.
- **Navigation icons:** Service-brand marks and small line icons precede compact text entries.
- **Close control:** A simple X aligns with the Settings title.
- **Chat control:** A circular green launcher carries a small red unread badge.

### Visual rhythm

- **Main inset:** Content begins around 80 pixels beyond the sidebar.
- **Grouping:** Title, explanatory block and action form a compact top-left cluster.
- **Whitespace:** The remaining workspace is blank, with no cards or secondary sections.

### Responsive

- **Observed state:** Only desktop is shown; compact behavior is unverified.
- **Recommended shell:** Collapse sidebar and preserve readable main padding.
- **Recommended copy:** Allow the long explanatory sentence to wrap above the button without fixed-height clipping.

### Adaptation guidance

- **Preserve sparsity:** Keep the page focused on one explanation and connection action.
- **State fidelity:** The screenshot shows an unconnected-looking action, not a successful connection.
- **Content scope:** Treat service terminology as captured interface content.
- **Accessibility:** Label navigation and chat controls and retain a visible focus state.

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