How to Build Insurance claims tool with V0

1// Paste this prompt into V0's AI chat:
2// Build an insurance claims tool. Create a Supabase schema with:
3// 1. policyholders: id (uuid PK), user_id (uuid FK to auth.users), policy_number (text unique), full_name (text), email (text), phone (text), address (text), policy_type (text check in 'auto','home','health','life','business'), policy_start (date), policy_end (date), coverage_limit_cents (bigint)
4// 2. claims: id (uuid PK), policyholder_id (uuid FK to policyholders), claim_number (text unique), type (text check in 'auto_collision','auto_theft','home_damage','home_theft','health_medical','health_dental','life','business_liability'), description (text), incident_date (date), incident_location (text), estimated_amount_cents (bigint), approved_amount_cents (bigint), status (text default 'submitted' check in 'submitted','under_review','investigation','approved','partially_approved','denied','paid','closed'), priority (text default 'normal' check in 'low','normal','high','urgent'), assigned_adjuster_id (uuid FK to auth.users nullable), submitted_at (timestamptz), resolved_at (timestamptz)
5// 3. claim_documents: id (uuid PK), claim_id (uuid FK to claims), title (text), file_url (text), document_type (text check in 'photo','police_report','medical_record','receipt','estimate','other'), uploaded_by (uuid FK to auth.users), uploaded_at (timestamptz)
6// 4. claim_notes: id (uuid PK), claim_id (uuid FK to claims), author_id (uuid FK to auth.users), content (text), is_internal (boolean default true), created_at (timestamptz)
7// 5. claim_status_log: id (uuid PK), claim_id (uuid FK to claims), from_status (text), to_status (text), changed_by (uuid FK to auth.users), reason (text), created_at (timestamptz)
8// Add RLS: policyholders see their own claims, adjusters see assigned claims, managers see all.

1// Paste this prompt into V0's AI chat:
2// Build a claim submission wizard at app/claims/new/page.tsx as a 'use client' component.
3// Requirements:
4// - Stepper showing 4 steps: Incident Details → Documents → Review → Confirmation
5// - Step 1 (Incident Details): Select for claim type, Input for incident_date (date picker), Textarea for description, Input for incident_location, Input for estimated_amount (currency formatted)
6// - Step 2 (Documents): File upload zone accepting multiple files, Select for document_type per file (photo, police_report, medical_record, receipt, estimate, other), Preview thumbnails for uploaded images
7// - Step 3 (Review): Summary Card showing all entered data with edit buttons per section
8// - Step 4 (Confirmation): success message with claim_number display
9// - Zod validation: incident_date <= today, estimated_amount <= coverage_limit, at least one document required for auto/home claims
10// - Server Action that: generates claim_number (CLM-{year}-{sequence}), inserts claim, uploads documents to Supabase Storage bucket 'claim-documents', inserts claim_documents rows, creates initial claim_status_log entry
11// - Navigate to /claims/[id] after submission
12// - Use Card for step content areas and Badge for document type labels

1// Paste this prompt into V0's AI chat:
2// Build claim detail at app/claims/[id]/page.tsx.
3// Requirements:
4// - Header: claim_number, type Badge, status Badge (color-coded), priority Badge
5// - Status timeline: vertical Stepper showing each status_log entry with timestamp, author, and reason
6// - Tabs component with sections:
7//   1. Overview: incident details Card, estimated vs approved amount, assigned adjuster
8//   2. Documents: gallery grid of uploaded documents with download Button per file, document_type Badge, "Upload Additional" Button
9//   3. Notes: threaded conversation of claim_notes, Textarea to add new note, Switch for is_internal (visible only to adjusters/managers)
10//   4. History: full status_log Table with from→to transition, changed_by, reason, timestamp
11// - Action buttons (role-dependent):
12//   - Adjuster: "Approve", "Deny", "Request Investigation" buttons that open Dialog with reason Textarea and approved_amount Input (for approve)
13//   - Manager: "Reassign" Button with adjuster Select
14// - AlertDialog for deny action requiring a reason
15// - Server Actions for status transitions, note creation, and document upload

1// Paste this prompt into V0's AI chat:
2// Build the status transition system:
3// 1. Create a PostgreSQL function transition_claim_status(claim_id uuid, new_status text, changed_by uuid, reason text):
4//    - Fetch current status with FOR UPDATE lock
5//    - Validate against state machine rules:
6//      submitted → under_review only
7//      under_review → investigation, approved, partially_approved, denied
8//      investigation → approved, partially_approved, denied
9//      approved → paid
10//      partially_approved → paid
11//      denied → closed
12//      paid → closed
13//    - If invalid transition, RAISE EXCEPTION 'Invalid status transition from X to Y'
14//    - Insert into claim_status_log (from_status, to_status, changed_by, reason)
15//    - Update claims.status = new_status
16//    - If new_status in ('approved','denied','paid','closed'), set resolved_at = now()
17//    - Return the updated claim
18//
19// 2. Create API route at app/api/claims/[id]/status/route.ts:
20//    - PATCH handler that validates role permissions and calls the RPC
21//    - Adjusters can transition to under_review, investigation, approved, denied
22//    - Managers can do all transitions
23//    - Policyholders cannot change status
24//    - Use Zod to validate input: new_status, reason (required for deny)

1// Paste this prompt into V0's AI chat:
2// Build three pages:
3// 1. app/claims/page.tsx — claims list:
4//    - Table with columns: claim_number, type Badge, policyholder name, status Badge, priority Badge, submitted date, assigned adjuster
5//    - Column sorting on submitted_at and priority
6//    - Select filters: status, priority, claim type
7//    - Search Input for claim_number or policyholder name
8//    - Click row to navigate to /claims/[id]
9//
10// 2. app/page.tsx — role-based dashboard:
11//    - Policyholder view: my claims list with status indicators, "File New Claim" Button
12//    - Adjuster view: assigned claims queue sorted by priority DESC, unassigned claims needing pickup
13//    - Manager view: KPI Cards (total claims, avg processing days, total payouts), claims volume BarChart by month, status distribution PieChart
14//
15// 3. app/admin/page.tsx — management analytics:
16//    - Recharts BarChart: claims volume by month with status stacking
17//    - LineChart: average processing time trend
18//    - Cards: total payouts this month, denial rate, adjuster workload distribution
19//    - Table: top 10 highest-value open claims
20//    - Select for time period and claim type filtering
21//    - Wrap all charts in 'use client' components