How to Build HR management system with V0

1// Paste this prompt into V0's AI chat:
2// Build an HR management system. Create a Supabase schema with:
3// 1. departments: id (uuid PK), name (text), head_id (uuid FK to employees nullable), parent_id (uuid FK to departments nullable), created_at (timestamptz)
4// 2. employees: id (uuid PK), user_id (uuid FK to auth.users), department_id (uuid FK to departments), first_name (text), last_name (text), email (text), phone (text), job_title (text), employment_type (text check in 'full_time','part_time','contract'), start_date (date), end_date (date nullable), salary_cents (bigint), manager_id (uuid FK to employees nullable), status (text default 'active' check in 'active','on_leave','terminated','onboarding'), avatar_url (text), created_at (timestamptz)
5// 3. leave_requests: id (uuid PK), employee_id (uuid FK to employees), type (text check in 'vacation','sick','personal','parental','unpaid'), start_date (date), end_date (date), days (decimal), reason (text), status (text default 'pending' check in 'pending','approved','rejected'), approved_by (uuid FK to employees nullable), created_at (timestamptz)
6// 4. leave_balances: id (uuid PK), employee_id (uuid FK to employees), type (text), year (int), total_days (decimal), used_days (decimal default 0), unique(employee_id, type, year)
7// 5. onboarding_tasks: id (uuid PK), employee_id (uuid FK to employees), title (text), description (text), assigned_to (uuid FK to employees), due_date (date), completed (boolean default false), position (int)
8// 6. time_entries: id (uuid PK), employee_id (uuid FK to employees), date (date), hours (decimal), project (text), notes (text), created_at (timestamptz)
9// 7. documents: id (uuid PK), employee_id (uuid FK to employees), title (text), file_url (text), type (text check in 'contract','id','certificate','other'), uploaded_at (timestamptz)
10// Add RLS: employees see their own data, managers see their reports, HR admins see all.

1// Paste this prompt into V0's AI chat:
2// Build an HR dashboard at app/page.tsx.
3// Requirements:
4// - Stats Cards row: total employees, open leave requests count, employees onboarding, departments count
5// - Recharts BarChart showing headcount by department (wrap in 'use client' component)
6// - PieChart showing leave type distribution for the current month
7// - Recent activity feed: latest leave requests, new hires, completed onboarding tasks
8// - Navigation to /employees, /leave, /reports
9//
10// Build employee directory at app/employees/page.tsx:
11// - Table with columns: Avatar + name, department, job title, status Badge, start date, actions
12// - Column sorting on name and start_date
13// - Search Input filtering by name or email
14// - Select filter for department
15// - Badge colors: active=green, on_leave=yellow, terminated=red, onboarding=blue
16// - Click row to navigate to /employees/[id]
17// - "Add Employee" Button linking to /employees/new

1// Paste this prompt into V0's AI chat:
2// Build employee profile at app/employees/[id]/page.tsx.
3// Requirements:
4// - Header: Avatar, full name, job title, department Badge, status Badge
5// - Tabs component with sections:
6//   1. Info tab: Card with personal details (email, phone, employment type, start date, salary), edit Button for HR admins
7//   2. Leave tab: Table of leave requests (type, dates, days, status Badge), "Request Leave" Button opening Dialog with DatePickerWithRange, Select for leave type, Textarea for reason
8//   3. Time tab: Table of time entries this month, total hours Card, "Log Time" Button
9//   4. Documents tab: list of uploaded documents with download links, "Upload" Button using file Input that uploads to Supabase Storage bucket 'employee-documents'
10//   5. Onboarding tab (visible only for status='onboarding'): Checkbox list of onboarding tasks with assigned person and due date
11// - Server Actions for leave request submission, time entry logging, document upload, onboarding task completion
12// - Zod validation on all form inputs

1// Paste this prompt into V0's AI chat:
2// Build leave management at app/leave/page.tsx and create the approval RPC.
3// Requirements:
4// - Pending leave requests queue: Table showing employee name, leave type, dates, days requested, reason
5// - Approve/Reject buttons per row
6// - Create a PostgreSQL function approve_leave(request_id uuid, approver_id uuid):
7//   BEGIN;
8//   SELECT days, type, employee_id FROM leave_requests WHERE id = request_id AND status = 'pending' FOR UPDATE;
9//   SELECT total_days - used_days AS remaining FROM leave_balances WHERE employee_id = emp AND type = leave_type AND year = current_year FOR UPDATE;
10//   IF remaining < requested_days THEN RAISE EXCEPTION 'Insufficient leave balance';
11//   UPDATE leave_balances SET used_days = used_days + requested_days;
12//   UPDATE leave_requests SET status = 'approved', approved_by = approver_id;
13//   COMMIT;
14// - API route at app/api/leave/approve/route.ts that calls this RPC
15// - Calendar overlay showing approved leave per team (visible to managers)
16// - Badge for leave status: pending=yellow, approved=green, rejected=red
17// - AlertDialog for rejection requiring a reason

1// Paste this prompt into V0's AI chat:
2// Build two pages:
3// 1. app/employees/new/page.tsx — multi-step onboarding form ('use client'):
4//    - Step 1: Personal info (first_name, last_name, email, phone, avatar upload)
5//    - Step 2: Employment details (department Select, job_title, employment_type Select, start_date, salary)
6//    - Step 3: Manager assignment (Select from existing employees in the chosen department)
7//    - Step 4: Onboarding tasks (pre-filled checklist with common tasks, ability to add custom tasks)
8//    - Progress indicator showing current step
9//    - Server Action to insert employee + leave_balances (auto-create vacation/sick/personal with defaults) + onboarding_tasks in one transaction
10//
11// 2. app/reports/page.tsx — HR analytics:
12//    - Recharts LineChart: headcount trend over 12 months
13//    - BarChart: leave utilization by department
14//    - PieChart: employment type distribution
15//    - Cards: average tenure, turnover rate this year, departments with highest leave usage
16//    - Select for time period filtering
17//    - Wrap all charts in 'use client' components