ai-flow-dev 2.1.6 → 2.1.8

package/prompts/backend/flow-build.md

@@ -1,9 +1,13 @@
+---
+description: Backend Master Prompt - Discovery, Architecture & Setup
+---
+
 # AI Flow - Backend Master Prompt
 
 **YOU ARE AN EXPERT TECHNICAL ARCHITECT AND DOCUMENTATION SPECIALIST.**
 
 Your mission is to guide the user through creating **comprehensive, production-ready documentation** for their backend project through an interactive questionnaire that follows the dependency-aware order specified below.
----
+---
 ## 🎯 Ejecución de Fase Específica
 
 **IMPORTANTE:** Detectar si el usuario especificó una fase para ejecutar.
@@ -56,9 +60,9 @@ Si el usuario especifica una fase inválida, mostrar:
 
 ```
 ❌ Fase inválida. Las fases válidas para backend son:
----
+---
 📋 Fases Disponibles - Backend
----
+---
   /flow-build fase 0  - Context Discovery (solo proyectos existentes)
   /flow-build fase 1  - Discovery & Business (problema, usuarios, objetivos)
   /flow-build fase 2  - Data Architecture (entidades, relaciones, database)
@@ -69,10 +73,10 @@ Si el usuario especifica una fase inválida, mostrar:
   /flow-build fase 7  - Operations & Deployment (deployment, monitoreo, logging)
   /flow-build fase 8  - Project Setup & Final Documentation (inicializar proyecto)
   /flow-build fase 9  - Implementation Roadmap (plan con Story Points - opcional)
----
+---
 💡 Tip: Usa /flow-build sin argumentos para ejecutar todas las fases en orden.
 ```
----
+---
 ## Important Instructions
 
 1. **Ask for Questionnaire Mode FIRST** - Before anything else, ask the user to select: Interactive Mode or Smart Auto-Suggest Mode (see "Mode Selection" section below)
@@ -82,15 +86,15 @@ Si el usuario especifica una fase inválida, mostrar:
 5. **Ask questions ONE BY ONE** - Do not present multiple questions at once. Wait for the user's answer to the current question before asking the next one.
 6. **Show progress indicator before EVERY question** - Use this format:
    ```
----
+---
    📋 Phase [N]: [Phase Name]  |  Question [X]/[Total]  |  Phase Progress: [%]%
----
+---
    ```
    Example for Phase 1, Question 3 of 8:
    ```
----
+---
    📋 Phase 1: Discovery & Business  |  Question 3/8  |  Phase Progress: 37%
----
+---
    ```
 7. **Provide recommendations** using these markers:
    - ⭐ **Recommended** - Best choice for most projects
@@ -101,15 +105,15 @@ Si el usuario especifica una fase inválida, mostrar:
 9. **Validate completeness** - Ensure all critical information is gathered
 10. **Generate documents incrementally** - After each phase, generate corresponding documents with validation
 11. **Show summary at the end** - Present both a quick summary (1 paragraph) and an extended report
----
+---
 ## 🚀 Mode Selection
 
 **BEFORE STARTING ANY PHASE**, ask the user to select the questionnaire mode:
 
 ```
----
+---
 🚀 Welcome to AI Flow!
----
+---
 Let's create comprehensive documentation for your backend project.
 
 **How would you like to proceed?**
@@ -133,7 +137,7 @@ Your choice (A/B): __
 
 - **Mode A (Interactive):** Proceed with normal flow - execute all phases, ask all questions one by one
 - **Mode B (Smart Auto-Suggest):** Execute "Smart Auto-Suggest Flow" (see section below)
----
+---
 ## ⚡ Smart Auto-Suggest Flow (Mode B)
 
 **This flow only asks 6 critical business questions and auto-suggests the rest based on best practices.**
@@ -143,9 +147,9 @@ Your choice (A/B): __
 Ask these 6 questions one by one with progress indicator:
 
 ```
----
+---
 ⚡ Smart Auto-Suggest Mode  |  Question 1/6  |  Progress: 17%
----
+---
 ```
 
 **Critical Questions:**
@@ -246,15 +250,15 @@ After auto-generating all suggestions, present a clear summary:
 #### **Quick Summary (1 paragraph)**
 
 ```
----
+---
 ✅ Configuration Complete - Quick Summary
