ai-flow-dev 2.1.3 → 2.1.4

package/prompts/backend/flow-build-phase-7.md

@@ -1,6 +1,6 @@
 ## PHASE 7: Operations & Deployment (10 min)
 
-> **Order for this phase:** 7.1 → 7.2 → 7.3 → 7.4 → 7.5 → 7.6 → 7.7 → 7.8 → 7.9 → 7.10 → 7.11
+> **Order for this phase:** 7.1 → 7.2 → 7.3 → 7.4 → 7.4.1 → 7.5 → 7.6 → 7.7 → 7.7.1 → 7.7.2 → 7.8 → 7.9 → 7.9.1 → 7.9.2 → 7.9.3 → 7.9.4 → 7.10 → 7.11
 
 > **📌 Scope-based behavior:**
 >
@@ -149,26 +149,46 @@ C) Manual deploy for all environments
 
 ```
 
-**7.4.1 Deployment Strategy**
+**7.4.1 Deployment Strategy** (Production-Ready and Enterprise only)
 
 ```
-What deployment strategy will you use?
+What deployment strategy will you use for production?
 
-A) ⭐ Standard deployment - Stop old, deploy new (downtime)
-B) 🏆 Blue-Green deployment - Zero-downtime, instant rollback
-C) ⚡ Canary deployment - Gradual rollout, A/B testing
-D) Rolling deployment - Gradual replacement (Kubernetes)
+A) ⭐ Rolling Deployment - Gradual replacement
+   - Replace instances one at a time
+   - Zero downtime
+   - Easy rollback
+
+B) 🔥 Blue-Green Deployment - Instant switch
+   - Two identical environments
+   - Switch traffic instantly
+   - Higher infrastructure cost
+
+C) ⚡ Canary Deployment - Progressive rollout
+   - Deploy to small percentage first
+   - Monitor for issues
+   - Gradually increase traffic
+
+D) 🏆 Feature Flags - Code-level control
+   - Deploy code, toggle features
+   - Instant enable/disable
+   - Best with: LaunchDarkly, Unleash
+
+Your choice: __
+
+Rollback plan:
+- How quickly must rollback complete? __ minutes
+- Who can trigger rollback? [DevOps/Tech Lead/Any developer]
+- Rollback trigger criteria? [Error rate > X%, latency > Y ms, manual]
 
 If Blue-Green:
 - Traffic switching: [Load balancer, DNS, etc.]
-- Rollback: [Instant switch back to blue]
 - Database migrations: [Strategy for zero-downtime]
 
 If Canary:
 - Initial traffic: __%
 - Gradual increase: __% per __ minutes
 - Success criteria: __
-- Rollback trigger: __
 ```
 
 **7.5 Monitoring & Logging**
@@ -454,6 +474,88 @@ Services to protect:
 {{/EACH}}
 ```
 
