UI/UX Design Prompts for Lovable AI

# Context
Build file upload with tagging: users drag files in, watch true per-file progress, and organize with tags that are managed values rather than free text. The unhappy paths are the feature; a demo-quality uploader breaks on the first flaky connection.

## Core Features (Priority Order)
1. Drag-drop zone with click-to-browse fallback and visible file-type and size rules
2. Per-file progress

# Context
Build an analytics dashboard for operators: headline metrics, one trend, one breakdown table, readable in five seconds and honest under failure. Every number answers 'compared to what, over when'.

## Core Features (Priority Order)
1. Four metric tiles, each stating its time window on the tile, with delta versus previous period
2. One time-series chart with range selector (7, 30, 90 days

# Context
Build a multi-step onboarding flow: a handful of screens that configure the product for a new user, with progress that survives interruption and questions that earn their place by visibly changing what comes next.

## Core Features (Priority Order)
1. Stepper UI: current position, step names, and back navigation that never loses answers
2. Progress persisted server-side per user; resume 

# Context
Build a poll tool: create a single-question poll, share a link, collect one vote per person, and show results that are honest about how many voted. Instant to answer, hard to stuff.

## Core Features (Priority Order)
1. Poll creation: question, 2-6 options, open or scheduled close
2. A public voting page: tap an option, see results immediately after
3. One-vote enforcement per visitor, s

# Context
Build a location directory: browse and filter places on a paired map and list, with every place and every city owning a server-rendered, indexable URL. The interactive layer enhances pages; it must never replace them.

## Core Features (Priority Order)
1. A detail page per location at a stable URL: name, address, attributes, description
2. City index pages listing that city's locations, 

# Context
Add sharing to content that is individually worth sharing: each shareable URL gets correct social metadata, mobile gets the native share sheet, desktop gets platform links and copy-link, and the whole thing weighs nearly nothing.

## Core Features (Priority Order)
1. Per-URL Open Graph and Twitter card metadata: title, description, image, rendered server-side
2. Native share sheet via th

# Context
Build an internal SEO metadata editor: every page listed with its title and description, edited inline against a realistic search-result preview, validated for the errors that actually cost clicks, exportable to where the site reads it.

## Core Features (Priority Order)
1. A page list: URL, current title, current description, status flags
2. Inline editing with a live SERP-style preview

# Context
Build the site navigation shell: a responsive navbar that collapses to a menu on small screens, communicates location, and behaves perfectly for keyboard and screen-reader users. Every page inherits this; build it like it is load-bearing, because it is.

## Core Features (Priority Order)
1. Desktop bar: logo home link, five or fewer items, one primary action visually distinct
2. Mobile c

# Context
Build the site's error surfaces: a 404 that recovers the visit, a generic error boundary that protects user work, and an offline state. These pages meet users at the worst moment; their quality is disproportionately remembered.

## Core Features (Priority Order)
1. 404 page: what happened in one line, search box, and links to the three most useful sections
2. Correct status codes: true 4

# Context
Build the page frame: one header component and one footer component used by every page, with clearly defined slots for the few things that vary. The footer is a working surface, not a copyright afterthought.

## Core Features (Priority Order)
1. Header: brand, primary nav slot, action slot, consistent height, server-rendered
2. Footer: grouped link columns (product, resources, company, l

# Context
Build the settings area: profile, preferences, notifications and account sections, navigable and predictable, where every change communicates its save state and destructive actions cannot be stumbled into.

## Core Features (Priority Order)
1. Sectioned layout: sidebar navigation on desktop, collapsible sections on mobile
2. Auto-save per control with visible saved-state confirmation, no

# Context
Build the application's states system: reusable empty, loading, error and partial-data components with clear rules for which appears when. Every list, form and detail screen will use these; they are the difference between an app that guides and one that shrugs.

## Core Features (Priority Order)
1. EmptyState component: icon slot, one-line explanation, primary action, sized variants
2. S

# Context
Build the application's dialog system: modal and confirmation primitives with consistent sizes, focus management and dismissal semantics, used by every overlay in the app. One system, no per-feature dialog physics.

## Core Features (Priority Order)
1. Base modal: sm, md, lg sizes, header, body, footer slots, close affordance
2. Focus behavior: trap inside, initial focus on the safe acti

# Context
Build a data table for production volumes: sorting, filtering and pagination driven server-side, the current view encoded in the URL, and rendering that stays smooth at ten thousand rows. Tables are where generated apps quietly collapse; this one is specified against that.

## Core Features (Priority Order)
1. Column sorting, single-column with direction, ascending and descending, indica