@donotdev/cli 0.0.16 → 0.0.18

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@donotdev/cli",
-  "version": "0.0.16",
+  "version": "0.0.18",
   "description": "Command-line interface for DoNotDev Framework",
   "type": "module",
   "private": false,

package/templates/root-consumer/.claude/commands/brainstorm.md.example

@@ -41,6 +41,14 @@ description: Extract requirements and generate complete HLD through conversation
 
 ## Process
 
+### Step 0: Start Phase (MANDATORY — DO THIS FIRST)
+
+**BEFORE asking any questions or doing any work**, call:
+```
+start_phase(0)
+```
+This activates Phase 0: BRAINSTORM and loads the blueprint, persona, context, and lessons learned from previous sessions. **Do NOT proceed without this call.**
+
 ### Step 1: Activate EXTRACTOR Agent
 
 **Deploy:** `/agents extractor` (BMAD EXTRACTOR persona)
@@ -87,7 +95,7 @@ EXTRACTOR generates `HLD.md` with:
 
 ---
 
-## Validation Gate
+## Validation Gate & Phase Completion (MANDATORY)
 
 **Before proceeding to `/design`:**
 - [ ] HLD is complete (no empty sections or TBDs)
@@ -97,6 +105,12 @@ EXTRACTOR generates `HLD.md` with:
 - [ ] Native vs custom analysis complete
 - [ ] User has validated HLD
 
+**When HLD is complete**, write the filled-out spec to `docs/HLD.md` (the template at `guides/wai-way/spec_template.md` stays untouched as reference). Then call:
+```
+complete_phase({ files: ["docs/HLD.md"], summary: "HLD complete — N entities, N pages, N features" })
+```
+Then wait for the user to call `approve_phase()` before moving to `/design`.
+
 **Quality Over Speed:** Take as long as needed. A complete HLD that takes 4 hours is better than an incomplete one that takes 20 minutes.
 
 ---

package/templates/root-consumer/.claude/commands/build.md.example

@@ -36,6 +36,14 @@ description: Two-agent workflow: Prompt Engineer → Coder (AFTER /design)
 
 ## Process
 
+### Step 0: Start Phase (MANDATORY — DO THIS FIRST)
+
+**BEFORE writing any code**, call:
+```
+start_phase(3)
+```
+This activates Phase 3: COMPOSE and loads the blueprint, persona, context, and lessons. **Do NOT write code without this call.**
+
 ### Step 1: Activate FORGER Agent
 
 **Deploy:** `/agents builder` (BMAD FORGER persona)
@@ -54,10 +62,19 @@ description: Two-agent workflow: Prompt Engineer → Coder (AFTER /design)
    - Phase 6: Integration (wire everything together)
 4. Use framework defaults ONLY (no styling, no customization)
 5. Hardcode all strings (no i18n yet)
-6. Validate each phase before proceeding
+6. Run `dndev tc` after every file change — type errors must be fixed immediately
+7. Validate each phase before proceeding
 
 **Output:** Working app (functional MVP, no styling)
 
+### Phase Completion (MANDATORY)
+
+When all pages are built and `dndev tc` passes, call:
+```
+complete_phase({ files: ["src/pages/...all page files..."], summary: "N pages composed, all type-checking" })
+```
+Wait for user to call `approve_phase()` before moving to `/polish`.
+
 ---
 
 ## Alternative: Two-Agent Workflow
@@ -79,10 +96,15 @@ For complex builds, you can use:
 - **Builder (FORGER):** Implements exactly what's in LLD, uses framework defaults only
 - **Framework defaults ONLY:** No styling, no customization (deferred to /polish)
 - **Hardcode strings:** No i18n yet (deferred to /polish)
-- **MCP required:** Use lookup_symbol for ALL components
 - **Phase by phase:** Complete each phase before proceeding
 - **User:** Reviews output, proceeds to /polish when functional
 
