clawhub-lovable

# ClawHub × Lovable — Clinical Hackathon Quick Start

Use this skill when helping participants of the **OpenClaw Clinical Hackathon** build **clinical or healthcare projects** with **Lovable** (full-stack AI app platform). Goal: get from idea to a working clinical MVP fast, with sensible patterns for auth, data, and scope.

## When to apply

- User mentions **OpenClaw Clinical Hackathon**, **Lovable**, or **clinical project**
- User wants to build a **clinical/healthcare app** (intake forms, dashboards, assessments, vitals, etc.)
- User asks for **quick start** or **getting started** with Lovable for clinical use cases

## Quick start (first clinical project in Lovable)

1. **Account and project**
   - Sign up at [lovable.dev](https://lovable.dev) and create a new project.
   - Name it clearly (e.g. “Patient Intake MVP”, “Clinical Dashboard”).

2. **Scope with Plan mode**
   - In Lovable, use **Plan mode** first: describe the clinical goal (e.g. “Patient intake form with consent and basic demographics, then a simple list view”).
   - Get a high-level plan and break the app into **components** (e.g. intake form, list, detail view).

3. **Build by component**
   - Use **Agent mode** to implement one component at a time.
   - Prompt for **that component** (e.g. “Add a patient intake form with fields: name, DOB, consent checkbox, submit”) instead of “build the whole app”.
   - Add **authentication early** if the app will show any user-specific or sensitive data.

4. **Backend and data**
   - Use **Lovable Cloud** (Supabase) for database and auth so you don’t manage servers.
   - Prefer **structured fields** (e.g. demographics, assessments) in the DB from the start; avoid free-text blobs for anything that might be PHI.

5. **Publish**
   - Use Lovable’s deploy/publish flow when the MVP is ready; add a **custom domain** later if needed.

## Clinical project patterns

- **Auth from day one**  
  If the app touches patient or user-specific data, add auth (e.g. Supabase Auth...