@donotdev/cli 0.0.13 → 0.0.15

package/templates/overlay-firebase/src/config/providers.expo.ts.example

@@ -0,0 +1,49 @@
+// src/config/providers.ts — Firebase provider bootstrap (Expo)
+// Auto-generated by DoNotDev scaffolding. Edit freely.
+// Import from root layout (app/_layout.tsx): import '../src/config/providers';
+
+import { initializeApp } from 'firebase/app';
+
+import { configureProviders } from '@donotdev/core';
+import {
+  FirestoreAdapter,
+  FirebaseAuth,
+  FirebaseStorageAdapter,
+} from '@donotdev/firebase';
+import { initializeExpoAuth } from '@donotdev/expo';
+
+const apiKey = process.env.EXPO_PUBLIC_FIREBASE_API_KEY;
+const projectId = process.env.EXPO_PUBLIC_FIREBASE_PROJECT_ID;
+
+if (!apiKey || !projectId) {
+  throw new Error(
+    '[dndev] Missing Firebase env vars (EXPO_PUBLIC_FIREBASE_API_KEY, EXPO_PUBLIC_FIREBASE_PROJECT_ID). ' +
+    'Copy .env.example to .env and fill in your Firebase config.'
+  );
+}
+
+const firebaseConfig = {
+  apiKey,
+  projectId,
+  authDomain: process.env.EXPO_PUBLIC_FIREBASE_AUTH_DOMAIN,
+  storageBucket: process.env.EXPO_PUBLIC_FIREBASE_STORAGE_BUCKET,
+  messagingSenderId: process.env.EXPO_PUBLIC_FIREBASE_MESSAGING_SENDER_ID,
+  appId: process.env.EXPO_PUBLIC_FIREBASE_APP_ID,
+};
+
+initializeApp(firebaseConfig);
+// Must run before FirebaseAuth — sets up AsyncStorage persistence
+initializeExpoAuth();
+
+/**
+ * Register Firebase as the backend provider.
+ * Must run before any CRUD/auth/storage operations.
+ *
+ * Uses EXPO_PUBLIC_FIREBASE_* env vars (not VITE_*).
+ * initializeExpoAuth() sets up AsyncStorage persistence before FirebaseAuth.
+ */
+configureProviders({
+  crud: new FirestoreAdapter(),
+  auth: new FirebaseAuth(),
+  storage: new FirebaseStorageAdapter(),
+});

package/templates/overlay-firebase/src/config/providers.ts.example

@@ -0,0 +1,23 @@
+// src/config/providers.ts — Firebase provider bootstrap
+// Auto-generated by DoNotDev scaffolding. Edit freely.
+// Import from root component (App.tsx): import './config/providers';
+
+import { configureProviders } from '@donotdev/core';
+import {
+  FirestoreAdapter,
+  FirebaseAuth,
+  FirebaseStorageAdapter,
+} from '@donotdev/firebase';
+
+/**
+ * Register Firebase as the backend provider.
+ * Must run before any CRUD/auth/storage operations.
+ *
+ * Firebase SDK is auto-initialized by the framework's Vite plugin
+ * from VITE_FIREBASE_* env vars — no `initializeApp()` needed here.
+ */
+configureProviders({
+  crud: new FirestoreAdapter(),
+  auth: new FirebaseAuth(),
+  storage: new FirebaseStorageAdapter(),
+});

package/templates/overlay-supabase/env.fragment.example

@@ -0,0 +1,7 @@
+
+# =============================================================================
+# Supabase Configuration
+# =============================================================================
+# Get these values from your Supabase project settings > API
+VITE_SUPABASE_URL=
+VITE_SUPABASE_ANON_KEY=

package/templates/overlay-supabase/env.fragment.expo.example

@@ -0,0 +1,7 @@
+
+# =============================================================================
+# Supabase Configuration
+# =============================================================================
+# Get these values from your Supabase project settings > API
+EXPO_PUBLIC_SUPABASE_URL=
+EXPO_PUBLIC_SUPABASE_ANON_KEY=

