SaaS App Prompts for Lovable AI

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