@vibecodemax/cli 0.1.1 → 0.1.3

package/README.md

@@ -1,156 +1,102 @@
 # @vibecodemax/cli
 
-Local VibeCodeMax CLI for bootstrap and future project operations.
+CLI for VibeCodeMax projects. Runs bootstrap provider configuration locally from your project root — credentials never leave your machine.
 
-This package is intended to run on the user's machine from the project root. It reads local environment files such as `.env.local` and `.env.bootstrap.local`, performs provider configuration locally, and prints JSON-only results to stdout.
+## What it does
 
-## Principles
+During bootstrap, the MCP orchestrates your project setup step by step. When a step requires provider configuration (setting up auth, applying API settings, enabling integrations), this CLI handles the actual provider calls locally using credentials stored in your env files.
 
-- Secrets stay local to the user's machine
-- No secret values are passed through MCP payloads
-- No secret values are printed to stdout
-- Commands return structured JSON only
-- Exit code `0` means success; non-zero means failure
+You don't run this CLI manually in most cases — the MCP tells your coding agent which command to execute and the agent runs it from your project root.
 
 ## Requirements
 
 - Node.js 20+
-- npm, pnpm, or yarn
+- A VibeCodeMax project with `.env.local` and/or `.env.bootstrap.local` configured
 
-## Development
-
-Install dependencies:
+## Usage
 
 ```bash
-npm install
+npx @vibecodemax/cli <command> [options]
 ```
 
-Build the CLI:
+Package manager variants:
 
 ```bash
-npm run build
+pnpm dlx @vibecodemax/cli <command> [options]
+yarn dlx @vibecodemax/cli <command> [options]
 ```
 
-Type-check without emitting files:
+## Commands
 
-```bash
-npm run typecheck
-```
+### `read-setup-state`
 
-Run the built CLI help command:
+Reads `.vibecodemax/setup-state.json` from the current project and prints a JSON `setupState` object for bootstrap prerequisite hydration.
 
 ```bash
-node dist/cli.js help
+npx @vibecodemax/cli read-setup-state
 ```
 
-## Local Execution
+### `admin ensure-admin`
 
-Use an exact package version when invoking the published package.
-
-npm:
+Ensures the target user exists in Supabase Auth and has the `admin` role in the default `profiles` table.
 
 ```bash
-npx @vibecodemax/cli@0.1.0 help
+npx @vibecodemax/cli admin ensure-admin --email admin@example.com
 ```
 
-pnpm:
-
-```bash
-pnpm dlx @vibecodemax/cli@0.1.0 help
-```
+This command reads `SUPABASE_SERVICE_ROLE_KEY` and `SUPABASE_URL` or `NEXT_PUBLIC_SUPABASE_URL` from local env files, performs lookup/create/promote/verify locally, and prints JSON only.
 
-yarn:
-
-```bash
-yarn dlx @vibecodemax/cli@0.1.0 help
-```
-
-## Commands
+If a new user is created, the CLI output includes `temporaryPassword`. Show that password to the user directly and do not forward it into MCP payloads.
 
 ### `configure-site-redirects`
 
-Configures Supabase auth site URL and redirect allow-list for test or production mode.
-
-Example:
-
-```bash
-node dist/cli.js configure-site-redirects --mode test
-```
-
-Production example:
+Configures site URL and redirect allow-list for the project's auth provider.
 
 ```bash
-node dist/cli.js configure-site-redirects --mode production --production-domain https://yourdomain.com
+npx @vibecodemax/cli configure-site-redirects --mode test
+npx @vibecodemax/cli configure-site-redirects --mode production --production-domain https://yourdomain.com
 ```
 
 ### `configure-email-password`
 
-Configures email/password signup behavior in Supabase.
-
-Example:
+Configures email/password signup behavior.
 
 ```bash
-node dist/cli.js configure-email-password --email-confirmation yes
+npx @vibecodemax/cli configure-email-password --email-confirmation yes
 ```
 
 ### `enable-google-provider`
 
-Enables Google auth in Supabase using local credentials from `.env.bootstrap.local`.
-
-Example:
+Enables Google OAuth using credentials from `.env.bootstrap.local`. The Supabase personal access token must be stored as `SUPABASE_ACCESS_TOKEN`.
 
 ```bash
-node dist/cli.js enable-google-provider
+npx @vibecodemax/cli enable-google-provider
 ```
 
 ### `apply-auth-templates`
 
-Applies custom auth email template content from local project files.
-
-Example:
+Applies custom auth email templates from local project files. The Supabase personal access token must be stored as `SUPABASE_ACCESS_TOKEN`.
 
 ```bash
-node dist/cli.js apply-auth-templates \
+npx @vibecodemax/cli apply-auth-templates \
   --confirm-email-enabled true \
   --confirm-email-path src/email/confirm-email.html \
   --reset-password-enabled true \
   --reset-password-path src/email/reset-password.html
 ```
 
-## Output Contract
+## Output
 
-Success example:
+All commands print structured JSON to stdout and exit with code 0 on success, non-zero on failure.
 
 ```json
-{
-  "ok": true,
-  "command": "configure-site-redirects",
-  "applied": ["site_url", "uri_allow_list", "NEXT_PUBLIC_SITE_URL"]
-}
+{ "ok": true, "command": "configure-site-redirects", "applied": ["site_url", "uri_allow_list"] }
 ```
 
-Failure example:
-
 ```json
-{
-  "ok": false,
-  "code": "MISSING_ENV",
-  "message": "SUPABASE_MANAGEMENT_TOKEN is missing. Add it to .env.bootstrap.local."
-}
+{ "ok": false, "code": "MISSING_ENV", "message": "SUPABASE_ACCESS_TOKEN is missing. Add it to .env.bootstrap.local." }
 ```
 
-Error output must reference file names and environment variable names, not secret values.
-
-## Publishing
+## Security
 
-Verify the package contents:
-
-```bash
-npm pack --dry-run
-```
-
-Publish publicly:
-
-```bash
-npm publish --access public
-```
+Credentials are read from local env files and sent only to the relevant provider APIs. No secret values appear in CLI output.