package/templates/overlay-supabase/env.fragment.nextjs.example

@@ -0,0 +1,7 @@
+
+# =============================================================================
+# Supabase Configuration
+# =============================================================================
+# Get these values from your Supabase project settings > API
+NEXT_PUBLIC_SUPABASE_URL=
+NEXT_PUBLIC_SUPABASE_ANON_KEY=

package/templates/overlay-supabase/src/config/providers.expo.ts.example

@@ -0,0 +1,35 @@
+// src/config/providers.ts — Supabase provider bootstrap (Expo)
+// Auto-generated by DoNotDev scaffolding. Edit freely.
+// Import from root layout (app/_layout.tsx): import '../src/config/providers';
+
+import { createClient } from '@supabase/supabase-js';
+
+import { configureProviders } from '@donotdev/core';
+import {
+  SupabaseAuth,
+  SupabaseCrudAdapter,
+  SupabaseStorageAdapter,
+} from '@donotdev/supabase';
+
+const url = process.env.EXPO_PUBLIC_SUPABASE_URL;
+const publicKey = process.env.EXPO_PUBLIC_SUPABASE_PUBLIC_KEY || process.env.EXPO_PUBLIC_SUPABASE_ANON_KEY; // New: sb_publishable_..., Legacy: anon key
+
+if (!url || !publicKey) {
+  console.warn(
+    '[dndev] Supabase not configured. Set EXPO_PUBLIC_SUPABASE_URL and EXPO_PUBLIC_SUPABASE_ANON_KEY in .env'
+  );
+} else {
+  const supabase = createClient(url, publicKey);
+
+  /**
+   * Register Supabase as the backend provider.
+   * Must run before any CRUD/auth/storage operations.
+   *
+   * Uses EXPO_PUBLIC_SUPABASE_* env vars (not VITE_*).
+   */
+  configureProviders({
+    crud: new SupabaseCrudAdapter(supabase),
+    auth: new SupabaseAuth(supabase),
+    storage: new SupabaseStorageAdapter(supabase),
+  });
+}

package/templates/overlay-supabase/src/config/providers.ts.example

@@ -0,0 +1,33 @@
+// src/config/providers.ts — Supabase provider bootstrap
+// Auto-generated by DoNotDev scaffolding. Edit freely.
+// Import from root component (App.tsx): import './config/providers';
+
+import { createClient } from '@supabase/supabase-js';
+
+import { configureProviders } from '@donotdev/core';
+import {
+  SupabaseAuth,
+  SupabaseCrudAdapter,
+  SupabaseStorageAdapter,
+} from '@donotdev/supabase';
+
+const url = import.meta.env.VITE_SUPABASE_URL;
+const publicKey = import.meta.env.VITE_SUPABASE_PUBLIC_KEY || import.meta.env.VITE_SUPABASE_ANON_KEY; // New: sb_publishable_..., Legacy: anon key
+
+if (!url || !publicKey) {
+  console.warn(
+    '[dndev] Supabase not configured. Set VITE_SUPABASE_URL and VITE_SUPABASE_PUBLIC_KEY (or VITE_SUPABASE_ANON_KEY) in .env'
+  );
+} else {
+  const supabase = createClient(url, publicKey);
+
+  /**
+   * Register Supabase as the backend provider.
+   * Must run before any CRUD/auth/storage operations.
+   */
+  configureProviders({
+    crud: new SupabaseCrudAdapter(supabase),
+    auth: new SupabaseAuth(supabase),
+    storage: new SupabaseStorageAdapter(supabase),
+  });
+}

package/templates/overlay-supabase/vercel.headers.example

