Lovable AI Prompt Library: 101 Prompts and Examples

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

# Context
Build an internal prompt library: team members store prompts with named variables, copy them with variables filled from a form, track versions as prompts improve, and see which prompts the team actually uses.

## Core Features (Priority Order)
1. Prompt entries: title, body with {variable} placeholders, category, usage notes, owner
2. Copy flow: clicking copy opens a variable form, outpu

# 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 a request explorer for your own API: users compose requests from your actual endpoint catalog, send them with their own credentials, inspect responses, and save named examples for reuse.

## Core Features (Priority Order)
1. Endpoint picker from your API catalog: method, path, described parameters
2. Request composer: path params, query params, headers, JSON body with validation ag

# Context
Add paid subscriptions to an existing app using Stripe Checkout. Entitlements per plan are already defined in the app; this prompt wires purchase, verification and lifecycle. Trust the webhook, not the redirect.

## Core Features (Priority Order)
1. Plan selection UI reading plan definitions from one config object
2. Stripe Checkout session creation on the server, never exposing the secr

# 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 a landing page for a dated event: a countdown to one canonical moment, email capture for reminders, and a defined transformation of the page when the countdown reaches zero.

## Core Features (Priority Order)
1. Countdown from a single UTC timestamp, rendered in the visitor's local time zone with the zone named
2. Email capture: 'remind me', storing the address with UTM parameters

# Context
Build a lightweight CRM: contacts and companies with duplicate prevention, a definable pipeline, fast activity logging, and a today view that surfaces due follow-ups before deals cool.

## Core Features (Priority Order)
1. Contacts: name, email, company, tags, owner, with company pages aggregating their contacts
2. Pipeline: definable stages, deals with value and expected close, drag bet

# 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 weather dashboard consuming a third-party weather API: current conditions and forecast for saved locations, with response caching, a visible data age, request budget tracking and honest failure states.

## Core Features (Priority Order)
1. Saved locations: add by search, reorder, remove, with current conditions per card
2. Detail view: hourly next 24h, daily next 7 days, sensible

# Context
Build a roadmap planner for a product team: cards move across stage columns, order within a column matters, and shipped work becomes a changelog entry without retyping. Decide visibility per board: internal or public read-only.

## Core Features (Priority Order)
1. Board with four columns: Ideas, Planned, In Progress, Shipped
2. Cards: title, one-paragraph description, tags, target quart

# 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
An existing landing page converts at a known baseline. Build variant testing: serve visitors one of two versions differing in exactly one element, keep the assignment stable per visitor, and measure conversion per variant from the first impression.

## Core Features (Priority Order)
1. Variant definition: one changed block (hero promise, CTA wording, or proof section), everything else sh

# Context
Build a survey tool: compose surveys from a small set of well-made question types, share by link, protect response integrity, and read results in views that answer the question the survey asked.

## Core Features (Priority Order)
1. Builder: single choice, multiple choice, scale (1-5, 1-10), short text, long text, reorderable
2. Share: public link per survey, open and close dates, respon

# 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 an AI PDF summarizer: upload a PDF, extract its text, produce a structured summary shown beside the source, with limits and failures stated plainly and costs controlled per account.

## Core Features (Priority Order)
1. Upload with page and size limits stated up front, progress shown
2. Extraction with per-page status; scanned or image pages reported as unextractable, not silently 

# Context
Build the customer billing area for an app that already has Stripe subscriptions. Users need to see what they paid, change their card, and change their plan without emailing support. Stripe is the source of truth; this page displays it.

## Core Features (Priority Order)
1. Invoice history list: date, amount, status, hosted invoice link
2. Current plan card with change-plan and cancel ac

# 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
Add first-party analytics to a landing page: enough to know traffic, source, device, conversion and drop-off, collected by your own endpoint, readable on one internal dashboard. No external analytics script.

## Core Features (Priority Order)
1. Pageview capture: path, referrer, UTM parameters, device class, timestamp
2. Conversion event tied to the page's one goal (form submit)
3. A dai

# Context
Build a support ticketing tool: requests arrive by form and forwarded email, become tickets with status and owner, agents reply from the tool with internal notes alongside, and response times are visible.

## Core Features (Priority Order)
1. Intake: a support form and an inbound email address both creating tickets with requester identity
2. Ticket lifecycle: new, open, waiting-on-custom

# 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 an AI insights layer over an existing analytics dataset: on schedule or on demand, it queries defined metrics, detects changes worth words, and writes a short narrative where every claim cites the number behind it.

## Core Features (Priority Order)
1. Metric bindings: each insight source is a defined query with owner and description, reused from your metrics layer
2. Change detect

