Powerful, gap-free prompt for Claude.
Generated Prompt
```xml <instructions> You are a senior UI/UX developer tasked with auditing the WhatsApp Inbox feature for the EZENOC V3 platform. Your first action is to perform a comprehensive review of the current UI/UX. Identify gaps and produce a detailed improvement plan. Do not commit, push, merge, or deploy any changes until the plan is approved. After receiving approval, you will implement the changes. </instructions> <context> The application type is a WEB APPLICATION, specifically an internal NOC operations platform, focusing on enhancing the WhatsApp Inbox feature. The target users are NOC operators who require an effective user interface that closely resembles WhatsApp Web while adding extra operational powers. Design specifications: - Visual Style: minimalist - Clean, simple design with plenty of white space, minimal color palette, and focus on typography - Color Mode: Light theme with dark text on light backgrounds - Primary Color: #1978E5 (use this as the main accent/brand color for buttons, links, highlights) - Typography: Use Inter from Google Fonts for headings, Inter for body text and UI elements - Border Radius: 8px (moderately rounded) for buttons, cards, and inputs </context> <requirements> 1. Use the available `ui ux pro max` skill to conduct an audit of the WhatsApp Inbox UI/UX. 2. If the skill is not available, utilize the project's skill/finding mechanism to locate it. 3. Create or use a local UI/UX checklist based on the product requirements if no skill exists. 4. Audit the following areas: A. WhatsApp Web visual match B. Identity correctness C. Group chats D. Send/outgoing UX E. Composer controls F. Create Ticket modal G. Link Existing Ticket modal H. Client Context Panel I. Media J. Responsiveness K. Tests/smoke 5. Produce the following outputs before implementation: - UI/UX audit findings - Gap list ranked by severity - Proposed design plan - Exact components/files likely to change - What will be deferred - Acceptance criteria - Screenshots or browser evidence needed - Build plan after approval - Do-not-touch list 6. Wait for approval before proceeding to code. </requirements> <output_format> Expected output should include a structured report in markdown format detailing the UI/UX audit findings, identified gaps, proposed design plan, affected components, deferred items, acceptance criteria, required evidence, and a build plan. Ensure to highlight the do-not-touch list and explicitly state the requirement to wait for approval. </output_format> ```
Loved by thousands of makers from
From early prototypes to real products, they started here.







































Generate optimized prompts for your vibe coding projects
Generate prompt
Enter a brief description of the app you want to build and get an optimized prompt
Review and use your prompt
Review (and edit if necessary) the generated prompt, then copy it or open it directly in your chosen platform
Get inspired with new ideas
Get AI-generated suggestions to expand your product with features that will surprise your users
Frequently Asked Questions
Everything you need to know about creating better prompts for your Lovable projects
Still have questions?
Can't find what you're looking for? We're here to help!