@@ -0,0 +1,23 @@
+[
+  {
+    "source": "/(.*)",
+    "headers": [
+      {
+        "key": "Content-Security-Policy",
+        "value": "default-src 'self'; script-src 'self' https://js.stripe.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; img-src 'self' data: blob: https:; font-src 'self' data: https://fonts.gstatic.com; connect-src 'self' https://*.supabase.co wss://*.supabase.co https://api.stripe.com; frame-src 'none' https://js.stripe.com https://hooks.stripe.com; object-src 'none'; base-uri 'self'; form-action 'self'"
+      },
+      {
+        "key": "X-Content-Type-Options",
+        "value": "nosniff"
+      },
+      {
+        "key": "X-Frame-Options",
+        "value": "DENY"
+      },
+      {
+        "key": "Referrer-Policy",
+        "value": "strict-origin-when-cross-origin"
+      }
+    ]
+  }
+]

package/templates/overlay-supabase/vercel.json.example

@@ -0,0 +1,22 @@
+{
+  "buildCommand": "bun run build",
+  "outputDirectory": "dist",
+  "installCommand": "bun install",
+  "rewrites": [
+    { "source": "/(.*)", "destination": "/index.html" }
+  ],
+  "headers": [
+    {
+      "source": "/(.*)",
+      "headers": [
+        {
+          "key": "Content-Security-Policy",
+          "value": "default-src 'self'; script-src 'self' https://js.stripe.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; img-src 'self' data: blob: https:; font-src 'self' data: https://fonts.gstatic.com; connect-src 'self' https://*.supabase.co wss://*.supabase.co https://api.stripe.com; frame-src 'none' https://js.stripe.com https://hooks.stripe.com; object-src 'none'; base-uri 'self'; form-action 'self'"
+        },
+        { "key": "X-Content-Type-Options", "value": "nosniff" },
+        { "key": "X-Frame-Options", "value": "DENY" },
+        { "key": "Referrer-Policy", "value": "strict-origin-when-cross-origin" }
+      ]
+    }
+  ]
+}

package/templates/overlay-vercel/env.fragment.example

@@ -0,0 +1,34 @@
+
+# =============================================================================
+# Firebase Configuration (data layer for Vercel-hosted app)
+# =============================================================================
+# Get these values from your Firebase project settings
+# Run `dndev firebase:setup` to auto-populate, or copy from Firebase Console
+VITE_FIREBASE_API_KEY=
+VITE_FIREBASE_PROJECT_ID=
+# Copy from Firebase Console. Framework uses APP_URL hostname in production automatically.
+VITE_FIREBASE_AUTH_DOMAIN=
+VITE_FIREBASE_STORAGE_BUCKET=
+VITE_FIREBASE_MESSAGING_SENDER_ID=
+VITE_FIREBASE_APP_ID=
+VITE_FIREBASE_MEASUREMENT_ID=
+VITE_FIREBASE_FUNCTIONS_REGION=
+
+# =============================================================================
+# Firebase Emulator (Development only)
+# =============================================================================
+# Set to true to use Firebase emulators instead of production services
+VITE_USE_FIREBASE_EMULATOR=false
+VITE_FIREBASE_EMULATOR_HOST=localhost
+VITE_FIREBASE_EMULATOR_PORT=9099
+VITE_FIREBASE_AUTH_EMULATOR_HOST=http://localhost:9099
+VITE_FIREBASE_FIRESTORE_EMULATOR_HOST=localhost:8080
+VITE_FIREBASE_FUNCTIONS_EMULATOR_PORT=5001
+
+# =============================================================================
+# Firebase App Check (Abuse Protection)
+# =============================================================================
+# reCAPTCHA v3 site key for App Check
+# VITE_RECAPTCHA_SITE_KEY=6LcXXXX...
+# Optional: Debug token for localhost testing
+# VITE_APPCHECK_DEBUG_TOKEN=XXXX-XXXX-XXXX

package/templates/overlay-vercel/env.fragment.nextjs.example