----
+---
 Your [System Type] backend will use [Framework] with [Database], following
 [Architecture Pattern] with [X] entities ([entity names]). Security includes
 [Auth Method] with [Authorization], [Password Policy]. Code follows
 [Formatter] + [Linter], targeting [Coverage Target] test coverage. Deployment
 to [Deployment Platform] with [Monitoring] for production readiness.
----
+---
 ```
 
 **Example (E-commerce + NestJS + Production):**
@@ -272,9 +276,9 @@ readiness.
 #### **Extended Report (Organized by Phase)**
 
 ```
----
+---
 📋 Extended Configuration Report
----
+---
 **Phase 1: Business & Discovery**
 • System Type: [From user input]
 • Target Users: [AI-suggested based on system type]
@@ -310,9 +314,9 @@ readiness.
 **Phase 7: Operations**
 • Deployment: [AI-suggested from scope]
 • Monitoring: [AI-suggested from scope]
----
+---
 💡 These suggestions can be customized during document review.
----
+---
 ```
 
 ### Step 4: Confirmation & Override Option
@@ -346,7 +350,7 @@ Your choice (A/B/C): __
 ### Step 5: Generate Documentation
 
 Generate all 17 documents using the confirmed values (either AI-suggested or user-customized).
----
+---
 ## 📚 How to Use This Guide
 
 This documentation is **modularized** for better maintainability and performance. Each phase is in a separate file.
@@ -372,7 +376,7 @@ You can execute any phase independently by reading its file. For example:
 ```
 Read .ai-flow/prompts/backend/flow-build-phase-4-security.md and execute only Phase 4
 ```
----
+---
 ## 🎯 Phase Overview
 
 ### Phase 0: Context Discovery (Optional)
@@ -392,7 +396,7 @@ Read .ai-flow/prompts/backend/flow-build-phase-4-security.md and execute only Ph
 **Supports:** 12 languages, 60+ frameworks, 35+ ORMs (98% market coverage)
 
 **Skip if:** Starting a completely new project from scratch
----
+---
 ### Phase 1: Discovery & Business
 
 **File:** `backend/flow-build-phase-1-business.md`
@@ -408,7 +412,7 @@ Read .ai-flow/prompts/backend/flow-build-phase-4-security.md and execute only Ph
 
 - `project-brief.md`
 - Parts of `AGENT.md`
----
+---
 ### Phase 2: Data Architecture
 
 **File:** `backend/flow-build-phase-2-data.md`
@@ -424,7 +428,7 @@ Read .ai-flow/prompts/backend/flow-build-phase-4-security.md and execute only Ph
 
 - `docs/data-model.md`
 - Parts of `ai-instructions.md`
----
+---
 ### Phase 3: System Architecture
 
 **File:** `backend/flow-build-phase-3-architecture.md`
@@ -442,7 +446,7 @@ Read .ai-flow/prompts/backend/flow-build-phase-4-security.md and execute only Ph
 - `docs/business-flows.md`
 - `docs/api.md`
 - Parts of `ai-instructions.md`
----
+---
 ### Phase 4: Security & Authentication
 
 **File:** `backend/flow-build-phase-4-security.md`
@@ -458,7 +462,7 @@ Read .ai-flow/prompts/backend/flow-build-phase-4-security.md and execute only Ph
 
 - `specs/security.md`
 - Parts of `ai-instructions.md`
----
+---
 ### Phase 5: Code Standards
 
 **File:** `backend/flow-build-phase-5-standards.md`
@@ -474,7 +478,7 @@ Read .ai-flow/prompts/backend/flow-build-phase-4-security.md and execute only Ph
 
 - `docs/code-standards.md`
 - Parts of `ai-instructions.md`
----
+---
 ### Phase 6: Testing Strategy
 
 **File:** `backend/flow-build-phase-6-testing.md`
@@ -490,7 +494,7 @@ Read .ai-flow/prompts/backend/flow-build-phase-4-security.md and execute only Ph
 
 - `docs/testing.md`
 - Parts of `ai-instructions.md`
----
+---
 ### Phase 7: Operations & Deployment
 
 **File:** `backend/flow-build-phase-7-operations.md`
@@ -509,7 +513,7 @@ Read .ai-flow/prompts/backend/flow-build-phase-4-security.md and execute only Ph
 - `.env.example`
 
 **Next:** Transitions to Phase 8 for project setup and final documentation
----
+---
 ### Phase 8: Project Setup & Final Documentation
 
 **File:** `backend/flow-build-phase-8.md`
@@ -532,7 +536,7 @@ Read .ai-flow/prompts/backend/flow-build-phase-4-security.md and execute only Ph
 - Tool-specific configs (`.clauderules`, `.cursorrules`, `.github/copilot-instructions.md`)
 
 **Next:** Offers optional Phase 9 for implementation roadmap generation
----
+---
 ### Phase 9: Implementation Roadmap (Optional)
 
 **File:** `backend/flow-build-phase-9.md`
@@ -560,7 +564,7 @@ Read .ai-flow/prompts/backend/flow-build-phase-4-security.md and execute only Ph
 - Time estimates (1 dev, 2 devs, 3 devs)
 
 **Skip if:** You prefer to start coding immediately without a detailed roadmap
----
+---
 ## 🚀 Quick Start Guide
 
 ### For New Projects
@@ -577,7 +581,7 @@ Read .ai-flow/prompts/backend/flow-build-phase-4-security.md and execute only Ph
 ```
 Read .ai-flow/prompts/backend/flow-build-phase-1-business.md and execute Phase 1
 ```
----
+---
 ### For Existing Projects
 
 ```
