Skip to content

feat: complete Phase 2 - exercise customization and fixes #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
CarsonL15 merged 1 commit into from
Oct 31, 2025
Merged

feat: complete Phase 2 - exercise customization and fixes #2

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
260 changes: 260 additions & 0 deletions CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,260 @@
# Summit - AI Assistant Context File

**Last Updated**: October 31, 2025
**Version**: 0.2.0 (Phase 2 Complete)
**Purpose**: Quick reference for Claude Code or other AI assistants

---

## 🎯 Project Overview

**Summit** is a gamified rehabilitation exercise management platform for chiropractic clinics. It digitizes the Functional Movement Screen (FMS) assessment and automatically assigns corrective exercises with a mountain-climbing progress metaphor.

### Key Concept
Patients "climb the mountain" through 4 phases (Analyze → Mobilize → Stabilize → Optimize) by completing exercises assigned based on their FMS assessment scores.

---

## 📂 Project Structure

```
summit/
├── app/ # Next.js 14 App Router
│ ├── auth/
│ │ ├── login/
│ │ ├── signup/
│ │ └── reset-password/ # Password reset page (Phase 2)
│ ├── patient/
│ │ ├── page.tsx # Patient dashboard (weekly exercises)
│ │ └── exercise/[id]/ # Exercise completion page
│ ├── employee/
│ │ ├── page.tsx # Employee dashboard
│ │ ├── assessment/
│ │ │ ├── page.tsx # FMS assessment tool
│ │ │ └── review/[assessmentId]/ # Exercise review (Phase 2)
│ │ └── patient/[id]/
│ └── owner/
├── components/ui/ # shadcn/ui components
├── lib/supabase/ # Supabase client setup
├── types/supabase.ts # Database TypeScript types
├── supabase/
│ ├── schema.sql # Initial database schema
│ ├── seed.sql # 40+ exercise seed data
│ └── migrations/ # Phase 2 migrations (002, 003, 004)
├── DATABASE_SCHEMA.md # ⭐ SINGLE SOURCE OF TRUTH for DB
├── DEVELOPMENT.md # Development guide & testing
├── ROADMAP.md # Future features & timeline
├── MIGRATION_INSTRUCTIONS.md # How to apply Phase 2 migrations
└── README.md # Main project documentation
```

---

## 🗄️ Database Schema (8 Tables, 88 Columns)

**IMPORTANT**: Always check `DATABASE_SCHEMA.md` before making database changes!

### Core Tables:
1. **clinics** - Clinic information
2. **users** - User profiles (extends auth.users) with roles
3. **fms_assessments** - FMS scores (7 patterns, max 21 points)
4. **exercises** - Exercise library (40+ pre-seeded)
5. **exercise_assignments** - Patient exercise assignments with date ranges
6. **exercise_completions** - Daily completion tracking
7. **patient_progress** - Gamification (points, streaks, phase)
8. **achievements** - Earned badges

### Key Database Rules:
- **FMS Scoring**: Bilateral movements use LOWER of L/R scores (max 21 total)
- **Date Ranges**: Exercises use `start_date` and `end_date` (not single `due_date`)
- **Daily Tracking**: `completion_date` tracks daily completions via trigger
- **Custom Parameters**: `custom_sets`, `custom_reps`, `total_completions_required` per assignment

---

## 🔑 Key Business Logic

### FMS Assessment Flow:
1. Employee conducts 7-pattern FMS assessment
2. Bilateral movements scored (take lower of L/R)
3. Scores ≤1 trigger **1 exercise per category** (~5-7 total)
4. Redirect to review page for customization
5. Employee adjusts sets/reps/program duration
6. Patient sees exercises immediately

### Exercise Completion:
- Patients can complete exercises **multiple times per day**
- **10 points** awarded only on **FIRST daily completion**
- Subsequent completions same day = 0 points (no double-dipping)
- Streak maintained by completing ANY exercise each day

### Patient Onboarding:
1. Employee clicks "Add New Patient"
2. System generates temp password (user never sees it)
3. Patient receives **password reset email**
4. Patient sets own password via reset link
5. Patient auto-assigned to employee's clinic

---

## 🛠️ Tech Stack

- **Framework**: Next.js 14 with App Router
- **Language**: TypeScript (strict mode)
- **Database**: Supabase (PostgreSQL with Row Level Security - currently disabled)
- **Authentication**: Supabase Auth
- **Styling**: Tailwind CSS + shadcn/ui components
- **Hosting**: Vercel
- **Package Manager**: npm
- **Dev Server**: `npm run dev` (runs on port 3001)

### Important Dependencies:
- `@supabase/supabase-js` - Supabase client
- `@supabase/ssr` - Server-side rendering support
- `canvas-confetti` - Celebration animations
- `lucide-react` - Icons
- `class-variance-authority`, `clsx`, `tailwind-merge` - Utility classes

---

## 📋 Common Commands