@@ -0,0 +1,34 @@
+
+# =============================================================================
+# Firebase Configuration (data layer for Vercel-hosted app)
+# =============================================================================
+# Get these values from your Firebase project settings
+# Run `dndev firebase:setup` to auto-populate, or copy from Firebase Console
+NEXT_PUBLIC_FIREBASE_API_KEY=
+NEXT_PUBLIC_FIREBASE_PROJECT_ID=
+# Copy from Firebase Console. Framework uses APP_URL hostname in production automatically.
+NEXT_PUBLIC_FIREBASE_AUTH_DOMAIN=
+NEXT_PUBLIC_FIREBASE_STORAGE_BUCKET=
+NEXT_PUBLIC_FIREBASE_MESSAGING_SENDER_ID=
+NEXT_PUBLIC_FIREBASE_APP_ID=
+NEXT_PUBLIC_FIREBASE_MEASUREMENT_ID=
+NEXT_PUBLIC_FIREBASE_FUNCTIONS_REGION=
+
+# =============================================================================
+# Firebase Emulator (Development only)
+# =============================================================================
+# Set to true to use Firebase emulators instead of production services
+NEXT_PUBLIC_USE_FIREBASE_EMULATOR=false
+NEXT_PUBLIC_FIREBASE_EMULATOR_HOST=localhost
+NEXT_PUBLIC_FIREBASE_EMULATOR_PORT=9099
+NEXT_PUBLIC_FIREBASE_AUTH_EMULATOR_HOST=http://localhost:9099
+NEXT_PUBLIC_FIREBASE_FIRESTORE_EMULATOR_HOST=localhost:8080
+NEXT_PUBLIC_FIREBASE_FUNCTIONS_EMULATOR_PORT=5001
+
+# =============================================================================
+# Firebase App Check (Abuse Protection)
+# =============================================================================
+# reCAPTCHA v3 site key for App Check
+# NEXT_PUBLIC_RECAPTCHA_SITE_KEY=6LcXXXX...
+# Optional: Debug token for localhost testing
+# NEXT_PUBLIC_APPCHECK_DEBUG_TOKEN=XXXX-XXXX-XXXX

package/templates/overlay-vercel/src/config/providers.ts.example

@@ -0,0 +1,24 @@
+// src/config/providers.ts — Vercel + Firebase provider bootstrap
+// Auto-generated by DoNotDev scaffolding. Edit freely.
+// Import from root component (App.tsx): import './config/providers';
+
+import { configureProviders } from '@donotdev/core';
+import {
+  FirestoreAdapter,
+  FirebaseAuth,
+  FirebaseStorageAdapter,
+} from '@donotdev/firebase';
+
+/**
+ * Register Firebase as the data provider for a Vercel-hosted app.
+ * Vercel handles hosting + API routes; Firebase provides CRUD/auth/storage.
+ * Must run before any CRUD/auth/storage operations.
+ *
+ * Firebase SDK is auto-initialized by the framework's Vite plugin
+ * from VITE_FIREBASE_* env vars — no `initializeApp()` needed here.
+ */
+configureProviders({
+  crud: new FirestoreAdapter(),
+  auth: new FirebaseAuth(),
+  storage: new FirebaseStorageAdapter(),
+});

package/templates/root-consumer/.claude/agents/architect.md.example

@@ -1,313 +1,5 @@
 ---
-description: BMAD PRINTER persona - Transform HLD into technical specifications (Step 2: Review/Design)
+description: BMAD PRINTER — Transform HLD into technical specifications
 ---
 
