← Previous8 / 33Next →

Folk Interactions List

FolkThe next generation contact manager

Design with AI

Create a new design inspired by Folk Interactions List, 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 570 words

# Design from Reference: Folk Interactions List

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

## Reference

- **Product:** Folk
- **Category:** Dashboard
- **Screenshot:** attached to this message (also available at https://media.saasframe.io/o/8a8302fbd793b7336493.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:** Sparse CRM contact-detail view with quiet gray metadata, narrow navigation and a broad interactions timeline.

### Page composition

- **Capture:** 1440 × 821 screenshot pixels; estimated CSS scale approximately 1×.
- **Structure:** Workspace/group sidebar, contact header and property column, right Interactions/Comments/Reminders tabs and one recent event.

### Information hierarchy

- **Priority:** Contact name/company establish identity; event title/author/date drive the timeline while empty properties invite completion.

### Typography

- **Family:** Sans serif; exact family unverified.
- **Estimated CSS sizes:** Contact heading 26px, body 14px, metadata 12px and uppercase property labels 11px.

### Colors & surfaces

- **Measured palette:** White #FFFFFF, selected/banner gray #EBEBEC, muted #6F7275, dark #181A1B/#323539 and borders #D6D7D7.

### Components

- **Elements:** Group selector, contact actions, property icons, favorite stars, sharing notice, New interaction button and author chip.
- **Estimated geometry:** Sidebar 240px, property column 360px, 32px controls, 6px radii and 24px pane gutters.

### Visual rhythm

- **Spacing:** Large gaps between property groups and a mostly empty timeline create a low-density workspace.

### Responsive

- **Suggested adaptation:** Collapse sidebar and show properties/timeline as stacked sections or tabs. Mobile behavior is unverified.

### Adaptation guidance

- **Transfer:** Preserve identity/property/activity separation and clear imported-interaction sharing 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.