+## STOP — lookup_symbol Before Every Component (Repeated Here On Purpose)
+
+**STOP before writing ANY `@donotdev` import.** Call `lookup_symbol({ symbol: "Name" })` first. Do NOT guess props, hooks, or APIs. Do NOT proceed without verification. `complete_phase` will reject un-looked-up symbols.
+
+**Import convention:** Always `@donotdev/<package>` — never sub-paths. No `@donotdev/ui/routing`, no `@donotdev/components/card`. The only exceptions are `@donotdev/core/server`, `@donotdev/core/vite`, `@donotdev/core/next`, `@donotdev/core/functions`.
+
 ## Mode Detection
 
 **CRITICAL:** Check working mode first.

package/templates/root-consumer/.claude/commands/design.md.example

@@ -36,6 +36,21 @@ description: Design workflow: Architect → Design Document (BEFORE /build)
 
 ## Process
 
+### Step 0: Start Phase (MANDATORY — DO THIS FIRST)
+
+**BEFORE doing any design work**, call the appropriate phase:
+```
+start_phase(1)   # for SCAFFOLD (routes, page stubs)
+start_phase(2)   # for ENTITIES (data models, fields, access)
+```
+This loads the blueprint, persona, context, and lessons. **Do NOT proceed without this call.**
+
+When design work is complete, call:
+```
+complete_phase({ files: ["...affected files..."], summary: "Description of what was designed" })
+```
+Wait for user to call `approve_phase()` before moving on.
+
 ### Step 1: Architect Phase
 
 **Deploy:** `/agents architect` (WAI-WAY architect role)
@@ -102,6 +117,8 @@ UNRESOLVED:
 - **ALWAYS reference framework architecture** - stay aligned
 - **ALWAYS identify impacts** - what breaks if we change this?
 - **ALWAYS prepare for /build** - design should be actionable
+- **ALWAYS use `lookup_symbol`** when referencing @donotdev components in your design — verify the API exists before putting it in the plan
+- **Import convention:** Always `@donotdev/<package>` top-level, never sub-paths. The only exceptions are `@donotdev/core/server`, `@donotdev/core/vite`, `@donotdev/core/next`, `@donotdev/core/functions`
 
 ## Integration with WAI-WAY & BMAD
 

package/templates/root-consumer/.claude/commands/polish.md.example

