App Builder Prompts for Lovable AI

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