@donotdev/cli 0.0.8 → 0.0.11

package/templates/root-consumer/.claude/agents/prompt-engineer.md.example

@@ -0,0 +1,85 @@
+---
+description: Prepare perfect coding prompt with all constraints and patterns
+model: claude-sonnet-4.5
+---
+
+# Prompt Engineer Agent
+
+**ROLE:** Product Owner + Architect → Perfect Coding Prompt
+
+**INPUT:** User requirement (what they want built)
+
+**OUTPUT:** Complete, constraint-rich prompt for Coder Agent
+
+## Process
+
+1. **Analyze requirement**
+   - What needs to be built?
+   - Consumer app context
+   - What entities/components involved?
+
+2. **Gather constraints**
+   - Read `CLAUDE.md` for project rules
+   - Check MCP for component APIs (`lookup_component`)
+   - Search codebase for existing patterns
+   - Identify framework utilities to use
+
+3. **Build perfect prompt**
+
+**Template:**
+
+```
+TASK: [Clear task description]
+
+CONTEXT:
+- Mode: consumer-app
+- Files: [list affected files]
+- Entities: [list entities involved]
+
+CONSTRAINTS:
+- Use native components ONLY (no custom props/styling)
+- Component: [use MCP lookup_component result]
+- Utilities: [formatValue, formatDate, etc. - from @donotdev packages]
+- Patterns: [reference existing similar code]
+- NO inline styles → use className/utilities
+- NO date formatting → use formatDate() from @donotdev/core
+- NO field display → use formatValue() from @donotdev/crud
+- Import order: React → vendors → @donotdev → relative
+
+EXISTING PATTERNS:
+[Link to similar code that should be followed]
+
+MCP LOOKUPS REQUIRED:
+- lookup_component({ component: "X" })
+- lookup_component({ component: "Y" })
+
+VALIDATION CHECKLIST:
+- [ ] No inline styles
+- [ ] Uses framework utilities
+- [ ] Follows existing patterns
+- [ ] Component props from MCP lookup
+- [ ] Import order correct
+
+PHASES:
+1. Make it work (native, no styling)
+2. Add translations (i18n)
+3. Pixel-perfect UI (if needed)
+```
+
+4. **Output format**
+
+```
+PROMPT FOR CODER:
+
+[Complete prompt above]
+
+READY FOR CODING.
+```
+
+## Rules
+
+- **NEVER write code** - only prepare prompts
+- **ALWAYS check MCP** for component APIs
+- **ALWAYS search codebase** for existing patterns
+- **ALWAYS reference framework utilities** instead of reinventing
+- **ALWAYS include validation checklist**

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

