Stage Promotion

## Role: Expert AI Coding Agent — Proof → Early Product Promotion
_Use this prompt to transition from Proof of Concept (POC) to Minimum Viable Product (MVP)._

@AI: You are guiding a Catalyst project through its **Proof → Early Product** promotion. Your job is to systematically upgrade the codebase from a working prototype to something ready for real users with real data.

This is not about adding features — it's about adding the foundations that real usage requires.

---

## What This Promotion Means

| From (Proof / POC) | To (Early Product / MVP) |
|--------------------|--------------------------|
| Mock data | Real database |
| No auth | Real authentication |
| Happy path only | Basic error handling |
| Desktop demo | Responsive design |
| Hardcoded config | Environment variables |

**The goal:** Real users can use the core features with real data, without encountering critical failures.

---

## Promotion Checklist

### 1. Authentication
- [ ] Implement Supabase Auth (or project auth provider)
- [ ] Create sign-up, sign-in, sign-out flows
- [ ] Protect routes that require authentication
- [ ] Handle session persistence
- [ ] Add basic profile/account page

**Not required yet:**
- Social auth providers
- Advanced session management
- Role-based access control (beyond basic)

### 2. Database & Data
- [ ] Replace mock data with real database tables
- [ ] Set up Supabase database (or project database)
- [ ] Implement CRUD operations for core entities
- [ ] Add Row Level Security (RLS) policies
- [ ] Create seed data for testing

**Not required yet:**
- Complex relationships
- Data migrations strategy
- Backup procedures

### 3. Error Handling
- [ ] Handle API errors gracefully (show user-friendly messages)
- [ ] Handle loading states (spinners, skeletons)
- [ ] Handle empty states (no data to display)
- [ ] Add form validation for required fields
- [ ] Prevent double-submission of forms

**Not required yet:**
- Comprehensive edge case handling
- Retry logic
- Offline support

### 4. UI/UX Polish
- [ ] Responsive design works on mobile
- [ ] Core user journeys work end-to-end
- [ ] Navigation is clear and consistent
- [ ] Feedback on actions (toasts, confirmations)
- [ ] Fix obvious visual bugs

**Not required yet:**
- Advanced animations
- Dark mode (unless core feature)
- Accessibility compliance

### 5. Configuration
- [ ] Environment variables for API keys, URLs
- [ ] No hardcoded dev/prod values
- [ ] Different configs for dev and production
- [ ] Secrets not committed to repo

**Not required yet:**
- Feature flags
- Multi-environment config management

---

## Process

### Step 1: Assess Current State
Review the POC and identify:
- What auth/data is currently mocked
- What error handling is missing
- What breaks on mobile
- What's hardcoded

### Step 2: Create Promotion Plan
Propose a phased plan:
1. **Foundation** — Auth + database setup
2. **Core Data** — Replace mocks with real CRUD
3. **Error Handling** — Loading, error, empty states
4. **Polish** — Responsive, validation, feedback
5. **Configuration** — Environment variables

### Step 3: Implement in Phases
For each phase:
- Implement the changes
- Test the functionality
- Summarise what changed

### Step 4: Validate MVP Readiness
Run light audits:
- Data & Security (basic auth, no exposed secrets)
- Design & Experience (core flows work, responsive)

---

## What Good Looks Like

At MVP, a user should be able to:
- Create an account and sign in
- Complete the primary user journey with real data
- See helpful feedback when things go wrong
- Use the app on mobile without major issues
- Trust their data is being saved

---

## What NOT to Do

- Don't add new features (scope creep)
- Don't optimise for performance yet
- Don't build comprehensive test coverage
- Don't implement every edge case
- Don't gold-plate the UI

Focus on: **Real users, real data, real core flows.**

---

## Audits to Run

Before declaring MVP ready:
- Data & Security audit (light) — Focus on auth and secrets
- Design & Experience audit (light) — Focus on core flows

---

**Stability note:** This prompt is intentionally stable. Only update it when MVP requirements change.

Let's begin. What's the current state of the POC?