fusebase-clilisted

# Fusebase CLI (fusebase) This skill describes how to use the Fusebase CLI tool to manage and deploy Fusebase Apps apps. For environment migrations, pair this skill with the local project guides **App Environments Guide** and **App Environment Migration Guide**. When e2e tests are part of the work, also load skill **app-e2e-tests** and local guide **E2E Playwright Setup Guide**; when backend runtime env or Gate access is involved, also load **app-backend** and **fusebase-gate** as applicable. ## Overview The Fusebase CLI (`fusebase`) is a command-line tool for: - Initializing new Fusebase Apps projects - Managing app development with hot reload - Deploying apps to the Fusebase platform ## Installation & Authentication The `fusebase` CLI is installed globally. Always invoke it as `fusebase <command>` — **never use `npx fusebase`**. Before using the CLI, authenticate with your API key: ```bash fusebase auth ``` This stores credentials in `~/.fusebase/config.json`. ## Project Configuration (fusebase.json) Every Fusebase Apps project requires a `fusebase.json` file in the project root. This file defines the app and its apps. For details on the `fusebase.json` schema, see references/fusebase-json-schema.md. ### Declarative manifest — never invent an app `id` `apps[]` is **declarative**: an app entry carries `subdomain` + `name` and **omits the platform app `id`**. `fusebase deploy` reconciles each entry against the platform — it binds to the app with a matching `sub