html

# Build a Cockpit app (a local React page) A **local application**, not a one-off page: the preview injects a global `window.cockpit` SDK — essentially the Bash tool exposed to the page, so buttons can `curl`, read/write files and run scripts; data lands on disk inside the app directory and is there on reopen. Zero build: React / Babel load from the same-origin `/html-lib` — no bundler, no deps, works offline. ## 1. Flow: align first, write only after confirmation (important) **Don't write files up front.** Three steps: 1. **Align on the requirement** — restate your understanding of the app (what it does, where data comes from, key features/interactions). Ask back only when the requirement is ambiguous or has several reasonable readings; if it's already clear, just give a short summary — don't interrogate. 2. **Tell the storage directory** — resolve `<dir>/<name>/` and tell the user exactly where it goes and what it's called; they may reject or change it: - **You always pick `<name>`** from the request (lowercase kebab-case, matching `cockpit-name`) — the user only describes the app, they don't name it. - The user gave a directory → `<the given directory>/<name>/`; none given → `<name>/` under the **current chat working directory** (this session's cwd). - Every file of the app lives in that one directory, with data split into `cache/` `state/` `out/` per section 4. Don't scatter files elsewhere or invent a `.cockpit-apps`. 3. **Write o...