OpenClaw

clawhub-lovable

Helps OpenClaw Clinical Hackathon participants get started quickly building clinical and healthcare apps with Lovable. Use when the user is building a clinical app in Lovable, mentions the hackathon or Lovable, or asks for quick-start guidance for clinical projects (patient intake, dashboards, assessments, PHI-safe patterns).

arunnadarasa0 来源安装数☆ 0 仓库 Stars

查看来源 ↗安装与使用 SKILL.md ↗

安装与使用

请根据来源仓库和你的 AI 工具说明安装此技能。先阅读技能文件和依赖要求，再添加到工作流。

SkillHub CLI

skillhub install arunnadarasa/lovable

打开来源仓库，查看说明和兼容环境后，按来源提供的命令或步骤安装。

将来源链接提供给你的 Agent，让它先读取说明、核对依赖，并向你说明将执行的安装步骤。

查看来源 ↗使用指南

技能说明

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)

Account and project
- Sign up at lovable.dev and create a new project.
- Name it clearly (e.g. “Patient Intake MVP”, “Clinical Dashboard”).
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).
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.
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.
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...

来源信息

Source: github
Repository: openclaw/skills
Path: skills/arunnadarasa/lovable
Version: —
Commit: ae832a455f3029fb7f3a7f0242e926f78888d2bd
分类来源: rules
状态: active
可见性: public

这些信息来自收录时的来源分析，可能滞后；使用前请核对最新来源文件。

来源内容

SKILL.md

# 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...

搜索