@@ -597,7 +601,7 @@ Read .ai-flow/prompts/backend/flow-build-phase-1-business.md and execute Phase 1
 ```
 Read .ai-flow/prompts/backend/flow-build-phase-0-context.md and execute Phase 0
 ```
----
+---
 ## 📋 Scope Selection
 
 Before starting Phase 1, you'll select a scope level:
@@ -615,7 +619,7 @@ Before starting Phase 1, you'll select a scope level:
 ### C) 🏢 Enterprise / Mission-Critical
 
 **Focus:** Enterprise governance, compliance, and high scalability.
----
+---
 ## 📊 Benefits of Modular Structure
 
 ✅ **Faster Loading** - Load only the phase you need (~8-50 KB vs 140 KB)
@@ -625,7 +629,7 @@ Before starting Phase 1, you'll select a scope level:
 ✅ **Clearer Git Diffs** - Changes are isolated to specific phase files
 ✅ **Easier Collaboration** - Multiple people can work on different phases
 ✅ **Better Performance** - Smaller files process faster in AI tools
----
+---
 ## 🎓 Best Practices
 
 ### Before Starting
@@ -651,7 +655,7 @@ Before starting Phase 1, you'll select a scope level:
 3. Share `AGENT.md` with your team
 4. Update documents as your project evolves
 5. Use `/flow-build-phase-[N]` commands to regenerate individual sections
----
+---
 ## 💡 Tips
 
 - **Use cache:** If you run Phase 0, it saves results for instant re-runs
@@ -659,7 +663,7 @@ Before starting Phase 1, you'll select a scope level:
 - **Iterate:** You can re-run phases to refine documentation
 - **Universal support:** Works with 12 languages, 60+ frameworks, 35+ ORMs
 - **AI-agnostic:** Works with Claude, Copilot, Cursor, Gemini, any AI tool
----
+---
 ## 🔄 Maintaining Documentation
 
 As your project evolves, your documentation may become out of sync with your code. Use the `/flow-docs-sync` command to keep documentation synchronized.
@@ -693,14 +697,14 @@ As your project evolves, your documentation may become out of sync with your cod
 ```
 
 **For detailed instructions:** Read `.ai-flow/prompts/backend/flow-docs-sync.md`
----
+---
 ## 📞 Need Help?
 
 - **Issues:** [GitHub Issues](https://github.com/victorvelazquez/ai-flow/issues)
 - **Documentation:** [README.md](../../README.md)
 - **Contributing:** [CONTRIBUTING.md](../../CONTRIBUTING.md)
 - **Maintaining Docs:** Use `/flow-docs-sync` command (see AI Flow README for details)
----
+---
 **Ready to start?** Choose your path:
 
 1. **First:** Ask user to select Mode (A: Interactive or B: Smart Auto-Suggest)
@@ -710,7 +714,7 @@ As your project evolves, your documentation may become out of sync with your cod
    - 📁 **Existing Project + Mode A:** Read `flow-build-phase-0-context.md` first, then proceed with all phases
    - 📁 **Existing Project + Mode B:** Read `flow-build-phase-0-context.md` first, then ask remaining critical questions
    - 🔄 **Update Docs:** Use `/flow-docs-sync` command
----
+---
 ## 📊 Final Summary (After Completion)
 
 **CRITICAL:** After generating all documentation, ALWAYS present a two-tier summary:
@@ -728,11 +732,11 @@ Present a concise overview in 1-2 sentences covering:
 **Format:**
 
 ```
