← Previous2 / 38Next →

Conduktor Delete Account

ConduktorEnterprise Apache Kafka platform

Design with AI

Create a new design inspired by Conduktor 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 588 words

# Design from Reference: Conduktor 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:** Conduktor
- **Category:** Delete Account
- **Screenshot:** attached to this message (also available at https://media.saasframe.io/v/f6edd2c14d40498a6bc1-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:** Administrative deletion screen using restrained red warnings within a light settings shell.

### Page composition

- **Canvas:** 2880 × 1642 screenshot px. Top account bar and left settings navigation frame a narrow deletion form; success toast appears bottom right.

### Information hierarchy

- **Priority:** Back link and deletion heading lead to consequences, five-item affected-data list, required DELETE confirmation, and Cancel/Delete permanently actions.

### Typography

- **Scale:** Estimated CSS at assumed 2× capture: heading 20 px bold, body 14 px, labels 14 px semibold, toast helper 12 px. Sans serif family unverified.

### Colors & surfaces

- **Palette:** Sampled sRGB #FFFFFF, pale #F9F8F9, active lavender #F1F0FF, dark #1B1524, and warning tint #FFF8F7. Red marks destructive text; green marks success feedback.

### Components

- **Details:** Approximately 616 CSS px form width, pale rounded warning panel, 36 px input, neutral cancel button, thin red-outlined destructive action, and white shadowed success toast.

### Visual rhythm

- **Spacing:** About 24 px panel padding and 28–36 px group gaps; sidebar remains dense while form area is sparse.

### Responsive

- **Adaptation:** Mobile is not shown. Stack form sections and ensure warning list and confirmation remain readable before the action.

### Adaptation guidance

- **Transfer:** Preserve explicit consequences and typed confirmation. Match deletion scope and success/redirect feedback to actual behavior.

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