+**7.9.3 Retry & Timeout Policies**
+
+```
+Define retry and timeout policies for external dependencies:
+
+| Service/Dependency | Timeout   | Retries | Backoff Strategy     | Notes                |
+|--------------------|-----------|---------|----------------------|----------------------|
+| Database queries   | 5000ms    | 2       | None (fail fast)     | Connection pooled    |
+| Redis cache        | 1000ms    | 1       | None                 | Cache miss = OK      |
+| Payment API        | 30000ms   | 3       | Exponential (1s,2s,4s)| Must complete        |
+| Email service      | 5000ms    | 3       | Fixed (2s)           | Queue if fails       |
+| External REST APIs | 10000ms   | 2       | Exponential          | Circuit breaker      |
+| File storage (S3)  | 15000ms   | 3       | Exponential          | Large files          |
+
+Your policies:
+
+| Service/Dependency | Timeout   | Retries | Backoff Strategy     | Notes                |
+|--------------------|-----------|---------|----------------------|----------------------|
+|                    |           |         |                      |                      |
+|                    |           |         |                      |                      |
+
+Global defaults:
+- Default HTTP timeout: __ ms (recommended: 10000)
+- Default retries: __ (recommended: 2)
+- Default backoff: [None/Fixed/Exponential]
+
+Non-retryable errors:
+- 400 Bad Request (client error, won't succeed on retry)
+- 401/403 Unauthorized/Forbidden
+- 404 Not Found
+- [Your additions]
+```
+
+**7.9.4 Request/Response Logging & Masking**
+
+```
+What request/response data will you log?
+
+Log levels by environment:
+| Environment | Level    | Body Logging | Performance Logging |
+|-------------|----------|--------------|---------------------|
+| Development | debug    | Full         | Yes                 |
+| Staging     | info     | Truncated    | Yes                 |
+| Production  | info     | Minimal      | Yes                 |
+
+Request logging:
+- ✅ HTTP method and URL
+- ✅ Request ID (correlation)
+- ✅ User ID (if authenticated)
+- ✅ IP address (optional, may hash for privacy)
+- ✅ Request duration (ms)
+- ❓ Request body (careful with size and PII)
+- ❓ Query parameters
+
+Response logging:
+- ✅ Status code
+- ✅ Response duration (ms)
+- ❓ Response body (careful with size)
+
+Sensitive data masking (CRITICAL):
+
+| Field Pattern          | Masking Strategy           |
+|------------------------|----------------------------|
+| password, secret       | Completely redact          |
+| token, api_key         | Show last 4 chars only     |
+| email                  | j***@example.com           |
+| phone                  | ***-***-1234               |
+| credit_card            | ****-****-****-1234        |
+| ssn, national_id       | Completely redact          |
+| [Your patterns]        | __                         |
+
+Log format:
+A) ⭐ Structured JSON (recommended for aggregation)
+B) Plain text with patterns
+C) Framework default
+
+Log aggregation:
+A) ⭐ Centralized (ELK, Datadog, CloudWatch)
+B) File-based with rotation
+C) Console only (development)
+```
+
 **7.10 Documentation & Runbooks**
 
 ```
@@ -507,9 +609,7 @@ C) 📄 Manual
 
 #### 🎨 MERMAID OPERATIONS DIAGRAM FORMATS - CRITICAL
 
-**Use these exact formats** for operational and infrastructure diagrams mentioned in question 7.10:
-
----
+## **Use these exact formats** for operational and infrastructure diagrams mentioned in question 7.10:
 
 ##### 1️⃣ System Architecture Diagram (Deployment View)
 
@@ -575,9 +675,7 @@ graph TD
 ```
 ````
 
-**Use for:** Showing deployed infrastructure, scaling configuration, redundancy, high availability
-
----
+## **Use for:** Showing deployed infrastructure, scaling configuration, redundancy, high availability
 
 ##### 2️⃣ Data Flow Diagram (Request Flow)
 
@@ -612,9 +710,7 @@ flowchart LR
 ```
 ````
 
-**Use for:** Documenting request/response cycles, async processing flows, numbered execution steps
-
----
+## **Use for:** Documenting request/response cycles, async processing flows, numbered execution steps
 
 ##### 3️⃣ Infrastructure Diagram (Cloud Resources)
 
@@ -685,9 +781,7 @@ graph TB
 ```
 ````
 
-**Use for:** Documenting cloud architecture, network topology, AWS/GCP/Azure resources, VPC design
-
----
+## **Use for:** Documenting cloud architecture, network topology, AWS/GCP/Azure resources, VPC design
 
 ##### 4️⃣ Monitoring & Observability Diagram (Optional)
 
@@ -744,9 +838,7 @@ graph TD
 ```
 ````
 
-**Use for:** Documenting observability strategy, monitoring infrastructure, alerting workflows
-
----
+## **Use for:** Documenting observability strategy, monitoring infrastructure, alerting workflows
 
 **Best Practices for Operations Diagrams:**
 
@@ -775,9 +867,7 @@ graph TD
 - For Serverless: Show Lambda functions, API Gateway, S3 triggers, event sources
 - For VMs: Show instances, security groups, load balancers, auto-scaling groups
 
-**Validation:** Test diagrams at https://mermaid.live/ before saving to ensure syntax is correct
-
----
+## **Validation:** Test diagrams at https://mermaid.live/ before saving to ensure syntax is correct
 
 ### Phase 7 Output
 
@@ -853,9 +943,7 @@ Re-read files to refresh context before continuing.
 
 ---
 
-**Proceed to final generation only after documents are validated.**
-
----
+## **Proceed to final generation only after documents are validated.**
 
 ## FINAL STEP: Generate Remaining Documents & Tool Configs
 
@@ -892,9 +980,7 @@ When you're done, type "ready" and I'll re-read ALL documents
 to ensure the final generation uses the most up-to-date information.
 ```
 
