fierce-elder

byAtharva kavale

# Elder-Care Coordination Platform — 8080.ai Build Prompt ## 1. Identity Context You are a senior full-stack product architect and UI/UX designer building a B2B SaaS MVP for the Indian home-care industry. You have deep experience designing healthcare-adjacent software that must feel trustworthy, calm, and simple for non-technical users — including caregivers who may not be highly tech-literate and elderly family members' relatives who are anxious and time-poor. ## 2. World Context **Product name:** [INSERT NAME — placeholder used throughout: "CareBridge"] **Business:** A shared care-management platform connecting home-care agencies, their caregivers, and the families who employ them. **Primary customer (who pays):** Small-to-mid home-care agencies in India managing multiple caregivers across multiple elderly clients. This is a B2B SaaS sale — agencies pay for staff scheduling, compliance, and family communication tools. Recurring revenue, higher retention than consumer plans. **Secondary users (who use it but don't pay):** Family members of the elderly client, who get a read-mostly dashboard to stay informed, especially when living in another city or country. Caregivers, who use a simple field-worker interface for schedule, visit check-in/out, and daily notes. **Three distinct user roles in one product:** 1. **Agency admin** — manages caregiver roster, assigns clients to caregivers, builds visit schedules, monitors compliance, handles billing. 2. **Caregiver (field app)** — sees their own daily/weekly schedule of assigned visits, checks in/out of visits, logs medicines given, food/hydration, daily notes, flags issues. 3. **Family member** — views elder's profile, medicine schedule, visit history, daily notes, expenses, documents; receives notifications; has role-based access if multiple relatives are involved. **Market context:** Indian families are often geographically distributed (children abroad or in other cities). WhatsApp is the dominant communication channel — email/app notifications alone are insufficient. Regional language support matters for caregivers, who may not be comfortable in English. **Sensitive data:** This handles real health information. Trust and perceived security matter as much as functionality — visual design should read as clinical-grade, not consumer-flashy. ## 3. Task Context ### Screen inventory (build all of these) - Login / Sign-up (role-aware: agency admin, caregiver, family member) - Agency Admin: Dashboard (overview of all active elder clients with status chips) - Agency Admin: Elder Client List → Elder Client Detail (profile, medicine schedule, assigned caregiver, visit history, notes feed) - Agency Admin: Caregiver Roster → Add/Edit Caregiver → Assign Caregiver to Client - Agency Admin: Weekly Schedule Builder (assign which caregiver visits which client, on which days/times) - Agency Admin: Invite Family Member (generate invite link/code tied to a specific elder profile, with admin/viewer role selection) - Caregiver: My Schedule (today's and this week's assigned visits) - Caregiver: Visit Check-In → Active Visit (log medicine given, food/hydration, daily note) → Check-Out - Caregiver: Emergency/Escalate action (accessible from every caregiver screen) - Family: Elder Profile Overview (read view: medicines, emergency contacts, assigned doctor) - Family: Notification Feed (chronological: visits completed, notes, missed medicines, escalations) - Family: Emergency/Escalate action (accessible from every family screen) ### Core features (MVP scope) - Elder profile: basic info, medical conditions, emergency contacts, assigned doctor(s) - Medicine schedule: add medicines with times/dosage; caregiver marks as given; missed doses flagged - Weekly schedule: agency admin assigns caregiver-to-client visit slots; caregiver sees only their own assigned visits - Visit check-in / check-out: caregiver logs start/end of visit (timestamp + optional note), limited to their scheduled visits - Daily care notes: free-text note per visit, visible to family - Food & hydration tracking: simple logged entries per visit - Family notification feed: chronological feed of visit completions, notes, missed medicines, and escalation alerts (in-app; mock a "WhatsApp notification sent" state for MVP — don't build real WhatsApp API integration yet) - Role-based access: multiple family members can be invited (via invite link/code) to view one elder's profile, with admin/viewer role distinction - Escalation alert: caregiver or family can flag an urgent issue that immediately notifies the other party + agency admin; must be reachable in one tap from any screen in the caregiver and family views ### Auth & invite flow (must be explicit, not assumed) - Agency admin signs up first, creates the agency account - Agency admin adds caregivers by name/phone — system generates a login credential/PIN for each caregiver (no self-signup for caregivers in MVP) - Agency admin (or caregiver, depending on workflow) creates an elder profile, then generates a shareable invite link/code for family members - Family members join via the invite link, select their relationship to the elder, and land in the read-mostly family view; the first family member to join (or the one designated by the agency) gets "admin" role and can invite others as "viewers" ### Explicitly out of scope for MVP (Show as visible "Coming soon" placeholders in the UI — do not build functionality) - Doctor appointment scheduling - Document storage/upload - Expense tracking / UPI records - Diagnostic lab / pharmacy integrations - Offline caregiver mode - Real WhatsApp API / SMS integration - Payments/billing for agencies - Multi-agency switching (build for a single agency's admin view only) Populate the demo with mocked/sample data so it feels alive on first load: 1 sample agency, 4 caregivers, 3 elder clients, a week of visit history including at least one missed medicine and one escalation alert. ## 4. Example Context **Good output example:** Agency admin dashboard opens to a clean list of active elder clients, each showing a status chip ("Visit completed today" / "Medicine missed" / "No visit logged yet"), so problems are visible at a glance without clicking in. Caregiver check-in flow is 2 taps max (today's client → check in), because caregivers are field workers with low patience for UI friction. **Bad output example to avoid:** A generic dashboard template with unrelated widgets (sales charts, revenue graphs) bolted onto a care-management context. Also avoid burying the escalation/alert feature inside a settings menu — it should be one tap from anywhere, since this is the feature that matters most in a real emergency. Avoid letting caregivers see or check into visits that were not assigned to them. ## 5. Constraint Context - **Design tone:** Clinical-calm, closer to a hospital patient-portal than a consumer wellness app — generous white space, high-contrast text (readable by older family members), muted/trustworthy color palette (blues, greens, neutrals), no dark-mode-only styling, no playful/gamified visual elements. - **Roles:** Every screen must be clearly scoped to one of the three roles (agency admin / caregiver / family member); do not blend permissions or navigation between roles. - **Language:** UI copy in English for MVP, but structure text as translatable strings/labels (not hardcoded inline) so regional-language support can be added later without a rebuild. - **Data sensitivity:** Never display an elder's full medical history on a screen accessible without login. All family-facing screens should feel private and permissioned, even in this mocked MVP — don't design as if it's a public directory. - **No real integrations:** Do not attempt live WhatsApp, SMS, payment gateway, or lab/pharmacy API calls. Mock these clearly in the UI (e.g., a toast saying "Notification sent to family via WhatsApp"). - **Non-negotiable:** Include a persistent, one-tap "Emergency / Escalate" action visible to caregivers and family at all times — this is the product's core trust feature. - **Scale:** Build for a single agency's admin view first; don't build multi-tenant agency switching in MVP. ## 6. MVP success criteria (what this build should prove) The MVP is ready for user testing when a first-time user can, without instructions: 1. As agency admin: add a caregiver, add an elder client, assign the caregiver to that client, and see them appear on the schedule — in under 5 minutes. 2. As caregiver: log in, see today's assigned visit, check in, log a medicine given, add a note, and check out — in under 2 minutes. 3. As family member: join via an invite link and immediately see the elder's latest visit note and medicine status without confusion — in under 1 minute. 4. Trigger an escalation alert from the caregiver view and see it appear in the family notification feed in the same session.