A student-wellbeing product prototype that brings planning, reflection, peer connection, and AI-guided check-ins into one gentle daily experience.
*VibeCare is a portfolio prototype, not a medical product, therapist, crisis service, or substitute for professional care.
University life asks students to manage academic pressure, personal routines, social connection, and emotional wellbeing across tools that rarely speak to one another. VibeCare explores a more coherent experience: a calendar-first workspace where lightweight mood reflection and support appear in the context of a student's actual day.
The project began as a rapid collaborative build. This repository is a carefully reconstructed portfolio edition for presentation use: the strongest product direction is preserved, duplicate experiments and exposed configuration are removed, and the implementation is documented with clearer safety and privacy boundaries.
Product Designer + Frontend Developer
- Lead the brainstorming and shaped the product concept and key user flows.
- Designed and implemented the responsive React interface.
- Integrated mood reflection, planning, avatar rewards, and AI-assisted experiences.
- Reworked the original prototype into a safer, reproducible portfolio repository.
VibeCare was created with 3 teammates.
The design is built around three principles:
- Meet students inside their routine. Wellbeing actions are connected to calendar context rather than isolated in another tracker.
- Keep reflection lightweight. Check-ins use small prompts, visible trends, and manageable next steps.
- Make support boundaries obvious. AI can guide reflection and assist moderation, but must not present itself as diagnosis, treatment, professional care, or reliable crisis monitoring.
| Area | Product intent |
|---|---|
| Dashboard and calendar | Combine schedule awareness, notes, suggested activities, and daily mood context. |
| Mood reflection | Capture a check-in and explore patterns across time, routine, and location. |
| Vibe Partner | Offer a customizable conversational companion for brief, supportive prompts. |
| Guided reflection | Walk through CBT-informed questions without claiming clinical authority. |
| Community Room | Explore peer connection with authenticated posting and fallible AI-assisted moderation. |
| Avatar rewards | Use lightweight progression and customization to encourage repeat engagement. |
flowchart LR
A["React + TypeScript client"] --> B["Supabase Auth"]
A --> C["Postgres with row-level policies"]
A --> D["Supabase Realtime"]
A --> E["Edge Functions"]
E --> F["Lovable AI Gateway"]
F --> G["Gemini model"]
A -. optional .-> H["Mapbox"]
The frontend is a Vite application using React, TypeScript, Tailwind CSS, shadcn/ui, TanStack Query, Recharts, and Mapbox GL. Supabase provides authentication, persistence, realtime updates, database policies, migrations, and Edge Functions.
Routes are lazy-loaded and larger chart, map, and Supabase dependencies are split into separate production chunks.
- Edge Functions require a valid Supabase JWT.
- Community moderation verifies that the authenticated user matches the submitted user ID before any service-role update.
- AI inputs are length-limited, and conversation history is constrained before gateway requests.
- Missing moderation is reported as degraded service rather than silently described as successful review.
- Product copy avoids unsupported claims about confidentiality, encryption, professional credentials, diagnosis, treatment, or guaranteed crisis detection.
- The included database policies should be reviewed and tested before real personal data is used.
For crisis support in the United Kingdom, contact NHS 111 and select the mental health option where available, or call Samaritans free on 116 123 for 24/7 emotional support. For immediate danger, call 999 or go to A&E. Outside the U.K., use an appropriate local crisis service.
- Node.js 20 or newer
- pnpm
- A Supabase project
- Access to a compatible AI gateway for the included Edge Functions
git clone https://github.com/tyh007/vibecare.git
cd vibecare
pnpm installcp .env.example .envAdd the public client values from Supabase:
VITE_SUPABASE_URL=https://your-project.supabase.co
VITE_SUPABASE_PUBLISHABLE_KEY=your-publishable-key
VITE_MAPBOX_TOKEN=optional-mapbox-tokenWithout the two Supabase values, VibeCare shows an actionable configuration screen instead of crashing.
- Link the project with the Supabase CLI.
- Apply the SQL files in
supabase/migrations/. - Configure
LOVABLE_API_KEYfor the current Edge Function gateway, or adapt the functions to another provider. - Deploy
vibe-partner-chat,cbt-therapist-chat, andmoderate-message.
The legacy function and route name cbt-therapist-chat is retained for migration compatibility; the user-facing experience is called Guided Reflection.
pnpm devOpen http://127.0.0.1:8080.
pnpm typecheck
pnpm lint
pnpm build
# or run the complete verification sequence
pnpm checkThis repository was rebuilt from the root application at source commit d2fc278.
The original repository is intentionally untouched. Its Git history was not imported because it contains committed environment files, a second divergent application, and unrelated notebook material. This portfolio edition begins with a new sanitized history while preserving the provenance link above.
- This is a prototype in a student activity and not a product.
- Backend configuration is required; there is no mock-data fallback for authentication or server features.
- The AI gateway configuration reflects the original prototype and may require adaptation.
- Automated moderation is probabilistic and cannot guarantee safety.
- The onboarding support-contact screen demonstrates a concept and does not contact anyone automatically.
- The product has not undergone clinical validation, formal security review, or production privacy assessment.
- Automated end-to-end and database policy tests remain future work.
This repository is published for portfolio review and technical discussion. No open-source license has been added because contributor authorization has not yet been confirmed. All rights remain with the respective contributors unless a license is added later.