Backend Logic Prompts for Lovable AI

# Context
Build an internal metrics dashboard for a small product team: a fixed set of company metrics, each computed by one saved query against the production database replica, displayed with current value, trend, and week-over-week delta.

## Core Features (Priority Order)
1. Metric cards: current value, 7-day sparkline, week-over-week delta with direction
2. One saved query per metric, stored w

# Context
Build an internal user management dashboard: support and admins find any account in seconds, see its state, and take the five common actions safely, with every action logged.

## Core Features (Priority Order)
1. Search by email, name, or account id, with results in under a second
2. User detail: plan, status, signup date, last active, recent key events
3. Actions: change plan, suspend, 

# Context
Build an API key manager for a developer-facing product: users create named keys, see them once, and manage their lifecycle; the server stores only hashes and records usage.

## Core Features (Priority Order)
1. Create key: name, optional expiry, shown in full exactly once with a copy button
2. Key list: name, prefix (first 8 chars), created, expires, last used
3. Revoke immediately; rot

# Context
Build an in-app notification system: events generate notifications, delivered live to online users and waiting for offline ones, with an accurate unread count and per-type user preferences.

## Core Features (Priority Order)
1. Notification feed: newest first, unread visually distinct, mark-one and mark-all read
2. Live delivery to online sessions; queued rows for offline users, no loss 

# Context
Build a file manager: users upload by drag or picker, organize with tags, find by search and filter, and preview without downloading, with storage quotas enforced on the server.

## Core Features (Priority Order)
1. Upload: multiple files, per-file progress, cancel, clear failure states with retry
2. Tags: create, assign multiple per file, filter by tag combinations
3. Search by filename

# Context
Build an API error tracker: failed requests are captured with context, grouped into issues by signature, counted, and worked through a simple status flow, with noise controls so the list stays meaningful.

## Core Features (Priority Order)
1. Capture: endpoint, method, status, error message, stack hash, timestamp, request id
2. Grouping: same signature (endpoint + error type + stack hash

# Context
Build user-visible session management: a settings page listing active sessions with device, approximate location and last activity, per-session and all-other revocation, backed by server-side session state that makes revocation take effect on the next request.

## Core Features (Priority Order)
1. Active sessions list: device summary, browser, approximate location, created, last active
2

# Context
Build a redirect manager: create short slugs on your domain pointing to destination URLs, count clicks, edit destinations without changing the public link, and keep the whole table auditable.

## Core Features (Priority Order)
1. Create redirect: slug (custom or generated), destination URL, optional note
2. The redirect itself: fast 302 by default with a per-link 301 option, explained in

# Context
Build an inventory tracker where current stock is the sum of movements: receipts, sales, adjustments and transfers are recorded events with actor and reason, and totals are derived, never edited directly.

## Core Features (Priority Order)
1. Item catalog: SKU, name, unit, location, reorder threshold
2. Movements: receive, remove, adjust, transfer between locations, each with actor, time

# Context
Build API rate limiting with an admin dashboard: per-key request limits over sliding windows, standard limit headers on every response, correct 429 behavior, and a view showing consumption and violations per key.

## Core Features (Priority Order)
1. Limit enforcement: requests per window per API key, sliding window counting
2. Response headers on every request: limit, remaining, reset t

# Context
Build a background job monitor: jobs report state transitions to a registry, the dashboard shows queues, running jobs, durations and failures, and dead jobs sit in a queue where a human can inspect, retry or discard them.

## Core Features (Priority Order)
1. Job registry: type, payload summary, state (queued, running, succeeded, failed, dead), timestamps, duration
2. Queue view: depth a

# Context
Build an RBAC engine: permissions and roles are rows, one server-side check function answers every access question, admins manage assignments through a readable matrix, and every change is audited.

## Core Features (Priority Order)
1. Permission registry: action keys (resource.verb) with descriptions, seeded from actual app actions
2. Roles: named permission sets, with system roles (own

# Context
Build a webhook listener: one endpoint pattern receives events from external services, verifies signatures, acknowledges fast, stores raw payloads, processes asynchronously with idempotency, and shows everything in a debug UI.

## Core Features (Priority Order)
1. Receiver endpoints per source with per-source signature verification
2. Store first, process later: raw payload persisted and

# Context
Build a CSV import pipeline: upload, map columns to fields, validate every row with clear errors, preview the outcome, then commit atomically, with a downloadable report of anything rejected.

## Core Features (Priority Order)
1. Upload with delimiter and encoding detection, first rows previewed immediately
2. Column mapping UI: your fields against their headers, auto-matched where names

# Context
Add soft delete and recovery to an app: deletions set a flag and timestamp, all reads exclude flagged rows by construction, a trash view lists recoverable items with time remaining, and a purge job hard-deletes past retention.

## Core Features (Priority Order)
1. Soft delete on the chosen entities: deleted_at timestamp plus deleted_by actor
2. Default-scope exclusion: normal queries nev