-Then execute `read_file()` for ALL previously generated documents.
-
----
+## Then execute `read_file()` for ALL previously generated documents.
 
 ### 📖 Loading Complete Context for Final Generation
 
@@ -953,9 +1039,7 @@ Phase 7:
 ✅ docs/operations.md
 ✅ specs/configuration.md
 ✅ .env.example
-
 ---
-
 📊 Progress Summary:
 
 Phases 1-7 completed:
@@ -972,9 +1056,7 @@ Phases 1-7 completed:
 
 Remaining:
 ⏭️  Phase 8: Project setup & final documentation
-
 ---
-
 🎯 Next: Phase 8 - Project Setup & Final Documentation
 
 Phase 8 will:
@@ -1112,9 +1194,7 @@ When executing this master prompt:
 - Phases 1-7: 30-60 min (only missing questions)
 - **Total: 40-80 minutes** (40-60% time saved!)
 
-This is an investment that will save 10-20 hours over the project lifecycle.
-
----
+## This is an investment that will save 10-20 hours over the project lifecycle.
 
 **EXECUTION FLOW:**
 

package/prompts/backend/flow-build-phase-8.md

@@ -5,9 +5,7 @@
 **Duration:** 10-15 minutes
 
 **Goal:** Set up the project structure and create comprehensive documentation that consolidates all information from previous phases.
-
----
-
+---
 ## 📋 Phase 8 Overview
 
 This final phase will:
@@ -18,9 +16,7 @@ This final phase will:
 4. **Generate master index** (AGENT.md)
 5. **Generate README.md** (with intelligent merge if needed)
 6. **Create tool-specific configs** (based on AI tool selection)
