Lovable AI Prompt Examples, With the Reasoning

# Context
Build the foundation of a multi-tenant SaaS: users sign up, get a workspace, and invite teammates who arrive in the same workspace with the right role. The target user is a small team adopting a tool together, so the invite must work before anything is polished.

## Core Features (Priority Order)
1. Email and password auth with session persistence across refresh
2. Workspace created automatically on first sign-in, creator becomes owner
3. Member list with three roles: owner, admin, member
4. Invite by email via tokenized link that joins the invitee to the inviter's workspace
5. Role-gated UI: only owner and admin can invite or change roles

## Access & Session Rules
- Roles are read from the database per request, never from client state
- Protected routes redirect signed-out users to sign-in and return them after
- Sessions persist across refresh and expire gracefully with a re-auth prompt, not a crash
- An expired or already-used invite shows a clear error and a way to request a new one

## Screens & States
- Sign in / sign up with inline validation, no alert() dialogs
- Member list: loading skeleton, and an empty state that prompts the first invite
- Invite dialog with a copyable link and a sent-state confirmation

## Build Order
Auth and the route guard first. Then the role-checking helper, before any UI that depends on a role. Then workspace and member reads, then the invite write path including the expired-token case.

## Safe-Guard Instructions
- Enforce roles in the database with row-level security as well as in the UI; hiding a button is not access control
- Never accept a role or workspace id from the client on writes
- Do not weaken a security policy to make a query work; if the query is denied, the query is wrong

# 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, indicator visible
2. Filters per column type: text contains, select of known values, date range
3. Sort, filters and page encoded in the URL; a pasted link reproduces the exact view
4. Row virtualization past a row threshold; the DOM never holds ten thousand rows
5. CSV export of the current filtered result, not just the visible page

## Data & Performance
- Sorting and filtering execute in the database; the client never sorts a partial dataset and pretends
- Filter changes debounce and cancel in-flight requests; stale responses never overwrite fresh ones
- Row selection supports select-all-matching with an explicit count, distinct from select-visible

## Screens & States
- Loading skeleton rows on first load; a subtle refresh indicator on filter changes
- Empty-by-filter offers clearing the newest filter; empty-table states differ
- Active filters render as removable chips above the table

## Build Order
Server-driven pagination and sorting first, then filters with URL encoding, then virtualization, then selection and export.

## Safe-Guard Instructions
- Export runs server-side against the filter set with a row cap and count warning
- URL state is validated on parse; a crafted URL must not inject filter logic
- Column headers are buttons with aria-sort; the table remains navigable by keyboard

# Context
Build a single-purpose landing page: capture an email address before a product launches. The visitor arrives from one known traffic source, so the page carries one offer and one action, and nothing that competes with them.

## Core Features (Priority Order)
1. Hero: the offer in one sentence, the form visible without scrolling
2. Email capture writing to Supabase with UTM parameters stored per signup
3. Inline success state replacing the form, no redirect, no alert
4. Duplicate handling: resubmitting the same address confirms instead of erroring
5. A substantive copy body below the fold: what it is, who it is for, three concrete FAQs

## Capture & Consent
- Client and server-side email validation; the server is the one that counts
- Store source, utm_source, utm_medium, utm_campaign and referrer on every row
- One-line consent text under the form stating what will be sent and how to leave

## Copy & Conversion
- One accent color, used by the submit button and nothing else
- Proof elements are placeholders clearly marked as placeholders; never invent names or numbers
- Maximum 65 characters per line of body copy; generous vertical rhythm

## Build Order
Static page with final copy first, so something exists to index. Then the form and write path with duplicate handling, then UTM capture, then analytics last.

## Safe-Guard Instructions
- The signups table accepts inserts and forbids reads from the client, with no exceptions for debugging
- No second call to action anywhere on the page
- The form must not lose the typed address on a validation error