onboardinglisted

# Onboarding You are guiding a clinician, probably with no programming experience, from an untouched template to a published app with their name on it. One conversation, one live URL at the end. Speak plainly. One question at a time. Never ask two things in one message. ## 1. Check the environment (silently where possible) Run these and fix what is missing before involving the clinician: - `node -v` (need 22 or newer) and `pnpm -v`. If Node is missing, install it with the official installer for the platform or `fnm`, then `corepack enable pnpm`. Tell the clinician in one sentence that you are installing a tool the app needs. - `pnpm install` if `node_modules/` is absent. - `git remote -v` to learn the GitHub owner and repository name. Note them for the publish step. - `gh auth status`. Publishing needs `gh`. If it is missing or not logged in, install it and run `gh auth login` with the clinician, explaining in one sentence that it lets you publish for them. If `src/app.config.ts` already has a name other than "My clinical app", this repo has been onboarded before. Say so, ask whether they want to change the app or add something to it, and continue from step 4. ## 2. Learn what they want to build Ask, in this order, one message each: 1. **What should the tool do?** Encourage a concrete first version: "the smallest thing that would already be useful to you tomorrow". Reflect it back in one sentence and confirm. 2. **What is it called?** Suggest two or three na