adapto-scaffoldlisted

# adapto:scaffold The **new-project** flow. It wraps `npx create-adapto-app` to stand up a fresh framework app already wired for Adapto. The read-client **ships with `create-adapto-app`**, so this skill doesn't add, vendor, or maintain any client of its own. ## When to use - Starting a brand-new site/app on Adapto: "create a new adapto project", "scaffold an adapto site", "new adapto app with Next/Astro/SvelteKit". - Routed here by `adapto:install` when the target is a new project. ## When not to use - Adding Adapto to an **existing** repo — out of scope in this variation (`create-adapto-app` is for new projects). - Just checking whether the environment is ready → `adapto:doctor`. ## Inputs - Project name / target directory — **ask**; if the user has no preference, default to `my-project` (or a short random name). - Framework: `next` | `astro` | `sveltekit`. - Package manager (optional): `npm` | `pnpm` | `yarn` | `bun`. - API key (optional) — **prefer not passing it on the command line** (see Forbidden actions); set it in `.env` after scaffolding instead. ## Outputs - A new project directory scaffolded for the chosen framework, including Adapto's read-client and a `.env` (`ADAPTO_API_URL` + `ADAPTO_API_KEY` to fill in). - The **`.adapto/` studio workspace** initialized in the project (empty brain dir, empty ledger, `.adapto/.gitignore`) — the agent's local source of truth ([studio.md](../../shared/studio.md)). - A clear next step: set the API key in `.env`, run `