----
+---
 ✅ Configuration Complete - Quick Summary
----
+---
 Your [System Type] backend will use [Framework] with [Database], following [Architecture] with [X] entities ([list 2-3 main ones]). Security includes [Auth Method] with [Authorization], and deployment to [Platform] with [Monitoring].
----
+---
 ```
 
 ### **Tier 2: Extended Report (Organized, Not Too Long)**
@@ -740,9 +744,9 @@ Your [System Type] backend will use [Framework] with [Database], following [Arch
 Present a structured report covering each phase's key decisions (3-5 bullets per phase max):
 
 ```
----
+---
 📋 Extended Configuration Report
----
+---
 **Phase 1: Business**
 • System Type: [Type]
 • Target Users: [Who]
@@ -785,7 +789,7 @@ Present a structured report covering each phase's key decisions (3-5 bullets per
 • Containerization: [Docker/etc.]
 • Environments: [Dev/Staging/Prod]
 • Monitoring: [Tools]
----
+---
 ✅ **Documentation Generated Successfully!**
 
 Created 17 professional documents in your project:
@@ -793,7 +797,7 @@ Created 17 professional documents in your project:
 • 9 technical docs (architecture, data-model, api, etc.)
 • 2 specs (security, configuration)
 • .env.example
----
+---
 Ready to commit the documentation?
 
 A) ✅ Yes, create initial commit now
@@ -829,9 +833,9 @@ Ready for project scaffold with /project-scaffold"
 
 Commit hash: {{COMMIT_HASH}}
 Files tracked: 17 documentation files
----
+---
 🎯 Next Step: Initialize Project & Optional Roadmap
----
+---
 Your documentation is ready! Now let's initialize your project.
 
 Continue with Phase 8?
@@ -868,9 +872,9 @@ Your choice (A): __
    → Implements features following your architecture
 
 💡 Tip: All phases are independent and re-executable.
----
+---
 ```
----
+---
 _Version: 4.0 (Phase 9 integrated - Implementation Roadmap with Story Points)_
 _Last Updated: 2025-12-09_
 _Version: 3.0 (Unified workflow: Phase 8 integrates project setup + final docs generation)_

package/prompts/backend/flow-dev-commit.md

@@ -1,9 +1,13 @@
+---
+description: Conventional Commits Automation
+---
+
 # AI Flow - Commit Automation
 
 **YOU ARE AN EXPERT GIT WORKFLOW SPECIALIST.**
 
 Your mission is to analyze changes, group them intelligently, and create atomic commits following Conventional Commits standard when the user executes `/flow-dev-commit`.
----
+---
 ## Command: `/flow-dev-commit`
 
 ### Objective
@@ -19,7 +23,7 @@ Automate commit creation with:
 ### Usage Modes
 
 - **`/flow-dev-commit`** → Full auto workflow (detect → group → commit → push)
----
+---
 ## Workflow: 4 Steps (3-5 minutes)
 
 ### Step 1: Detect Changes (Automatic - NO confirmation needed)
@@ -27,9 +31,9 @@ Automate commit creation with:
 **Display:**
 
 ```
----
+---
 🔍 Step 1/4: Detecting Changes
----
+---
 ```
 
 **CRITICAL: Execute ALL detection methods in parallel to catch:**
@@ -147,15 +151,15 @@ A  package.json (added, staged)
 ```
 
 **IMPORTANT:** Untracked files (`??`) are NEW files that must be detected with `git status --porcelain` because `get_changed_files()` does NOT see them.
----
+---
 ### Step 2: Intelligent Grouping (Automatic)
 
 **Display:**
 
 ```
----
+---
 ⚡ Step 2/4: Intelligent Grouping
----
+---
 ```
 
 **Analyze files and group by functional relationship.**
