@vaiftech/cli 1.9.9 → 1.10.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) (v1.9.7) — scaffold full projects from templates with feature selection, browser-based authentication, manage schemas, deploy functions, generate TypeScript types, and more.
+Command-line tools for [VAIF Studio](https://vaif.studio) (v1.10.0) — scaffold full projects from templates with feature selection, browser-based authentication, manage schemas, deploy functions, generate TypeScript types, migrate from Supabase/Firebase, and more.
 
 ## Installation
 
@@ -25,6 +25,12 @@ vaif init --template nextjs-fullstack
 # Scaffold with specific features
 vaif init --template react-spa --features auth,realtime,storage
 
+# Migrate from another platform
+vaif migrate --from supabase --dry-run
+
+# Generate CLAUDE.md for AI assistants
+vaif init --claude
+
 # Pull your database schema and generate types
 vaif pull
 vaif generate
@@ -158,6 +164,8 @@ vaif init --template react-spa       # Scaffold from template
 vaif init --template nextjs-fullstack --features auth,storage
 vaif init --typescript               # Setup for TypeScript
 vaif init --force                    # Overwrite existing config
+vaif init --claude                   # Auto-detect project type + generate CLAUDE.md from live data
+vaif init --claude saas              # Generate CLAUDE.md from static template (base|saas|mobile|ecommerce)
 ```
 
 ### Add Features to Existing Project
@@ -256,6 +264,54 @@ export default async function handler(req, ctx) {
 }
 ```
 
+### Migration from Other Platforms
+
+Migrate your project from Supabase or Firebase to VAIF Studio. The CLI analyzes your local project files, builds a migration plan, and optionally executes it via the VAIF API.
+
+```bash
+vaif migrate --from supabase         # Analyze Supabase project + show migration plan
+vaif migrate --from firebase         # Analyze Firebase project + show migration plan
+vaif migrate --from supabase --dry-run  # Preview plan without executing
+vaif migrate --from firebase -p <id> # Specify target VAIF project
+vaif migrate --from supabase -o ./my-supabase-app  # Analyze a different directory
+```
+
+**Supabase migration reads:**
+- `supabase/migrations/*.sql` — Table schemas, indexes, RLS policies
+- `supabase/config.toml` — Project configuration
+- `supabase/.temp/project-ref` — Project reference
+- `supabase/functions/` — Edge functions
+
+**Firebase migration reads:**
+- `firebase.json` — Hosting, functions, Firestore, storage config
+- `.firebaserc` — Project aliases
+- `firestore.rules` — Security rules (translated to RLS policies)
+- `functions/src/index.ts` — Cloud functions
+
+The migration plan shows tables, storage buckets, functions, and notes. In dry-run mode, it also saves the plan to `migration-plan.md`. When executed, it creates tables, buckets, and function stubs via the VAIF API.
+
+### CLAUDE.md Generation
+
+Generate a `CLAUDE.md` file for AI assistants to understand your project:
+
+```bash
+vaif init --claude                   # Auto-detect project type, generate from live project data
+vaif init --claude base              # Static template: universal project
+vaif init --claude saas              # Static template: SaaS with billing, teams, multi-tenancy
+vaif init --claude mobile            # Static template: mobile app (React Native, Expo, Flutter)
+vaif init --claude ecommerce         # Static template: e-commerce with products, orders, Stripe
+```
+
+**Auto-detection** examines `package.json` dependencies and directory structure to determine project type (mobile, ecommerce, saas, or base) and generates a tailored CLAUDE.md with live project data.
+
+**Convention import**: When using a static template, the CLI automatically imports team conventions from existing AI config files (`.cursorrules`, `.github/copilot-instructions.md`, `.windsurfrules`, `.clinerules`) and appends them to the generated CLAUDE.md.
+
+For a fully personalized CLAUDE.md from your live project data (database schema, API keys, etc.), use:
+
+```bash
+vaif claude-setup
+```
+
 ### Claude Code Integration
 
 Set up [Claude Code](https://claude.ai/claude-code) to work with your VAIF project. This generates a `.mcp.json` (MCP server config) and a `CLAUDE.md` (project context with your full database schema, SDK examples, and API reference).