# Context
Inbound leads arrive from forms and product signups. Build transparent lead scoring: named rules award points on attributes and behavior, every score is explainable, and sales works from a ranked queue instead of a chronological inbox.

## Core Features (Priority Order)
1. Rules table: condition, points, active toggle (e.g. company email +10, pricing page visit +15)
2. Score per lead com

# 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
A generated site has public pages that should rank. Build the indexability layer: sitemap.xml, per-page canonicals and titles, robots.txt, and basic structured data, all derived from the route list so nothing can drift.

## Core Features (Priority Order)
1. One route registry: path, title, description, indexable flag, content date
2. sitemap.xml generated from the registry, indexable rou

# Context
Build multi-user chat: channels and direct messages with live delivery, dependable history, correct unread counts, presence, and moderation controls, built to survive reconnects and growth.

## Core Features (Priority Order)
1. Channels: create, join, leave, member list; DMs as private two-person channels on the same model
2. Messages: send, edit with marker, delete with tombstone, live 

# 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
Build a translation tool on an AI model: text in, translation out across your supported language pairs, with a glossary that locks your product terms, tone presets, and honest handling of ambiguity.

## Core Features (Priority Order)
1. Translate: source text, target language, output beside input with copy
2. Glossary: your terms with required translations per language, injected into eve

# Context
An app with workspaces and basic roles exists. Build the management layer: changing roles, removing members, and transferring ownership, with the rules enforced in the database and every change recorded.

## Core Features (Priority Order)
1. Member table: name, email, role, last active, joined date
2. Role changes via inline select, owner and admin only
3. Member removal with confirmatio

# 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 a press and media page: everything a journalist needs to write about the company accurately without waiting for a reply. Facts, quotes, assets, contact, all current and all downloadable.

## Core Features (Priority Order)
1. Fact block: what the product is in one sentence, founded date, founder names, location, one-line traction statement with its as-of date
2. Approved quotes: two

# Context
Build a habit tracker: users define habits with schedules, check them off in one tap, build streaks computed against their own timezone and declared schedule, and read their history as patterns.

## Core Features (Priority Order)
1. Habits: name, schedule (daily, specific weekdays, N-times-per-week), optional reminder time
2. Check-off: one tap from the main screen, undo within the day, 

# 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 in-product chat assistant: users ask questions, answers ground in your documentation and their account context, sources are cited, unanswerable questions escalate to a human channel gracefully.

## Core Features (Priority Order)
1. Chat UI: streaming responses, message history within the conversation, typing and error states
2. Grounding: retrieval over your docs corpus; answers

# Context
A SaaS stores logins, feature usage, billing events and support tickets. Build a churn-risk view: a 0-100 risk score per account from weighted named signals, always shown with its reasons, plus a weekly view of who moved.

## Core Features (Priority Order)
1. Signals config: recency of login, 30-day usage trend, failed payments, seat shrinkage, ticket sentiment flag
2. Risk score per acc

# 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 landing page targeting one search query. The searcher's intent defines the structure; the page answers it thoroughly enough to deserve the ranking, then converts attention it has earned. Server-rendered throughout.

## Core Features (Priority Order)
1. An H1 and title matched to the query's actual intent, not just its words
2. The direct answer within the first 150 words, before 

# Context
Build a task list with an AI suggestion layer: fast capture, then per-task proposals (breakdown into subtasks, priority, estimate) rendered as suggestions the user accepts, edits or dismisses, with every acceptance marked.

## Core Features (Priority Order)
1. Capture: one input, enter to add, no required fields at capture time
2. Task basics: done state, due date, notes, manual ordering

# 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 an API documentation generator: parse the OpenAPI spec, render per-endpoint pages with parameters, schemas, responses and runnable examples, rebuilt on spec change so drift is impossible.

## Core Features (Priority Order)
1. Spec parsing: endpoints, parameters, request/response schemas, auth requirements, with a validation report of spec gaps
2. Per-endpoint pages: description, pa

# Context
Build a feature flag system for a multi-tenant SaaS: flags gate features by plan tier, percentage rollout, or explicit account list, evaluated server-side through one function, with an admin UI and a change log.

## Core Features (Priority Order)
1. Flags: key, description, on/off, targeting (all, plan tiers, percentage, account list)
2. One server-side evaluation function used by every 

# 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 a gated download page for one asset (guide, checklist, template pack): the visitor sees what they get, trades an email, receives it instantly, and knows exactly what follows. The gate is a fair trade, not a trap.

## Core Features (Priority Order)
1. Asset preview: table of contents or sample pages, page count, format, last-updated date
2. Capture form: email only, with a disclosur