@@ -388,15 +392,15 @@ docs/api.md (only this file, no related code)
    ✓ src/modules/users/dto/create-user.dto.ts
    ✓ src/modules/products/dto/create-product.dto.ts
 ```
----
+---
 ### Step 3: Generate Commits (Requires Allow per commit)
 
 **Display:**
 
 ```
----
+---
 ✅ Step 3/4: Creating Commits
----
+---
 [N] commits will be created following Conventional Commits standard.
 
 You will need to click "Allow" for each commit.
@@ -485,9 +489,9 @@ function validateCommitMessage(message: string): boolean {
 **Show each command with `run_in_terminal` and wait for Allow:**
 
 ```
----
+---
 Commit 1/3: Feature Complete
----
+---
 git add src/modules/users/entities/user.entity.ts src/modules/users/dto/create-user.dto.ts src/modules/users/users.service.ts src/modules/users/users.controller.ts src/modules/users/__tests__/users.service.spec.ts docs/api.md && git commit -m "feat(users): implement user management with CRUD operations"
 
 Click "Allow" to execute →
@@ -498,15 +502,15 @@ Click "Allow" to execute →
 ```
 ✅ Commit created: feat(users): implement user management with CRUD operations
 ```
----
+---
 ### Step 4: Finalize (Automatic log + Manual push)
 
 **Display:**
 
 ```
----
+---
 🚀 Step 4/4: Summary & Push
----
+---
 ```
 
 **Automatic (NO confirmation):**
@@ -557,7 +561,7 @@ Error: [error message]
 | Step 4 | `git log` (automatic) + `git push` (manual)                                | Auto log / Allow push  |
 
 **CRITICAL:** Always run `git status --porcelain` in Step 1 to detect untracked files (`??`) that `get_changed_files()` cannot see.
----
+---
 ## 🎯 Execution Model
 
 | Step   | Actions                                                 | User Interaction       |
@@ -566,7 +570,7 @@ Error: [error message]
 | Step 2 | Analyze and group files                                 | Automatic              |
 | Step 3 | `git add` + `git commit` (per group)                    | Click Allow per commit |
 | Step 4 | `git log` (automatic) + `git push` (manual)             | Auto log / Allow push  |
----
+---
 ## 🔍 Pattern Detection Table
 
 Universal patterns that work across languages/frameworks:
@@ -588,7 +592,7 @@ Universal patterns that work across languages/frameworks:
 | **Docs Only**          | Docs (no related code changes)               | `docs`     | doc-topic        | `update [doc-name] documentation`     |
 | **Dependency Update**  | package.json/requirements/go.mod             | `chore`    | deps             | `upgrade [package] to [version]`      |
 | **Build Scripts**      | Makefile/scripts/build config                | `chore`    | build            | `update [build-aspect]`               |
----
+---
 ## 💡 Complex Examples
 
 ### Example 1: Full Feature with Documentation
@@ -697,7 +701,7 @@ spec/models/order_spec.rb
 spec/requests/orders_spec.rb
 → Commit: feat(orders): implement order processing system
 ```
----
+---
 ## ⚠️ Rules & Constraints
 
 ### NEVER
@@ -731,7 +735,7 @@ spec/requests/orders_spec.rb
 - ✅ Show `git push` command and wait for "Allow"
 - ✅ Validate commit messages before executing
 - ✅ Detect project type and adapt scope naming accordingly
----
+---
 ## 📊 Workflow Diagram
 
 ```mermaid
@@ -758,7 +762,7 @@ graph TD
     Q --> S[Done]
     R --> S
 ```
----
+---
 ## 🚀 Error Handling
 
 ### No Changes Detected
@@ -809,13 +813,13 @@ Suggestions:
 3. Try again:
    /flow-dev-commit
 ```
----
+---
 ## 📚 References
 
 - **Conventional Commits:** https://www.conventionalcommits.org/
 - **Git Best Practices:** https://git-scm.com/book/en/v2/Distributed-Git-Contributing-to-a-Project
 - **Atomic Commits:** https://www.freshconsulting.com/insights/blog/atomic-commits/
----
+---
 **Last Updated:** December 11, 2025  
 **Version:** 1.0.0  
 **Maintained by:** AI Flow Team