-<persona>
-You are PRINTER — a Framework Architect who transforms HLD documents into technical specifications.
-
-Your personality:
-- PRECISE: You generate exact code, not descriptions
-- FRAMEWORK-NATIVE: You know DoNotDev inside-out and map everything to it
-- VIGILANT: You catch inconsistencies and flag them
-- MINIMAL: You include only what's in the HLD
-
-You focus on:
-- Generating schemas and configuration code, not implementing app features
-- Including only features specified in the HLD
-- Flagging every issue you find for human review
-- Letting code speak for itself, keeping explanations concise
-</persona>
-
-<mission>
-Transform the HLD into technical artifacts (LLD - Low-Level Design):
-1. Entity Schemas — defineEntity() code for each entity
-2. Navigation Config — route definitions
-3. Feature Mapping — what framework packages implement what
-4. Custom Component Specs — detailed specs for custom components (if any)
-
-You succeed when artifacts are complete and valid.
-You fail if you generate invalid code or miss HLD items.
-</mission>
-
-<input_context>
-You are receiving an HLD document from Step 1 (Brainstorm) or `/brainstorm` command.
-The HLD contains: Vision, Users, Entities, Features, Pages, Constraints, Native vs Custom.
-Your job is to translate this into DoNotDev framework code and implementation plan.
-</input_context>
-
-<framework_knowledge>
-DoNotDev Entity System:
-
-```typescript
-import { defineEntity } from '@donotdev/core';
-
-export const exampleEntity = defineEntity({
-  name: 'Example',           // Display name
-  collection: 'examples',    // Firestore collection (plural, lowercase)
-  fields: {
-    fieldName: {
-      type: 'text',          // Field type
-      visibility: 'user',    // guest | user | admin | technical | hidden
-      validation: {          // Optional
-        required: true,
-        minLength: 3
-      }
-    }
-  }
-});
-```
-
-Field Types:
-text, email, number, textarea, select, date, checkbox, dropdown,
-multiDropdown, file, image, radio, range, phone, geopoint, map,
-timestamp, reference, password, address, avatar, hidden
-
-Technical Fields (auto-added by defineEntity, no need to add manually):
-- id, createdAt, updatedAt, createdById, updatedById
-- All have visibility: 'technical' (shown as read-only in edit forms, hidden in create forms)
-
-Reference Format:
-- type: 'reference'
-- ref: 'collectionName' (the target collection, plural lowercase)
-
-Select Format:
-- type: 'select'
-- options: ['option1', 'option2']
-
-Validation Options:
-- required: boolean
-- minLength / maxLength: number
-- min / max: number
-- nullable: boolean
-</framework_knowledge>
-
-<framework_packages>
-Available packages for feature mapping:
-
-| Package | Purpose |
-|---------|---------|
-| @donotdev/core | defineEntity, utilities |
-| @donotdev/features/auth | Email/password auth, AuthForm |
-| @donotdev/features/oauth | OAuth providers (Google, GitHub) |
-| @donotdev/crud | useCrud hook, EntityFormRenderer, EntityList |
-| @donotdev/features/billing | Stripe integration |
-| @donotdev/components | UI: Section, Card, Hero, Button, etc. |
-| @donotdev/ui | Layouts, navigation, theme |
-</framework_packages>
-
-<mcp_usage>
-Before generating code, use MCP to verify component capabilities:
-
-1. For each component mentioned in HLD:
-   - Call `lookup_symbol({ symbol: "ComponentName" })`
-   - Verify props match requirements
-   - Document any limitations
-
-2. For custom components identified in HLD:
-   - Use `search_framework` to check if similar component exists
-   - If not, create detailed spec for custom component
-
-3. Document MCP findings in "Custom Component Specs" section
-</mcp_usage>
-
-<output_format>
-Generate EXACTLY this structure:
-
----
-
-## 1. Entity Schemas
-
-### entities/[name].ts
-
-```typescript
-import { defineEntity } from '@donotdev/core';
-
-export const [name]Entity = defineEntity({
-  name: '[Name]',
-  collection: '[names]',
-  fields: {
-    // Technical fields (id, createdAt, updatedAt, createdById, updatedById)
-    // are automatically added by defineEntity - no need to add them manually
-    // ... all fields from HLD
-  }
-});
-```
-
-(Generate one block per entity)
-
-### entities/index.ts
-
-```typescript
-export { [name]Entity } from './[name]';
-// ... export all
-```
-
----
-
-## 2. Navigation Config
-
-```typescript
-export const routes = [
-  {
-    path: '/path',
-    name: 'PageName',
-    access: 'public' | 'protected' | 'admin',
-    layout: 'marketing' | 'app' | 'auth' | 'admin',
-    components: ['ComponentName']
-  }
-];
-```
-
----
-
-## 3. Feature Mapping
-
-| HLD Feature | Implementation | Package |
-|-------------|----------------|---------|
-| [Feature from HLD] | [How to implement] | [@donotdev/...] |
-
----
-
-## 4. Custom Component Specs
-
-For each custom component identified in HLD "Native vs Custom" section:
-
-### [ComponentName]
-
-**Purpose:** [What it does]
-
-**Props:**
-```typescript
-interface [ComponentName]Props {
-  // ... props definition
-}
-```
-
-**Behavior:** [How it works]
-
-**Integration:** [How it integrates with framework]
-
-**Implementation Notes:** [Any special considerations]
-
----
-
-## 5. Implementation Plan
-
-**Order of Implementation:**
-1. Entities (create all entity files)
-2. Native Pages (using framework defaults)
-3. Custom Components (create custom components)
-4. Integration (wire everything together)
-
-**Dependencies:**
-- [What depends on what]
-
----
-
-## 6. Validation Issues
-
-List ANY problems found:
-- ⚠️ [Issue description]
-
-If no issues: ✅ All valid
-</output_format>
-
-<validation_checks>
-Before outputting, verify:
-□ Every HLD entity has a schema
-□ Technical fields (id, createdAt, etc.) are NOT manually added (auto-added by defineEntity)
-□ Every reference field has valid ref pointing to existing collection
-□ Every select field has options array
-□ Every HLD page has a route
-□ Every HLD feature is mapped to a package
-□ Collection names are plural lowercase
-□ Visibility levels are: guest | user | admin | technical | hidden
-□ All custom components have detailed specs
-□ Implementation order is clear
-
-Flag violations in "Validation Issues" section.
-</validation_checks>
-
-<examples>
-GOOD OUTPUT (partial):
-
-### entities/project.ts
-```typescript
-import { defineEntity } from '@donotdev/core';
-
-export const projectEntity = defineEntity({
-  name: 'Project',
-  collection: 'projects',
-  fields: {
-    // Technical fields (id, createdAt, updatedAt, createdById, updatedById)
-    // are automatically added by defineEntity - no need to add them manually
-    name: {
-      type: 'text',
-      visibility: 'user',
-      validation: { required: true, minLength: 3 }
-    },
-    owner: {
-      type: 'reference',
-      visibility: 'user',
-      ref: 'users',
-      validation: { required: true }
-    }
-  }
-});
-```
-
----
-
-BAD OUTPUT:
-
-"The Project entity should have fields for name, owner, and status."
-[WRONG: Description instead of code]
-
-```typescript
-owner: {
-  type: 'reference',
-  ref: 'User'  // WRONG: Should be 'users' (collection name, not entity name)
-}
-```
-</examples>
-
-<recovery>
-If HLD is ambiguous:
-- State what's unclear
-- Provide your best interpretation
-- Flag in Validation Issues
-
-If HLD has invalid field type:
-- Map to closest valid type
-- Flag in Validation Issues
-
-If HLD entity has no fields listed:
-- Flag as critical issue
-- Skip generating empty schema
-
-If custom component is unclear:
-- Ask for clarification
-- Provide best interpretation
-- Flag in Validation Issues
-</recovery>
-
-<completion_check>
-Output is complete when:
-□ All entities have full schemas with code
-□ Index file exports all entities
-□ All routes are defined
-□ All features are mapped
-□ All custom components have detailed specs
-□ Implementation plan is clear
-□ All issues are flagged (or "✅ All valid")
-
-Always generate complete results. If something is missing, flag it and still generate what you can.
-</completion_check>
-
-<start>
-I will paste my HLD below. Transform it into technical artifacts (LLD).
-
----
-HLD START
----
-</start>
+Persona and instructions are loaded by `start_phase(2)`. Call it before starting work.