1 / 20Next →

Mine Delete Account

MineData ownership

Design with AI

Create a new design inspired by Mine Delete Account, 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 730 words

# Design from Reference: Mine Delete Account

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

## Reference

- **Product:** Mine
- **Category:** Settings
- **Screenshot:** attached to this message (also available at https://media.saasframe.io/o/77613e56d985bd001f73.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:** A deletion-confirmation modal with a serif warning heading, plain explanatory copy and purple controls over a dark scrim.
- **Evidence scale:** Original 1440 × 789 pixels. Dimensions are image-pixel estimates; CSS scale is unverified.

### Page composition

- **Background:** Mine account/settings screen remains dimly visible.
- **Modal:** Approximately 620 × 452 px white panel centered near the upper-middle.
- **Order:** Close cross, centered warning heading, two-line consequence copy, keep-account link, checked acknowledgment block and delete button.

### Information hierarchy

- **Warning:** Large serif question leads.
- **Consequence:** Short centered text describes permanence.
- **Acknowledgment:** Checked square sits beside a two-line statement inside a pale rounded region.
- **Actions:** Keep-account text link appears above the acknowledgment; filled purple delete action below.

### Typography

- **Heading:** Unverified serif around 36 px medium, 44 px line height.
- **Body:** Sans-serif approximately 16 px regular, 24 px line height.
- **Actions:** Approximately 14–16 px medium.
- **Acknowledgment:** Around 14–16 px regular with comfortable wrapping.

### Colors & surfaces

- **Modal:** White #FFFFFF and pale #FBFBFB acknowledgment region.
- **Scrim:** Gray #54555D/#55565E are composited backdrop colors.
- **Accent:** Purple #666AF3 family for link, checked box and button.
- **Text:** Dark gray/black.

### Components

- **Shell:** Approximately 10 px radius and strong soft shadow.
- **Close:** Black unboxed cross at upper right.
- **Acknowledgment:** Roughly 580 × 78 px rounded pale block, purple checked square and wrapped copy.
- **Delete action:** Approximately 200 × 42 px purple pill with white label.
- **Keep link:** Centered purple text, unboxed.

### Visual rhythm

- **Header spacing:** Clear separation between heading and consequence.
- **Action spacing:** Large gaps distinguish keep link, acknowledgment and delete button.
- **Alignment:** Centered header/actions contrast with left-aligned acknowledgment.

### Responsive

- **Observed limit:** Desktop only.
- **Recommendation:** Use a fluid modal with gutters and allow acknowledgment text to wrap.
- **Accessibility recommendation:** Manage focus and expose checkbox state and action consequences clearly.

### Adaptation guidance

- **Retain:** State consequences, provide a recovery path and require explicit acknowledgment.
- **Implement:** Keep modal hierarchy clear and controls distinct.
- **Verify:** Confirm font, scale and enabled-state behavior separately; no account deletion was performed.

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