API & Integration Prompts for Lovable AI

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