@vaiftech/cli 1.3.2 → 1.5.0

package/README.md

@@ -3,7 +3,7 @@
 [![npm version](https://img.shields.io/npm/v/@vaiftech/cli)](https://www.npmjs.com/package/@vaiftech/cli)
 [![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](https://opensource.org/licenses/MIT)
 
-Command-line tools for [VAIF Studio](https://vaif.studio) — scaffold full projects from templates, manage schemas, deploy functions, generate TypeScript types, and more.
+Command-line tools for [VAIF Studio](https://vaif.studio) — scaffold full projects from templates with feature selection, browser-based authentication, manage schemas, deploy functions, generate TypeScript types, and more.
 
 ## Installation
 
@@ -114,28 +114,29 @@ vaif init --template nextjs-fullstack
 | `storage` | File upload/download, signed URL helpers |
 | `functions` | Serverless function invocation utilities |
 
-Each template has sensible defaults (e.g. `nextjs-fullstack` defaults to `database` + `auth`), but you can customize freely. Feature-specific files are only generated when the feature is selected — for example, selecting `auth` adds login/signup pages, selecting `storage` adds upload hooks.
+Each template has sensible defaults (e.g. `nextjs-fullstack` defaults to `database` + `auth`), but you can customize freely. Feature-specific files are only generated when the feature is selected — for example, selecting `auth` adds login/signup pages and the `@vaiftech/auth` dependency, selecting `storage` adds upload hooks.
+
+If a `package.json` already exists in your directory, the CLI merges the template's dependencies into it instead of overwriting it.
 
 ### What Templates Generate
 
-Templates generate **complete project scaffolding**, not just config files:
+Templates generate **complete project scaffolding** with everything you need to start building:
 
-**JavaScript/TypeScript templates** (nextjs-fullstack, react-spa, etc.):
-- `package.json` — with all VAIF SDK dependencies pre-configured
-- `tsconfig.json` — TypeScript configuration
+**Every template includes:**
+- `README.md` — Step-by-step setup guide (credentials, login, migrations, functions, running)
+- `package.json` (or equivalent) — All dependencies pre-configured
 - `vaif.config.json` — VAIF project configuration
-- `src/lib/vaif.ts` — Client initialization
 - `.env.example` — Environment variables template
-- `app/` or `src/` — Full app structure (layout, pages, components)
-- Feature-conditional files (auth pages, storage hooks, realtime hooks)
-- Prints next steps after scaffolding
-
-**Native/Backend templates** (ios-swift-app, flutter-app, python-fastapi-backend, go-backend-api):
-- `vaif.config.json` — Project configuration
-- Platform-specific project files (Package.swift, pubspec.yaml, requirements.txt, go.mod)
 - Client initialization and integration files
-- `.env.example` — Environment variables
-- Setup instructions
+
+**With features selected, templates also include:**
+- **database**: Drizzle migration (`drizzle/0001_initial.sql`), schema file, and config
+- **auth**: Login/signup pages, auth guard component
+- **realtime**: Subscription hooks with live data
+- **storage**: File upload/download hooks
+- **functions**: Example serverless function (`functions/hello.ts`) ready to deploy
+
+**Native/Backend templates** include platform-specific equivalents (Python models, Go structs, Dart classes, Swift managers).
 
 ## Commands