-
----
-
+---
 ## 8.1: Project State Detection
 
 > ⚠️ **PRE-REQUISITE CHECK:** Before proceeding, verify that README.md does NOT exist yet (unless it's a framework-generated one from previous initialization). If README.md exists and was NOT generated by a framework, this indicates an error in previous phases.
@@ -57,9 +53,7 @@ Found:
 
 Recommendation: [Next action based on state]
 ```
-
----
-
+---
 ## 8.2: Framework Initialization (Optional)
 
 **Only if:** Project state = "New Project"
@@ -471,9 +465,7 @@ Next steps:
 - ✅ **ONLY** create .env.example, .gitignore, docker-compose (optional), ORM init
 - ✅ **LET** framework CLI handle structure, configs, dependencies
 - ✅ **REFER** to official docs for starter code when needed
-
----
-
+---
 ## 8.2.7: Generate .gitignore (Always)
 
 **IMPORTANT:** This step runs for ALL projects, regardless of framework initialization choice.
@@ -627,9 +619,7 @@ docker-compose.override.yml
 ✅ Generated: .gitignore
    Patterns included: [Node.js | Python | Go] + [Prisma] + [Docker]
 ```
-
----
-
+---
 ## 8.3: Generate Final Documentation
 
 ```
@@ -696,9 +686,7 @@ Generating...
 ```
 ✅ Generated: docs/business-flows.md
 ```
-
----
-
+---
 ### 8.3.2: Generate docs/api.md
 
 - **Template:** `.ai-flow/templates/docs/api.template.md`
@@ -780,9 +768,7 @@ We use [workflow from Phase 5]
 ```
 ✅ Generated: docs/contributing.md
 ```
-
----
-
+---
 ## 8.4: Generate AGENT.md (Master Index)
 
 - **Template:** `.ai-flow/templates/AGENT.template.md`
@@ -843,9 +829,7 @@ We use [workflow from Phase 5]
 
 [From operations.md and contributing.md]
 ```
-
----
-
+---
 ## 8.5: Generate README.md (Intelligent Merge)
 
 - **Template:** `.ai-flow/templates/README.template.md`
@@ -938,9 +922,7 @@ The API will be available at `http://localhost:3000`
 ✅ Generated: .ai-flow/README.md
    [If merged] Merged with framework's setup instructions
 ```
-
----
-
+---
 ## 8.6: Generate AGENT.md (Master Index)
 
 **CRITICAL:** Before generating AGENT.md, re-read ALL previously generated documents to have complete context.
@@ -973,9 +955,7 @@ Now generate AGENT.md with complete information from all documents.
 ```
 ✅ Generated: .ai-flow/AGENT.md (Master Index)
 ```
-
----
-
+---
 ## 8.7: Create Tool-Specific Configs
 
 **Based on AI tool selection from Phase 3 (question 3.8):**
@@ -1093,9 +1073,7 @@ Master index: `.ai-flow/AGENT.md`
 ✅ Generated tool-specific configs:
    [List generated files based on selection]
 ```
-
----
-
+---
 ## 8.8: Final Validation & Success Message
 
 ```
@@ -1156,9 +1134,7 @@ Phase 8:
 
 Tool-specific configs:
 ✅ [List generated configs: .clauderules, .cursorrules, .github/copilot-instructions.md]
-
----
-
+---
 📁 Project Structure:
 ```
 
@@ -1187,9 +1163,7 @@ your-project/
 └── [tool configs] # .clauderules, .cursorrules, etc.
 
 ````
-
----
-
+---
 Next steps:
 
 1. ⭐ **Read `.ai-flow/AGENT.md`** - Master index of all documentation
@@ -1201,9 +1175,7 @@ Next steps:
 5. 🚀 **Install dependencies** - Run: `[show command from Phase 7]`
 6. 💾 **Initialize git** (if not done) - `git init && git add . && git commit -m "Initial commit with AI Flow docs"`
 7. 🧪 **Start building!** - Your AI assistant now has complete project context
-
----
-
+---
 💡 **Remember:**
 
 - Documents are **living artifacts** - update them as project evolves
@@ -1223,9 +1195,7 @@ Your AI assistant (Claude, Cursor, Copilot) will now:
 Happy building! 🎉
 
 ```
-
----
-
+---
 ## EXECUTION CHECKLIST FOR AI ASSISTANT
 
 When executing Phase 8:
@@ -1308,26 +1278,20 @@ When executing Phase 8:
 - 8.6: Tool configs - 1 min
 - 8.7: Validation - 1 min
 - **Total: 10-15 minutes**
-
----
-
+---
 **FINAL STEP: Offer Phase 9 (Implementation Roadmap)**
 
 ```
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+---
 ✅ PHASE 8 COMPLETE: PROJECT READY FOR DEVELOPMENT
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
+---
 🎯 All documentation generated and validated!
 📁 Project initialized and ready
 📖 AGENT.md and README.md created
 ⚙️ AI tool configurations in place
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+---
 🗺️ Optional: Generate Implementation Roadmap?
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
+---
 Phase 9 will analyze all your documentation and generate a complete
 implementation roadmap with:
 
@@ -1360,11 +1324,9 @@ Your choice (A/B): \_\_
 **If choice B:** Show completion message:
 
 ```
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+---
 ✅ DOCUMENTATION COMPLETE - READY TO BUILD
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
+---
 Your project is fully documented and initialized! 🎉
 
 📖 Next steps:
@@ -1374,13 +1336,14 @@ Your project is fully documented and initialized! 🎉
 3. Generate roadmap anytime by asking "Continue to Phase 9"
 
 Happy coding! 🚀
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
+---
 ```
-
----
-
+---
 **CONTINUE TO:** Phase 9 (optional) or End
 
 **SUCCESS:** Project fully documented and ready for development! 🚀
 ```
+
+
+
+