@@ -42,6 +42,14 @@ description: Generate tests, firestore rules, CI/CD, config, fix bugs, i18n (Pha
 
 ## Process
 
+### Step 0: Start Phase (MANDATORY — DO THIS FIRST)
+
+**BEFORE any polish work**, call:
+```
+start_phase(4)
+```
+This activates Phase 4: CONFIGURE and loads the blueprint, persona, context, and lessons. **Do NOT proceed without this call.**
+
 ### Step 1: Activate Polisher Agent
 
 **Deploy:** `/agents polisher` (Phase 4 Polisher persona)
@@ -112,6 +120,7 @@ Extract strings to `src/locales/`, replace with `useTranslation()`.
 ## Ship Readiness
 
 App is ready to ship when:
+- ✅ `dndev tc` passes
 - ✅ `bun test` passes
 - ✅ `firestore.rules` generated
 - ✅ `.github/workflows/ci.yml` created
@@ -121,6 +130,14 @@ App is ready to ship when:
 - ✅ Configuration complete
 - ✅ (Optional) i18n added
 
+## Phase Completion (MANDATORY)
+
+When all ship readiness checks pass, call:
+```
+complete_phase({ files: ["...all test/config files..."], summary: "Tests passing, config complete, ready to ship" })
+```
+Wait for user to call `approve_phase()`.
+
 ---
 
 ## Next Step

package/templates/root-consumer/AI.md.example

@@ -2,39 +2,52 @@
 
 > **You are building a DoNotDev app.** Read this file completely before doing anything else.
 
+## Welcome
+
+We'll build your app together in **5 structured phases**: brainstorm requirements, scaffold pages, define data, wire everything up, and polish for production. Each phase has a clear deliverable and validation gate. This isn't freeform coding — there's a proven methodology that produces solid, production-ready apps.
+
 ## What To Do Right Now
 
 1. **Verify MCP is working.** Call `list_features()`. If it fails, run `get_guide("AGENT_START_HERE")` for IDE-specific setup.
 2. Call `start_phase(0)` — begin **Phase 0: BRAINSTORM**
-3. Follow each phase in order. Do not skip phases.
+3. Follow each phase in order. **Do not skip phases. Do not work outside a phase.**
+
+## The 5 Phases — MANDATORY
 
-## The 5 Phases
+**ALL work MUST happen inside an active phase.** Call `start_phase(N)` BEFORE writing any code or documents. Call `complete_phase({ files })` BEFORE moving to the next phase. Working outside a phase is a violation — no exceptions.
 
-| Phase | Name | What Happens |
-|-------|------|-------------|
-| 0 | **BRAINSTORM** | Ask questions, understand requirements, produce validated spec |
-| 1 | **SCAFFOLD** | Create all routes and page stubs from spec |
-| 2 | **ENTITIES** | Define all data models (fields, access, visibility) |
-| 3 | **COMPOSE** | Build pages with framework components (hardcode strings) |
-| 4 | **CONFIGURE** | Config, test, polish, i18n. Run `/grill` and `/techdebt` before shipping |
+| Phase | Name | Slash Command | What Happens |
+|-------|------|---------------|-------------|
+| 0 | **BRAINSTORM** | `/brainstorm` | Ask questions, understand requirements, produce validated spec |
+| 1 | **SCAFFOLD** | `/design` | Create all routes and page stubs from spec |
+| 2 | **ENTITIES** | `/design` | Define all data models (fields, access, visibility) |
+| 3 | **COMPOSE** | `/build` | Build pages with framework components (hardcode strings) |
+| 4 | **CONFIGURE** | `/polish` | Config, test, polish, i18n. Run `/grill` and `/techdebt` before shipping |
 
-## Workflow Per Phase
+## Workflow Per Phase — NON-NEGOTIABLE
 
 ```
 start_phase(N)          → get blueprint + persona + context + lessons
   ↓
 work                    → follow blueprint, lookup_symbol for every component
   ↓
+dndev tc                → type-check MUST pass before completing phase
+  ↓
 complete_phase(files)   → validate conventions + symbol usage → submit for review
   ↓
-approve_phase()         → phase done, move to next
+approve_phase()         → user approves, move to next phase
 ```
 
-## Component Usage — Non-Negotiable
+**You MUST call `start_phase(N)` before ANY work in that phase.**
+**You MUST call `complete_phase({ files })` when the phase is done.**
+**You MUST run `dndev tc` after every code change and before every `complete_phase`.**
+Skipping these steps means the work is untracked, unvalidated, and unacceptable.
+
+## STOP — lookup_symbol Before ANY @donotdev Code
 
-**Never guess component props.** Call `lookup_symbol({ symbol: "ComponentName" })` before writing ANY `@donotdev` component. Every call is tracked — `complete_phase` flags components used without lookup.
+**STOP. Before writing ANY `@donotdev` import, call `lookup_symbol({ symbol: "Name" })`.** Do NOT guess. Do NOT proceed without it. `complete_phase` rejects un-looked-up symbols.
 
-Without MCP: read `.d.ts` files directly from `node_modules/@donotdev/*/dist/`.
+**Always import from `@donotdev/<package>` top-level** — never sub-paths. See `get_guide("SETUP_PAGES")` for conventions and patterns.
 
 ## CLI Commands
 
@@ -42,12 +55,30 @@ Without MCP: read `.d.ts` files directly from `node_modules/@donotdev/*/dist/`.
 
 | Command | What it does |
 |---------|-------------|
-| `dndev create-app` | Interactive wizard — creates a new app in the monorepo |
 | `dndev dev` | Start the dev server (Vite/Next.js via Turbo) |
-| `dndev emu start` | Start Firebase emulators |
+| `dndev dev:myapp` | Start dev server for a specific app |
+| `dndev build` | Build for production |
+| `dndev preview` | Preview production build |
+| `dndev emu` | Start dev with Firebase emulators |
+| `dndev tc` | **Type-check all packages — run after every code change** |
+| `dndev tc:myapp` | Type-check a specific app |
+| `dndev format` | Format code with Prettier |
 | `dndev deploy` | Deploy to production |
+| `dndev staging` | Deploy to staging/UAT |
 | `dndev setup firebase` | Configure Firebase project + .env |
 | `dndev setup supabase` | Configure Supabase project + .env |
+| `dndev doctor` | Check project health (providers, .env) |
+| `dndev bump` | Update @donotdev packages to latest |
+| `dndev cacheout` | Clear build caches |
+| `dndev sync-secrets` | Sync env vars to Firebase/Vercel/GitHub |
+| `dndev make-admin` | Set a user as admin |
+| `dndev agent` | Configure MCP server for AI agents |
+| `dndev wai` | Output WAI-WAY activation prompt |
+| `dndev create-app` | Interactive wizard — creates a new app in the monorepo |
+
+Most commands support `:<app>` syntax: `dndev dev:web`, `dndev tc:admin`, `dndev build:public`.
+
+Run `dndev --help` for the full command list.
 
 `dndev create-app` is **interactive** — it prompts for builder (Vite/Next.js/Expo), backend (Firebase/Supabase/none), and features. There is no `--preset` flag.
 
@@ -56,6 +87,7 @@ Without MCP: read `.d.ts` files directly from `node_modules/@donotdev/*/dist/`.
 - **ESM only** — never `require()`
 - **RTL safe** — use `start`/`end`, never `left`/`right`
 - **Import order** — React → vendors → @donotdev → relative
+- **Import convention** — always `@donotdev/<pkg>` top-level, never sub-paths
 - **Framework-first** — if something's missing, say what and stop
 - **No .md file creation** — never create documentation/analysis/summary .md files unless explicitly asked. Session notes go in `.dndev/`
 - **Follow existing patterns** — the scaffolded files ARE your documentation
@@ -64,8 +96,8 @@ Without MCP: read `.d.ts` files directly from `node_modules/@donotdev/*/dist/`.
 
 Call `get_guide("AGENT_START_HERE")` for the full tool reference, IDE setup, env var guide, and fallback instructions.
 
-Key tools: `start_phase` · `complete_phase` · `approve_phase` · `lookup_symbol` · `get_guide` · `get_guideline` · `search_framework` · `list_features` · `record_lesson`
+Key tools: `start_phase` · `complete_phase` · `approve_phase` · `lookup_symbol` · `get_guide` · `get_guideline` · `search_framework` · `list_features` · `record_lesson` · `run_typecheck`
 
 ## Security Gate
 
-Before production: run `dn soc2`. See `get_guide("SOC2")` for details.
+Before production: run `dndev doctor` and `/grill`. See `get_guide("SOC2")` for details.

package/templates/root-consumer/guides/dndev/ENV_SETUP.md.example

@@ -9,8 +9,8 @@ If you haven’t run `dndev init` yet, see [AGENT_START_HERE.md](./AGENT_START_H
 ## The Flow
 
 ```
-bun install                    -> install dependencies
-bun dev                        -> start app, read the homepage setup guide
+bun install                    → install dependencies
+dndev dev                        -> start app, read the homepage setup guide
 dndev setup firebase           -> configure Firebase project + .env
   -- or --
 dndev setup supabase           -> configure Supabase project + .env
@@ -24,7 +24,7 @@ dndev deploy                   -> deploy to production
 
 ```bash
 bun install
-bun dev
+dndev dev
 ```
 
 Open the app. The homepage shows every setup step with instructions.
@@ -73,7 +73,7 @@ Asks for your **public** project URL and anon key (both safe to share -- shipped
 
 Get them from: https://supabase.com/dashboard -> your project -> Settings -> API
 
-See [SETUP_SUPABASE.md](./SETUP_SUPABASE.md) for full details (tables, RLS, `dn generate sql`). See [Secrets Philosophy](#secrets-philosophy) for how we handle secret keys.
+See [SETUP_SUPABASE.md](./SETUP_SUPABASE.md) for full details (tables, RLS, `dndev generate sql`). See [Secrets Philosophy](#secrets-philosophy) for how we handle secret keys.
 
 ---
 
@@ -186,7 +186,7 @@ my-project/
 
 | Command | What It Does |
 |---------|-------------|
-| `bun dev` | Start dev server |
+| `dndev dev` | Start dev server |
 | `dndev emu start` | Start Firebase emulators |
 | `dndev setup firebase` | Configure Firebase project + .env |
 | `dndev setup supabase` | Configure Supabase project + .env |
@@ -215,4 +215,4 @@ my-project/
 
 ---
 
-**Start here: `bun install && bun dev`. The homepage tells you everything else.**
+**Start here: `bun install && dndev dev`. The homepage tells you everything else.**

package/templates/root-consumer/guides/dndev/INDEX.md.example

@@ -12,7 +12,7 @@
 - [ENV_SETUP.md](./ENV_SETUP.md) — After `dndev init`: env, Firebase/Supabase, deploy
 - [GOTCHAS.md](./GOTCHAS.md) - **Common mistakes & pitfalls** (phase-tagged, read before coding)
 - [SETUP_FIREBASE.md](./SETUP_FIREBASE.md) - Firebase project setup (`dndev setup firebase`)
-- [SETUP_SUPABASE.md](./SETUP_SUPABASE.md) - Supabase project setup (`dndev setup supabase`, `dn generate sql`)
+- [SETUP_SUPABASE.md](./SETUP_SUPABASE.md) - Supabase project setup (`dndev setup supabase`, `dndev generate sql`)
 - [SETUP_TESTING.md](./SETUP_TESTING.md) - Test generation (Phase 4)
 
 ---
@@ -36,7 +36,7 @@
 - [SETUP_BILLING.md](./SETUP_BILLING.md) - Stripe subscriptions (pre-configured)
 - [SETUP_BLOG.md](./SETUP_BLOG.md) - Convention-based markdown blog with i18n
 - [SETUP_PWA.md](./SETUP_PWA.md) - Progressive Web App setup
-- [SETUP_FUNCTIONS.md](./SETUP_FUNCTIONS.md) - Firebase Functions (pre-configured)
+- [SETUP_FUNCTIONS.md](./SETUP_FUNCTIONS.md) - Functions overview (redirects to provider guides)
 
 ---
 

package/templates/root-consumer/guides/dndev/SETUP_AUTH.md.example

@@ -1,6 +1,6 @@
-# Setup: Authentication (Firebase Auth)
+# Setup: Authentication
 
-**Most is pre-configured.** Firebase Auth for user sign-in/sign-up. Add env vars and config. Framework handles providers, callbacks, sessions.
+**Most is pre-configured.** Works with Firebase Auth or Supabase Auth. Add env vars and config. Framework handles providers, callbacks, sessions.
 
 ---
 
@@ -24,7 +24,8 @@ export const appConfig: AppConfig = {
 };
 ```
 
-**Firebase Console:** Enable providers in Authentication > Sign-in method
+**Firebase:** Enable providers in Firebase Console → Authentication → Sign-in method
+**Supabase:** Enable providers in Supabase Dashboard → Authentication → Providers
 
 ---
 
@@ -80,10 +81,10 @@ const signOut = useAuth('signOut');
 
 **Default:** All authenticated users are `'user'` role.
 
-**Setting admin/super roles:** Set Firebase Auth customClaims:
+**Setting admin/super roles:**
 
+**Firebase** — Set customClaims:
 ```typescript
-// Using Firebase Admin SDK
 import { getFirebaseAdminAuth } from '@donotdev/firebase/server';
 
 const auth = getFirebaseAdminAuth();
@@ -93,12 +94,18 @@ await auth.setCustomUserClaims(userId, {
 });
 ```
 
+**Supabase** — Set user metadata:
+```sql
+-- In Supabase Dashboard → SQL Editor
+UPDATE auth.users SET raw_app_meta_data = raw_app_meta_data || '{"role": "admin"}' WHERE id = '<user-id>';
+```
+
 **Using CLI:**
 ```bash
 dndev make-admin <userId>
 ```
 
-**Note:** User must sign out and sign in again for role changes to take effect (customClaims are in the ID token).
+**Note:** User must sign out and sign in again for role changes to take effect.
 
 **Used by:** CRUD access control, protected routes, field visibility filtering.