```bash
# Development
npm run dev # Start dev server (http://localhost:3001)

# Production
npm run build # Build for production
npm start # Start production server

# Linting
npm run lint # Run Next.js linter
```

---

## 🚨 Critical Things to Know

### 1. Database Schema Changes
- **ALWAYS** read `DATABASE_SCHEMA.md` first
- **ALWAYS** update `DATABASE_SCHEMA.md` after schema changes
- Create migration files in `supabase/migrations/`
- Update `types/supabase.ts` to match schema

### 2. FMS Scoring
- Bilateral movements use `Math.min(left, right)` in frontend
- Database uses `LEAST(left, right)` in generated column
- **Max total score is 21** (not 36!)
- See `app/employee/assessment/page.tsx:100-109` for scoring logic

### 3. Exercise Assignment
- Only assign **1 exercise per category** (not 2)
- Use date ranges: `start_date` to `end_date`
- Default program duration is 7 days
- See `app/employee/assessment/page.tsx:280-300` for assignment logic

### 4. Points System
- Check for daily completions FIRST before awarding points
- Use `completion_date` field (not `completed_at`) for daily checks
- See `app/patient/exercise/[id]/page.tsx:150-180` for points logic

### 5. Authentication
- Password reset requires Supabase redirect URL configuration
- Redirect URLs: `/auth/reset-password`
- See `app/employee/page.tsx:90-120` for patient creation flow

---

## 🧪 Testing Workflow

### Quick Test (Employee → Patient Flow):
1. Create clinic in Supabase (if not exists)
2. Login as employee (set role + clinic_id in Supabase)
3. Add patient via "Add New Patient"
4. Check email for password reset link
5. Conduct FMS assessment (test bilateral scoring)
6. Review exercises on review page (~5-7 exercises)
7. Customize sets/reps/duration
8. Login as patient
9. Verify exercises show immediately
10. Complete exercise twice (verify points only on first)

### Test FMS Scoring:
Enter: Deep Squat=3, Hurdle(L=3,R=3), Inline(L=2,R=3), Shoulder(L=3,R=3), ASLR(L=2,R=3), Trunk=3, Rotary(L=3,R=3)
**Expected Total**: 19 (not 33)

---

## 🐛 Known Issues

1. **Video URLs are placeholders** - Not implemented yet
2. **RLS is disabled** - Need to re-enable for production
3. **Email templates** - Need customization
4. **Phase progression** - Only analyze → mobilize works
5. **Owner analytics** - Static data (no filtering)

---

## 📈 Current Phase Status

### ✅ Phase 1 Complete (Oct 30, 2025)
- MVP with all core features

### ✅ Phase 2 Complete (Oct 31, 2025)
- Fixed exercise visibility
- Fixed FMS scoring
- Exercise review & customization
- Password reset flow
- Daily tracking improvements

### 🔄 Phase 3 Next (Recommended):
1. Framer Motion animations (2-3 hrs)
2. Video integration (3-4 hrs)
3. Email notifications (4-5 hrs)
4. Phase progression logic (3-4 hrs)

---

## 💡 Quick Tips for AI Assistants

### Before Making Changes:
1. Read `DATABASE_SCHEMA.md` if touching database
2. Read `DEVELOPMENT.md` for current status
3. Read `ROADMAP.md` for planned features
4. Check if feature already exists (don't duplicate)

### When Writing Code:
- **FMS Scoring**: Use `Math.min()` for bilateral movements
- **Exercise Queries**: Filter by date ranges, not due_date
- **Points**: Check daily completions first
- **Types**: Import from `@/types/supabase`
- **Client**: Use `createClient()` from `@/lib/supabase/client` or `server`

### When Updating Database:
1. Create migration file in `supabase/migrations/`
2. Update `types/supabase.ts`
3. Update `DATABASE_SCHEMA.md`
4. Update `MIGRATION_INSTRUCTIONS.md`

### Common File Paths:
- FMS scoring logic: `app/employee/assessment/page.tsx:100-109`
- Exercise assignment: `app/employee/assessment/page.tsx:280-300`
- Review page: `app/employee/assessment/review/[assessmentId]/page.tsx`
- Patient dashboard query: `app/patient/page.tsx:40-60`
- Exercise completion: `app/patient/exercise/[id]/page.tsx:150-180`
- Add patient flow: `app/employee/page.tsx:90-120`

---

## 🔗 Related Files

- **User-facing docs**: `README.md`
- **Developer guide**: `DEVELOPMENT.md`
- **Future plans**: `ROADMAP.md`
- **Database reference**: `DATABASE_SCHEMA.md` ⭐
- **Migration guide**: `MIGRATION_INSTRUCTIONS.md`
- **This file**: `CLAUDE.md`

---

**Remember**: This project is ready for client demo! The core functionality works well. Next focus should be on polish (animations, videos) or production readiness (email notifications).
20 changes: 0 additions & 20 deletions CLAUDE.old.md
View file
Open in desktop

This file was deleted.

Loading