# Context
Build a booking system: visitors pick a service, see genuinely available slots in their timezone, book with an atomic hold that makes double-booking impossible, and manage their booking through links that respect your notice rules.

## Core Features (Priority Order)
1. Services: name, duration, buffer before/after, active hours per weekday
2. Slot display: available times computed from h

# 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 an image captioning tool: upload images singly or in batch, generate alt text and longer descriptions to defined style rules, flag low-confidence results for review, and export in useful formats.

## Core Features (Priority Order)
1. Upload: single and batch with per-image progress and format validation
2. Two outputs per image: alt text (under 125 characters, subject-first) and a 

# Context
An app with paid plans needs promo codes: created by an admin, redeemed at checkout, honest about expiry, and resistant to the usual abuse. Codes influence price only at the moment of payment, server-side.

## Core Features (Priority Order)
1. Admin creation: code, type (percent or fixed), applicable plans, max redemptions, expiry
2. Redemption field at checkout with instant server valid

# 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 a pricing page for two or three plans: what each costs, what genuinely differs, which one fits whom, and answers to the questions that stall purchases. Every number on it must match what the product enforces.

## Core Features (Priority Order)
1. Plan cards: price, billing unit, the three differences that matter, one CTA each
2. A recommendation with a reason ('most solo builders s

# Context
Build a member directory: members complete profiles with per-field visibility choices, browse and search each other by skills, location and interests, and connect through the directory without exposing contact details until they choose to.

## Core Features (Priority Order)
1. Profiles: name, photo, headline, skills tags, location, links, about, each field with a visibility toggle (membe

# 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 a research assistant: a question spawns a research run that gathers from configured sources, extracts relevant passages, and composes an answer where every claim links to its supporting quote.

## Core Features (Priority Order)
1. Research runs: question in, status through gathering, extraction and composition, answer out
2. Source panel: every document consulted, with the exact pa

# Context
An app with a catalog and user behavior events (views, saves, purchases) needs recommendations: a personal shelf per user, similar-item rows on detail pages, and an explicit fallback ladder so no surface is ever empty.

## Core Features (Priority Order)
1. Event capture: view, save, purchase per user per item, timestamped
2. A 'For you' shelf: recency-weighted category and attribute affi

# 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 social-proof page assembling verifiable customer evidence: quotes, results and logos, each with provenance. This page's entire value is credibility, so its design constraint is verifiability, not volume.

## Core Features (Priority Order)
1. Featured quotes: full name, role, company, photo where permitted, each with permission on record
2. Result statements with context: what cha

# Context
Build a simple blog CMS: write in markdown with live preview, manage drafts and scheduled publishing, and serve posts as fast server-rendered pages with the metadata, feed and sitemap that make content findable.

## Core Features (Priority Order)
1. Editor: markdown with preview, title, slug (editable before first publish, locked after), excerpt, cover image
2. States: draft, scheduled w

# 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
Add social login to an app: two OAuth providers with correct flows, account creation and linking rules by verified email, coexisting with email/password, with every edge case given a decided behavior.

## Core Features (Priority Order)
1. Sign in with Google and one more provider fitting your audience, standard OAuth authorization-code flow
2. Account rules: new social sign-in with an em

# Context
An app knows which three actions predict whether a new user sticks. Build an onboarding checklist that drives those actions, verifies them from live events, and gets out of the way when done.

## Core Features (Priority Order)
1. A checklist of 3 to 5 steps, each mapped to a verifiable product event
2. Auto-completion: doing the thing checks the step, wherever it was done
3. Progress per

# 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 a waitlist page for a pre-launch product: explain what is coming and when, capture emails with source attribution, confirm honestly, and keep the list unreadable from the client. Clarity converts here; vagueness reads as vapor.

## Core Features (Priority Order)
1. Hero: what the product is in one concrete sentence, and the expected launch window
2. What joining gets you: early acc

# Context
Build a reusable file upload component: drag-drop and picker input, instant local previews, per-file progress with cancel and retry, validation before and after transfer, and an interface other features consume.

## Core Features (Priority Order)
1. Input: drag-drop zone with keyboard-accessible picker fallback, multi-file
2. Local previews immediately on selection: image thumbnails, PDF

# 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 a public API explorer: a catalog of APIs with structured capsule pages (what it does, auth model, rate limits, example call) and an in-browser console to try requests, all server-rendered.

## Core Features (Priority Order)
1. Catalog: APIs with category, auth type, pricing model, capsule description, searchable and filterable
2. API detail pages: overview, auth requirements, key e

# Context
An app has plan tiers with defined limits (per-month actions, storage, seats). Build the enforcement and the visibility: limits that hold on the server, and meters that tell users where they stand before they hit a wall.

## Core Features (Priority Order)
1. One plan-limits config object: every limit defined once, imported everywhere
2. Server-side enforcement at each metered action, fai

# 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 an AI email template builder: describe the email's job, get a client-compatible HTML template with your brand applied and merge fields placed, editable in a structured editor before export or send.

## Core Features (Priority Order)
1. Brand settings once: logo, colors, font stack, footer block with the legally required bits
2. Generate from a brief: 'a welcome email with one CTA' 

# 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 an AI action logger: every model call in your product writes a structured record (actor, feature, prompt inputs, output, model, tokens, cost, latency), with a browse-and-search UI and retention rules.

## Core Features (Priority Order)
1. The log write: one function wrapping every model call, recording before and after, failing open so logging never blocks the feature
2. Browse UI:

# Context
An app offers a 14-day trial of its paid features. Build the full lifecycle: visible countdown, expiry that actually restricts, retained data, and a clean path back. The trial end must hold even if the user never opens the app again.

## Core Features (Priority Order)
1. trial_ends_at set server-side at signup; all logic derives from it
2. A countdown surface: subtle until 3 days remain,

# 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 poll tool: create a one-question poll in seconds, share a link, voters answer in one tap and see live results immediately, with the results view designed to be screenshotted and embedded.

## Core Features (Priority Order)
1. Create: question, 2-6 options, optional close time, done in one screen
2. Vote: one tap, no account, results revealed after voting, changeable while the pol

# 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 text classification service on an AI API: input text is labeled against your defined label set with confidence, low-confidence items queue for human review, and everything is measured against drift.

## Core Features (Priority Order)
1. The label set: names, definitions and two examples each, versioned as data, injected into every classification request
2. Classify endpoint: text

# Context
Build in-app announcements for a SaaS: admins publish targeted messages (new feature, maintenance, plan changes) that render as non-blocking banners or cards, dismiss permanently per user, and expire on schedule.

## Core Features (Priority Order)
1. Admin composer: title, body, type (info, feature, warning), placement (banner or card)
2. Targeting: all users, plan tiers, or a behavior f

# 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
Build a quiz builder: authors compose scored quizzes (points toward a total) or outcome quizzes (answers weighted toward result buckets), takers get a satisfying result screen, and completion is measured per question.

## Core Features (Priority Order)
1. Builder: question with 2-5 answers, per-answer points (scored mode) or per-answer outcome weights (outcome mode)
2. Result screens: sc

# 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

# Context
Integrate payment provider webhooks: signature-verified events drive subscription and entitlement state, processing is idempotent and ordered, failures alert loudly, and a reconciliation view proves your database agrees with the provider.

## Core Features (Priority Order)
1. Verified receipt: signature checked, raw event stored, fast acknowledgment, processing async
2. The event handler

# Context
Build audit logging for a multi-tenant SaaS: security-relevant actions are captured append-only, and admins get a viewer that answers who did what, when, to what, with filters and export.

## Core Features (Priority Order)
1. Capture: actor, action, target type and id, timestamp, IP, and a compact context object
2. Coverage of the actions that matter first: auth events, role changes, dat

# 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

# Context
Build a budget planner: monthly budgets per category, fast manual transaction entry, and a month view answering 'what is left where', with rollover behavior the user chooses per category.

## Core Features (Priority Order)
1. Categories with monthly budget amounts, grouped (essentials, lifestyle, goals), editable mid-month with the change logged
2. Transaction entry: amount, category, op

# Context
Build a CRM sync: your product's accounts and contacts against the CRM's, with per-field mapping, direction and conflict rules declared as configuration, changes logged with reasons, and drift surfaced.

## Core Features (Priority Order)
1. Field mapping config: your field, their field, direction (push, pull, two-way), conflict winner, transform if any
2. Sync engine: scheduled and on-de

# Context
Build a reading list tracker: capture articles and books fast, move them through an honest status flow, attach notes when finishing, and get resurfacing that turns the pile into a practice.

## Core Features (Priority Order)
1. Capture: paste a URL (title and site auto-fetched) or type a book title, tags optional, under five seconds
2. Statuses: to-read, reading, finished, abandoned; aba

# Context
Integrate a hosted feature-flag service: all evaluation flows through one wrapper with typed flag definitions, defaults that work offline, environment separation, and a registry that keeps flags from becoming permanent.

## Core Features (Priority Order)
1. The wrapper: one module owning the provider SDK; the rest of the codebase imports flags, never the provider
2. Typed flag registry: 

# Context
Build a contact form backend: submissions validate and store first, notify reliably second, sit in an inbox with handled-states third, with spam defense layered in from the start.

## Core Features (Priority Order)
1. The form: name, email, message, optional topic select, inline validation, a success state that sets response expectations
2. Storage first: every valid submission is stored

# Context
Build a resource booking manager: define resources with their rules, let members reserve conflict-free time slots, see availability at a glance, and give admins the utilization picture.

## Core Features (Priority Order)
1. Resources: name, type, location, capacity where relevant, per-resource rules (min/max duration, advance-booking window, approval required or not)
2. Booking: pick res

# Context
Build a recipe generator: users enter available ingredients and constraints, get structured recipes (ingredients with amounts, ordered steps, time and servings) that respect the constraints absolutely, with substitutions where the pantry falls short.

## Core Features (Priority Order)
1. Ingredient input: type-ahead entry with quantities optional, a persistent pantry list for staples
2. 

# Context
Build a job description creator: a short role brief generates a structured posting (summary, responsibilities, requirements split hard/nice, benefits, process), run through language and requirement checks before anyone can copy it.

## Core Features (Priority Order)
1. The brief: role title, level, team context, 3-5 duty bullets, location/remote, salary range field
2. Generation into fix

# Context
Build a quick-notes tool: a note is captured in under two seconds from anywhere in the app, #tags typed inline become the only organization, and search plus tag filters retrieve anything fast enough to trust the pile.

## Core Features (Priority Order)
1. Capture: a global input (keyboard shortcut opens it anywhere), enter saves, no required fields, no folders
2. Inline tags: #words in t

# Context
Build a meeting-notes-to-todos tool: notes go in, an extraction pass proposes action items with owners and dates where stated, a human confirms in one review screen, and confirmed items become tracked tasks.

## Core Features (Priority Order)
1. Input: paste notes or upload a text/markdown file, with meeting title and date
2. Extraction: proposed action items, each with the source line q

# Context
Build an AI customer FAQ: a curated set of Q&A entries and help content answers visitor questions with citations, questions the corpus cannot answer are said so honestly and logged, and the log becomes new entries.

## Core Features (Priority Order)
1. The corpus: FAQ entries (question, answer, category) managed in an admin view, plus optional imported help articles
2. Ask interface: a q

# Context
Build an appointment scheduler: a host defines weekly availability with exceptions and buffers, shares a booking link per meeting type, and invitees pick from live slots rendered in their own timezone, with the resulting appointment protected against conflicts.

## Core Features (Priority Order)
1. Meeting types: name, duration, location mode (call link, phone, in person), buffer before/

# Context
Build event recommendations: users express preferences implicitly (views, saves, attendance) and explicitly (topics, formats, times), and a ranked 'for you' feed suggests events with a stated reason per suggestion.

## Core Features (Priority Order)
1. Preference capture: explicit topic and format picks at onboarding, plus implicit signals (viewed, saved, attended, dismissed) recorded fr

# Context
Build an internal dashboard builder: engineering defines approved data sources (named queries with parameters), teams compose dashboards from widgets bound to those sources, with layout, refresh and sharing handled properly.

## Core Features (Priority Order)
1. Source registry: named queries with typed parameters, owner, description and allowed visualizations, defined in code
2. Widgets

# Context
Build a help center: categorized articles with owners and review dates, fast search, was-this-helpful feedback routed to owners, served as fast indexable pages that measurably deflect tickets.

## Core Features (Priority Order)
1. Articles: title, task-focused body (markdown with step lists and callouts), category, owner, last-reviewed date
2. Structure: categories with descriptions, fea

# Context
Build an employee directory: profiles with role, team, expertise and contact preferences, a browsable team structure, and search tuned for 'who knows about X', with the data kept current by design rather than by nagging.

## Core Features (Priority Order)
1. Profiles: name, photo, role title, team, location/timezone, expertise tags, how-to-reach-me preferences, a short now-working-on lin

# Context
Build a form builder with conditional logic: authors compose fields with validation, attach show-when rules, preview the branching live, and collect submissions that record which path the respondent took.

## Core Features (Priority Order)
1. Field types: text, email, number with ranges, select, multi-select, date, file upload, each with required and validation options
2. Conditions: sho

# Context
Build a kanban workflow board: columns represent your stages with optional WIP limits, cards move by drag with history recorded, and the board surfaces flow health (aging cards, cycle time) instead of just position.

## Core Features (Priority Order)
1. Board: columns definable with names, order and optional WIP limit; cards with title, description, assignee, labels
2. Movement: drag bet