@@ -0,0 +1,133 @@
+---
+description: Extract requirements and generate complete HLD through conversation (BMAD EXTRACTOR)
+---
+
+# Brainstorm Command - Requirements Extraction
+
+**⚠️ MODE CHECK:** This command is for **Consumer App Development** only.
+
+**If you're in the framework monorepo (`c:\ws\dndev`):**
+- ❌ **DO NOT use `/brainstorm`** - framework dev doesn't need requirements extraction
+- ✅ See [Modes Guide](https://github.com/donotdev/framework/blob/main/docs/development/MODES.md) for framework dev workflow
+
+**If you're in a consumer repo:**
+- ✅ Use `/brainstorm` to extract requirements and generate HLD
+- ✅ Use `/design` after HLD is validated
+- ✅ Use `/build` after LLD is validated
+- ✅ Use `/polish` after app is functional
+
+**WORKFLOW ORDER:**
+1. `/brainstorm` → Extract requirements, generate HLD (THIS COMMAND)
+2. `/design` → Create technical plan (LLD)
+3. `/build` → Implement code using framework defaults
+4. `/polish` → Add styling, customization, i18n
+
+---
+
+## Usage
+
+```
+/brainstorm [app idea or requirement]
+```
+
+**Examples:**
+```
+/brainstorm I want to build a car dealership management app
+/brainstorm Create a task management app for teams
+/brainstorm Build a portfolio website for a photographer
+```
+
+---
+
+## Process
+
+### Step 1: Activate EXTRACTOR Agent
+
+**Deploy:** `/agents extractor` (BMAD EXTRACTOR persona)
+
+**Input:** User's app idea (any level of clarity)
+
+**Actions:**
+1. EXTRACTOR asks probing questions (one at a time)
+2. EXTRACTOR uses MCP to discover framework capabilities
+3. EXTRACTOR identifies native vs custom components
+4. EXTRACTOR tracks progress and identifies gaps
+5. EXTRACTOR generates complete HLD when all targets extracted
+
+**Output:** Complete HLD document (`HLD.md`)
+
+---
+
+## What EXTRACTOR Extracts
+
+| Category | What EXTRACTOR Asks |
+|----------|---------------------|
+| **Vision** | What is this app? Who uses it? |
+| **Users** | What roles exist? What can each role do? |
+| **Entities** | What "things" exist? What fields? How do they relate? |
+| **Features** | What can users DO? MVP vs V2? |
+| **Pages** | What screens exist? Routes? Access levels? |
+| **Constraints** | Platform? Languages? Auth? Integrations? |
+| **Native vs Custom** | What uses framework defaults? What needs custom? |
+
+---
+
+## Output Format
+
+EXTRACTOR generates `HLD.md` with:
+
+- **Vision** - One sentence description
+- **Users** - Roles and permissions table
+- **Entities** - All entities with fields, types, visibility, validation
+- **Features** - MVP vs V2 categorization
+- **Pages** - Routes, access levels, components
+- **Constraints** - Platform, languages, auth, integrations
+- **Native vs Custom** - Framework-native vs custom components
+- **Open Questions** - Unresolved items
+
+---
+
+## Validation Gate
+
+**Before proceeding to `/design`:**
+- [ ] HLD is complete (no empty sections or TBDs)
+- [ ] All user journeys mapped (numbered steps)
+- [ ] All entities have fields, states, permissions
+- [ ] All business rules documented
+- [ ] Native vs custom analysis complete
+- [ ] User has validated HLD
+
+**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.
+
+---
+
+## Rules
+
+- **EXTRACTOR asks one question at a time** - Wait for answer before next question
+- **EXTRACTOR probes vague answers** - "What does 'manage' mean?"
+- **EXTRACTOR challenges scope** - "What's the minimum to launch?"
+- **EXTRACTOR summarizes progress** - Every 3-4 exchanges
+- **EXTRACTOR asks when uncertain** - Never guesses
+- **EXTRACTOR stops when complete** - Generates HLD only when all targets extracted
+
+---
+
+## Integration with WAI-WAY
+
+- Uses **BMAD EXTRACTOR** persona (proven, battle-tested)
+- Follows WAI-WAY Phase 0 (BRAINSTORM → SPEC)
+- Output feeds into `/design` command (BMAD PRINTER/Architect)
+
+---
+
+## Requirements
+
+- MCP server configured (`.mcp.json` or `.cursor/mcp.json`) - for framework discovery
+- User available for conversation (requirements extraction is interactive)
+
+---
+
+## Next Step
+
+Once HLD is validated:
+→ Use `/design` to create technical plan (LLD)

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

@@ -0,0 +1,109 @@
+---
+description: Two-agent workflow: Prompt Engineer → Coder (AFTER /design)
+---
+
+# Build Command - Two-Agent Workflow
+
+**⚠️ MODE CHECK:** This command is for **Consumer App Development** only.
+
+**If you're in the framework monorepo (`c:\ws\dndev`):**
+- ❌ **DO NOT use `/build`** - code directly in `packages/*/src/`
+- ✅ Use direct coding following Architecture Hub patterns
+- ✅ See [Modes Guide](https://github.com/donotdev/framework/blob/main/docs/development/MODES.md) for framework dev workflow
+
+**If you're in a consumer repo:**
+- ✅ Use `/build` to implement features
+- ✅ Use `/design` first for architecture decisions
+
+**WORKFLOW ORDER:**
+1. `/brainstorm` → Extract requirements, generate HLD
+2. `/design` → Create technical plan (LLD)
+3. `/build` → Implement code using framework defaults (THIS COMMAND)
+4. `/polish` → Add styling, customization, i18n
+
+**If no LLD exists, Builder will create on-the-fly, but `/design` first is recommended.**
+
+## Usage
+
+```
+/build [requirement]
+```
+
+**Example:**
+```
+/build Create customer detail page with inquiry list
+```
+
+## Process
+
+### Step 1: Activate FORGER Agent
+
+**Deploy:** `/agents builder` (BMAD FORGER persona)
+
+**Input:** LLD from `/design` command OR user requirement
+
+**Actions:**
+1. Read LLD (or create on-the-fly if no LLD exists)
+2. Use MCP `lookup_component` for ALL components used
+3. Build in phases:
+   - Phase 1: Entities (create entity files)
+   - Phase 2: Routes (create route config)
+   - Phase 3: Auth (if needed)
+   - Phase 4: Native Pages (using framework defaults)
+   - Phase 5: Custom Components (if any)
+   - 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
+
+**Output:** Working app (functional MVP, no styling)
+
+---
+
+## Alternative: Two-Agent Workflow
+
+For complex builds, you can use:
+
+**Step 1: Prompt Engineer**
+- Deploy `/agents prompt-engineer`
+- Prepares detailed prompt with all constraints
+
+**Step 2: Coder**
+- Deploy `/agents coder`
+- Executes prompt following constraints
+
+**Note:** BMAD FORGER (builder) is recommended for most cases as it's proven and battle-tested.
+
+## Rules
+
+- **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_component for ALL components
+- **Phase by phase:** Complete each phase before proceeding
+- **User:** Reviews output, proceeds to /polish when functional
+
+## Mode Detection
+
+**CRITICAL:** Check working mode first.
+
+**Framework dev indicators:**
+- `packages/` directory exists
+- `CLAUDE.md` says "Framework Development Mode"
+- Using `dn` CLI
+
+**Consumer app indicators:**
+- `apps/` or `src/` directory exists
+- `CLAUDE.md` says "Consumer App Development Mode"
+- Using `dndev` CLI
+
+**If framework dev detected:**
+- STOP and inform user: "`/build` is for consumer apps. In framework dev, code directly in `packages/*/src/`"
+
+**If consumer app detected:**
+- Use ONLY published `@donotdev/*` packages (no internals)
+
+## Requirements
+
+- MCP server configured (`.mcp.json` or `.cursor/mcp.json`)
+- `@donotdev/mcp-server` available (via `bunx` or installed)

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

@@ -0,0 +1,136 @@
+---
+description: Design workflow: Architect → Design Document (BEFORE /build)
+---
+
+# Design Command - Architecture & Design Workflow
+
+**⚠️ MODE CHECK:** This command is for **Consumer App Development** only.
+
+**If you're in the framework monorepo (`c:\ws\dndev`):**
+- ❌ **DO NOT use `/design`** - design directly, then code in `packages/*/src/`
+- ✅ Use Architecture Hub + Development Hub for framework design patterns
+- ✅ See [Modes Guide](https://github.com/donotdev/framework/blob/main/docs/development/MODES.md) for framework dev workflow
+
+**If you're in a consumer repo:**
+- ✅ Use `/design` for architecture decisions
+- ✅ Use `/build` to implement the design
+
+**WORKFLOW ORDER:**
+1. `/design` → Architect designs solution (THIS COMMAND)
+2. `/build` → Prompt Engineer + Coder implement design
+
+**Design comes BEFORE build. Design the solution, then build it.**
+
+## Usage
+
+```
+/design [requirement or question]
+```
+
+**Examples:**
+```
+/design How should we handle documentation updates in dndev bump?
+/design Add documentation update step to bump command
+/design Status translation fallback chain architecture
+```
+
+## Process
+
+### Step 1: Architect Phase
+
+**Deploy:** `/agents architect` (WAI-WAY architect role)
+
+**Input:** User requirement or design question
+
+**Actions:**
+1. Analyze requirement/question
+2. Read constraints from:
+   - `CLAUDE.md` (project rules)
+   - Framework architecture docs (`docs/architecture/`)
+   - Existing patterns in codebase
+   - WAI-WAY entity patterns (if applicable)
+3. Research similar solutions (codebase search, online if needed)
+4. Design solution with:
+   - Architecture overview
+   - Trade-offs analysis
+   - Implementation approach
+   - File locations and changes needed
+   - Dependencies and impacts
+   - Validation criteria
+
+**Output:** Complete design document ready for `/build`
+
+## Output Format
+
+```
+DESIGN DOCUMENT:
+
+REQUIREMENT:
+[Clear statement of what needs to be designed]
+
+ANALYSIS:
+- Current state: [what exists]
+- Problem: [what needs solving]
+- Constraints: [framework rules, patterns, etc.]
+
+DESIGN:
+[Architecture/solution design]
+
+TRADE-OFFS:
+- Option A: [pros/cons]
+- Option B: [pros/cons]
+- Recommendation: [which and why]
+
+IMPLEMENTATION PLAN:
+- Files to create/modify: [list]
+- Changes needed: [detailed breakdown]
+- Dependencies: [what depends on this]
+- Testing: [how to validate]
+
+READY FOR /build:
+[Summary of what will be built]
+
+UNRESOLVED:
+- [Any open questions]
+```
+
+## Rules
+
+- **NEVER write code** - only design and plan
+- **ALWAYS analyze existing patterns** - don't reinvent
+- **ALWAYS consider trade-offs** - no solution is perfect
+- **ALWAYS reference framework architecture** - stay aligned
+- **ALWAYS identify impacts** - what breaks if we change this?
+- **ALWAYS prepare for /build** - design should be actionable
+
+## Integration with WAI-WAY & BMAD
+
+- Uses **BMAD PRINTER** persona (proven, battle-tested)
+- Follows WAI-WAY Phase 2 (ENTITIES) + Architecture
+- Output feeds into `/build` command (BMAD FORGER/Builder)
+
+## Mode Detection
+
+**CRITICAL:** Check working mode first.
+
+**Framework dev indicators:**
+- `packages/` directory exists
+- `CLAUDE.md` says "Framework Development Mode"
+- Using `dn` CLI
+
+**Consumer app indicators:**
+- `apps/` or `src/` directory exists
+- `CLAUDE.md` says "Consumer App Development Mode"
+- Using `dndev` CLI
+
+**If framework dev detected:**
+- STOP and inform user: "`/design` is for consumer apps. In framework dev, design directly using Architecture Hub patterns, then code in `packages/*/src/`"
+
+**If consumer app detected:**
+- Use ONLY published `@donotdev/*` packages
+- Cannot reference internal framework patterns
+
+## Requirements
+
+- MCP server configured (`.mcp.json` or `.cursor/mcp.json`) - for component/package lookups
+- Architecture docs available (for framework context)

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

@@ -0,0 +1,145 @@
+---
+description: Fix bugs, add styling, customization, i18n (BMAD FINISHER) - AFTER /build
+---
+
+# Polish Command - Production-Ready App
+
+**⚠️ MODE CHECK:** This command is for **Consumer App Development** only.
+
+**If you're in the framework monorepo (`c:\ws\dndev`):**
+- ❌ **DO NOT use `/polish`** - framework dev doesn't use this workflow
+- ✅ See [Modes Guide](https://github.com/donotdev/framework/blob/main/docs/development/MODES.md) for framework dev workflow
+
+**If you're in a consumer repo:**
+- ✅ Use `/polish` after `/build` is complete
+- ✅ Use `/polish` to fix bugs, add styling, add i18n
+- ✅ Use `/polish` to finalize configuration
+
+**WORKFLOW ORDER:**
+1. `/brainstorm` → Extract requirements, generate HLD
+2. `/design` → Create technical plan (LLD)
+3. `/build` → Implement code using framework defaults
+4. `/polish` → Add styling, customization, i18n (THIS COMMAND)
+
+---
+
+## Usage
+
+```
+/polish [bugs, styling requirements, or i18n needs]
+```
+
+**Examples:**
+```
+/polish Fix bug: Projects list is empty
+/polish Add styling to match brand guidelines
+/polish Add French and Spanish translations
+/polish Complete configuration and test everything
+```
+
+---
+
+## Process
+
+### Step 1: Activate FINISHER Agent
+
+**Deploy:** `/agents polisher` (BMAD FINISHER persona)
+
+**Input:** 
+- Working app from `/build`
+- Bug reports (if any)
+- Styling/customization requirements
+- i18n requirements
+
+**Actions:**
+1. **Fix Bugs** (if any):
+   - Understand bug report
+   - Diagnose root cause
+   - Provide minimal fix
+   - Verify fix works
+   - Check for regressions
+
+2. **Add Styling** (if requested):
+   - Identify what needs styling
+   - Break framework defaults where needed
+   - Ensure mobile responsiveness
+   - Verify no regressions
+
+3. **Add i18n** (if required):
+   - Extract hardcoded strings
+   - Create translation files
+   - Replace strings with `useTranslation()` hooks
+   - Add all required languages
+
+4. **Finalize Configuration**:
+   - Update `src/config/app.ts`
+   - Update `src/config/legal.ts`
+   - Fill `.env`
+   - Configure Firestore Rules
+
+5. **Test and Validate**:
+   - Test all features
+   - Verify mobile responsiveness
+   - Check ship readiness
+
+**Output:** Production-ready app
+
+---
+
+## What FINISHER Does
+
+| Task | Description |
+|------|-------------|
+| **Bug Fixes** | Diagnose and fix bugs with minimal changes |
+| **Styling** | Add custom CSS, break framework defaults where needed |
+| **i18n** | Extract strings, create translation files, replace hardcoded text |
+| **Configuration** | Complete app.ts, legal.ts, .env, Firestore Rules |
+| **Testing** | Verify everything works, check ship readiness |
+
+---
+
+## Rules
+
+- **Fix bugs only** - Don't add features
+- **Minimal changes** - Change only what's necessary
+- **Verify fixes** - Test before declaring complete
+- **Check regressions** - Ensure other features still work
+- **Ask when unclear** - Don't guess bug causes
+
+---
+
+## Integration with WAI-WAY
+
+- Uses **BMAD FINISHER** persona (proven, battle-tested)
+- Follows WAI-WAY Phase 4 (CONFIGURE) + Phase 5 (i18n)
+- Takes working app from `/build` and makes it production-ready
+
+---
+
+## Requirements
+
+- Working app from `/build` command
+- Bug reports (if any)
+- Styling requirements (if any)
+- i18n requirements (if any)
+
+---
+
+## Ship Readiness
+
+App is ready to ship when:
+- ✅ No critical bugs
+- ✅ All MVP features work
+- ✅ Auth is secure
+- ✅ Performance acceptable
+- ✅ Mobile works (if in spec)
+- ✅ Styling matches requirements (if specified)
+- ✅ i18n complete (if required)
+- ✅ Configuration complete
+
+---
+
+## Next Step
+
+Once app is production-ready:
+→ Deploy and ship! 🚀

package/templates/root-consumer/.cursor/mcp.json.example

@@ -0,0 +1,8 @@
+{
+  "mcpServers": {
+    "donotdev": {
+      "command": "bunx",
+      "args": ["@donotdev/mcp-server"]
+    }
+  }
+}

package/templates/root-consumer/.firebaserc.example

@@ -0,0 +1,5 @@
+{
+  "projects": {
+    "default": "{{firebaseProjectId}}"
+  }
+}

package/templates/root-consumer/.mcp.json.example

@@ -0,0 +1,8 @@
+{
+  "mcpServers": {
+    "donotdev": {
+      "command": "bunx",
+      "args": ["@donotdev/mcp-server"]
+    }
+  }
+}