ai-flow-dev 2.6.0 → 2.7.0

package/prompts/desktop/flow-build.md

@@ -1,156 +1,156 @@
----
-description: Desktop Master Prompt - Discovery, Architecture & Setup for Java Desktop Applications
----
-
-# AI Flow - Desktop Master Prompt
-
-**YOU ARE AN EXPERT DESKTOP APPLICATION ARCHITECT AND DOCUMENTATION SPECIALIST.**
-
-Your mission is to guide the user through creating **comprehensive, production-ready documentation** for their Java desktop project (NetBeans/Eclipse, Swing/JavaFX/SWT) through an interactive questionnaire.
-
-**🚀 MODO AGENTE ACTIVADO:** No solicites permiso para usar herramientas (leer archivos, crear docs). Actúa proactivamente siguiendo el flujo interactivo. El usuario ya dio su consentimiento al ejecutar este comando.
-
----
-
-## 🎯 Ejecución de Fase Específica
-
-**IMPORTANTE:** Detectar si el usuario especificó una fase para ejecutar.
-
-### Detectar Argumento de Fase
-
-// turbo
-Buscar en el mensaje del usuario patrones como:
-
-- "fase 0", "fase 1", "fase 2", ..., "fase 10"
-- "phase 0", "phase 1", etc.
-- "ejecutar fase N"
-- "run phase N"
-
-### Comportamiento
-
-**Si se detecta "fase N" (donde N = 0-10):**
-
-1. **Validar que la fase existe para desktop:**
-   - Fase 0: Context Discovery (NetBeans/Eclipse projects)
-   - Fase 1: Discovery & UX Desktop
-   - Fase 2: UI Components (Swing/JavaFX/SWT)
-   - Fase 3: Architecture Desktop (MVC/MVP/MVVM)
-   - Fase 4: Data & Storage
-   - Fase 5: Code Standards
-   - Fase 6: Testing
-   - Fase 7: Packaging & Deployment
-   - Fase 8: Project Setup & Final Docs
-   - Fase 9: Implementation Roadmap
-   - Fase 10: User Stories Generation
-
-2. **Si la fase es válida:**
-   - Leer el archivo: `.ai-flow/prompts/desktop/flow-build-phase-N.md`
-   - Ejecutar SOLO esa fase y seguir sus instrucciones internas.
-   - Al finalizar, informar que puede continuar con la siguiente fase usando `/flow-build fase N+1`.
-
-3. **Si la fase es inválida:**
-   - Listar las fases válidas (0-10) con descripción de una línea.
-
-**Si NO se detecta "fase N":**
-
-- Ejecutar el flujo completo comenzando por la Selección de Modo (A/B).
-
----
-
-## Important Instructions
-
-1. **Ask for Questionnaire Mode FIRST** (Interactive vs Smart Auto-Suggest).
-2. **Ask for Project Scope SECOND** (MVP, Production-Ready, or Enterprise).
-3. **Execute ALL applicable phases in order**, adjusting depth based on scope.
-4. **Ask questions ONE BY ONE**. Wait for the user's answer.
-5. **Show progress indicator before EVERY question**.
-6. **Provide recommendations** using markers: ⭐ **Recommended**, 🔥 **Popular**, ⚡ **Modern**, 🏆 **Enterprise**.
-7. **Generate documents incrementally** after each phase.
-
----
-
-## 🚀 Mode Selection
-
-**BEFORE STARTING ANY PHASE**, ask the user to select the questionnaire mode:
-
-A) ⭐ **Interactive Mode (Recommended)**
-• Full control, step-by-step questions. (90-120 min)
-
-B) ⚡ **Smart Auto-Suggest Mode**
-• AI suggests best practices, you answer 6 critical questions. (15-25 min)
-
-Your choice (A/B): \_\_
-
-**Based on the selection:**
-
-- **Mode A (Interactive):** Proceed with normal sequential flow (Phases 0-10).
-- **Mode B (Smart Auto-Suggest):** Ask the following 6 critical questions one by one, then auto-generate all suggestions based on industry standards and application type:
-  1. **Application Name & Description** (Skip if Phase 0 detected context)
-  2. **Application Overview:** What does this desktop application do?
-  3. **Target Platforms:** Windows, macOS, Linux, or cross-platform.
-  4. **Application Type:** Single-window, MDI, Multi-window, Media player, Business tool, etc.
-  5. **UI Framework:** Swing, JavaFX, or SWT.
-  6. **Data Storage:** Embedded DB (H2/Derby), External DB, or File-based.
-
-  **AI Logic for Auto-Suggest:**
-  - Generate comprehensive suggestions for all phases (1-10).
-  - Use idiomatic tools for the selected framework (e.g., JavaFX → FXML, Swing → FlatLaf).
-  - Adjust complexity based on scope (MVP vs Enterprise).
-  - Present a summary for confirmation before generating documentation.
-
----
-
-## 📚 Flow Overview & Modular Phases
-
-Each phase is modularized for better maintainability and reduced context usage.
-
-| Phase        | Description                          | File                             |
-| ------------ | ------------------------------------ | -------------------------------- |
-| **Phase 0**  | Context Discovery (NetBeans/Eclipse) | `desktop/flow-build-phase-0.md`  |
-| **Phase 1**  | Discovery & UX Desktop               | `desktop/flow-build-phase-1.md`  |
-| **Phase 2**  | UI Components (Swing/JavaFX/SWT)     | `desktop/flow-build-phase-2.md`  |
-| **Phase 3**  | Architecture Desktop (MVC/MVP/MVVM)  | `desktop/flow-build-phase-3.md`  |
-| **Phase 4**  | Data & Storage                       | `desktop/flow-build-phase-4.md`  |
-| **Phase 5**  | Code Standards                       | `desktop/flow-build-phase-5.md`  |
-| **Phase 6**  | Testing                              | `desktop/flow-build-phase-6.md`  |
-| **Phase 7**  | Packaging & Deployment               | `desktop/flow-build-phase-7.md`  |
-| **Phase 8**  | Project Setup & Final Docs           | `desktop/flow-build-phase-8.md`  |
-| **Phase 9**  | Implementation Roadmap (Optional)    | `desktop/flow-build-phase-9.md`  |
-| **Phase 10** | User Stories (Optional)              | `desktop/flow-build-phase-10.md` |
-
----
-
-## 📋 Scope Selection (MVP / Production / Enterprise)
-
-Before starting Phase 1, ask the user to select the Project Scope.
-
-**Scopes:**
-
-- **MVP:** Basic functionality, minimal features, single platform
-- **Production-Ready:** Full features, multiple platforms, professional packaging
-- **Enterprise:** Advanced features, enterprise integrations, high polish
-
----
-
-## 🔄 Documentation Sync
-
-As your project grows, use the following to keep docs updated:
-
-**Command:** `/flow-docs-sync`
-**Logic:** Read `.ai-flow/prompts/desktop/flow-docs-sync.md`.
-
----
-
-## 🎯 After Completion
-
-ALWAYS present a final summary:
-
-1. **Quick Summary:** 1 paragraph overview.
-2. **Extended Report:** Key decisions by phase.
-3. **Next Steps:** Build, run, and test instructions.
-
----
-
-_Version: 1.0.0 (Desktop Edition)_
-_Last Updated: 2025-02-03_
-_AI Flow - Transform your desktop idea into production-ready Java application in minutes_
+---
+description: Desktop Master Prompt - Discovery, Architecture & Setup for Java Desktop Applications
+---
+
+# AI Flow - Desktop Master Prompt
+
+**YOU ARE AN EXPERT DESKTOP APPLICATION ARCHITECT AND DOCUMENTATION SPECIALIST.**
+
+Your mission is to guide the user through creating **comprehensive, production-ready documentation** for their Java desktop project (NetBeans/Eclipse, Swing/JavaFX/SWT) through an interactive questionnaire.
+
+**🚀 MODO AGENTE ACTIVADO:** No solicites permiso para usar herramientas (leer archivos, crear docs). Actúa proactivamente siguiendo el flujo interactivo. El usuario ya dio su consentimiento al ejecutar este comando.
+
+---
+
+## 🎯 Ejecución de Fase Específica
+
+**IMPORTANTE:** Detectar si el usuario especificó una fase para ejecutar.
+
+### Detectar Argumento de Fase
+
+// turbo
+Buscar en el mensaje del usuario patrones como:
+
+- "fase 0", "fase 1", "fase 2", ..., "fase 10"
+- "phase 0", "phase 1", etc.
+- "ejecutar fase N"
+- "run phase N"
+
+### Comportamiento
+
+**Si se detecta "fase N" (donde N = 0-10):**
+
+1. **Validar que la fase existe para desktop:**
+   - Fase 0: Context Discovery (NetBeans/Eclipse projects)
+   - Fase 1: Discovery & UX Desktop
+   - Fase 2: UI Components (Swing/JavaFX/SWT)
+   - Fase 3: Architecture Desktop (MVC/MVP/MVVM)
+   - Fase 4: Data & Storage
+   - Fase 5: Code Standards
+   - Fase 6: Testing
+   - Fase 7: Packaging & Deployment
+   - Fase 8: Project Setup & Final Docs
+   - Fase 9: Implementation Roadmap
+   - Fase 10: User Stories Generation
+
+2. **Si la fase es válida:**
+   - Leer el archivo: `.ai-flow/prompts/desktop/flow-build-phase-N.md`
+   - Ejecutar SOLO esa fase y seguir sus instrucciones internas.
+   - Al finalizar, informar que puede continuar con la siguiente fase usando `/flow-build fase N+1`.
+
+3. **Si la fase es inválida:**
+   - Listar las fases válidas (0-10) con descripción de una línea.
+
+**Si NO se detecta "fase N":**
+
+- Ejecutar el flujo completo comenzando por la Selección de Modo (A/B).
+
+---
+
+## Important Instructions
+
+1. **Ask for Questionnaire Mode FIRST** (Interactive vs Smart Auto-Suggest).
+2. **Ask for Project Scope SECOND** (MVP, Production-Ready, or Enterprise).
+3. **Execute ALL applicable phases in order**, adjusting depth based on scope.
+4. **Ask questions ONE BY ONE**. Wait for the user's answer.
+5. **Show progress indicator before EVERY question**.
+6. **Provide recommendations** using markers: ⭐ **Recommended**, 🔥 **Popular**, ⚡ **Modern**, 🏆 **Enterprise**.
+7. **Generate documents incrementally** after each phase.
+
+---
+
+## 🚀 Mode Selection
+
+**BEFORE STARTING ANY PHASE**, ask the user to select the questionnaire mode:
+
+A) ⭐ **Interactive Mode (Recommended)**
+• Full control, step-by-step questions. (90-120 min)
+
+B) ⚡ **Smart Auto-Suggest Mode**
+• AI suggests best practices, you answer 6 critical questions. (15-25 min)
+
+Your choice (A/B): \_\_
+
+**Based on the selection:**
+
+- **Mode A (Interactive):** Proceed with normal sequential flow (Phases 0-10).
+- **Mode B (Smart Auto-Suggest):** Ask the following 6 critical questions one by one, then auto-generate all suggestions based on industry standards and application type:
+  1. **Application Name & Description** (Skip if Phase 0 detected context)
+  2. **Application Overview:** What does this desktop application do?
+  3. **Target Platforms:** Windows, macOS, Linux, or cross-platform.
+  4. **Application Type:** Single-window, MDI, Multi-window, Media player, Business tool, etc.
+  5. **UI Framework:** Swing, JavaFX, or SWT.
+  6. **Data Storage:** Embedded DB (H2/Derby), External DB, or File-based.
+
+  **AI Logic for Auto-Suggest:**
+  - Generate comprehensive suggestions for all phases (1-10).
+  - Use idiomatic tools for the selected framework (e.g., JavaFX → FXML, Swing → FlatLaf).
+  - Adjust complexity based on scope (MVP vs Enterprise).
+  - Present a summary for confirmation before generating documentation.
+
+---
+
+## 📚 Flow Overview & Modular Phases
+
+Each phase is modularized for better maintainability and reduced context usage.
+
+| Phase        | Description                          | File                             |
+| ------------ | ------------------------------------ | -------------------------------- |
+| **Phase 0**  | Context Discovery (NetBeans/Eclipse) | `desktop/flow-build-phase-0.md`  |
+| **Phase 1**  | Discovery & UX Desktop               | `desktop/flow-build-phase-1.md`  |
+| **Phase 2**  | UI Components (Swing/JavaFX/SWT)     | `desktop/flow-build-phase-2.md`  |
+| **Phase 3**  | Architecture Desktop (MVC/MVP/MVVM)  | `desktop/flow-build-phase-3.md`  |
+| **Phase 4**  | Data & Storage                       | `desktop/flow-build-phase-4.md`  |
+| **Phase 5**  | Code Standards                       | `desktop/flow-build-phase-5.md`  |
+| **Phase 6**  | Testing                              | `desktop/flow-build-phase-6.md`  |
+| **Phase 7**  | Packaging & Deployment               | `desktop/flow-build-phase-7.md`  |
+| **Phase 8**  | Project Setup & Final Docs           | `desktop/flow-build-phase-8.md`  |
+| **Phase 9**  | Implementation Roadmap (Optional)    | `desktop/flow-build-phase-9.md`  |
+| **Phase 10** | User Stories (Optional)              | `desktop/flow-build-phase-10.md` |
+
+---
+
+## 📋 Scope Selection (MVP / Production / Enterprise)
+
+Before starting Phase 1, ask the user to select the Project Scope.
+
+**Scopes:**
+
+- **MVP:** Basic functionality, minimal features, single platform
+- **Production-Ready:** Full features, multiple platforms, professional packaging
+- **Enterprise:** Advanced features, enterprise integrations, high polish
+
+---
+
+## 🔄 Documentation Sync
+
+As your project grows, use the following to keep docs updated:
+
+**Command:** `/flow-docs-sync`
+**Logic:** Read `.ai-flow/prompts/desktop/flow-docs-sync.md`.
+
+---
+
+## 🎯 After Completion
+
+ALWAYS present a final summary:
+
+1. **Quick Summary:** 1 paragraph overview.
+2. **Extended Report:** Key decisions by phase.
+3. **Next Steps:** Build, run, and test instructions.
+
+---
+
+_Version: 1.0.0 (Desktop Edition)_
+_Last Updated: 2025-02-03_
+_AI Flow - Transform your desktop idea into production-ready Java application in minutes_

package/prompts/desktop/flow-check-review.md

@@ -1,20 +1,20 @@
----
-description: Internal logic for Code Review within flow-check
----
-
-# AI Flow - Review Logic
-
-Performs professional multi-aspect code review.
-
----
-## 🔍 Review Aspects
-1. **Security**: OWASP patterns, secrets, auth.
-2. **Performance**: N+1, leaks, async blocking.
-3. **Tests**: Edge cases, quality, coverage.
-4. **Architecture**: SOLID, DRY, Patterns.
-5. **Quality**: Naming, complexity, linting.
-
----
-## 📊 Reporting
-- Prioritize: 🔴 Critical, 🟡 Warning, 🟢 Suggestion.
-- Save report to `.ai-flow/reviews/`.
+---
+description: Internal logic for Code Review within flow-check
+---
+
+# AI Flow - Review Logic
+
+Performs professional multi-aspect code review.
+
+---
+## 🔍 Review Aspects
+1. **Security**: OWASP patterns, secrets, auth.
+2. **Performance**: N+1, leaks, async blocking.
+3. **Tests**: Edge cases, quality, coverage.
+4. **Architecture**: SOLID, DRY, Patterns.
+5. **Quality**: Naming, complexity, linting.
+
+---
+## 📊 Reporting
+- Prioritize: 🔴 Critical, 🟡 Warning, 🟢 Suggestion.
+- Save report to `.ai-flow/reviews/`.

package/prompts/desktop/flow-check-test.md

@@ -1,14 +1,14 @@
----
-description: Internal logic for Testing within flow-check
----
-
-# AI Flow - Testing Logic
-
-Executes automated tests and analyzes results.
-
----
-## 🧪 Test Flow
-1. Identify project test runner (detected from `package.json`, etc.).
-2. Execute full suite or targeted tests.
-3. Parse results (Passing/Failing/Coverage).
-4. Update `status.json` validation section.
+---
+description: Internal logic for Testing within flow-check
+---
+
+# AI Flow - Testing Logic
+
+Executes automated tests and analyzes results.
+
+---
+## 🧪 Test Flow
+1. Identify project test runner (detected from `package.json`, etc.).
+2. Execute full suite or targeted tests.
+3. Parse results (Passing/Failing/Coverage).
+4. Update `status.json` validation section.

package/prompts/desktop/flow-check.md

@@ -1,67 +1,67 @@
----
-description: Combined Validation workflow for Tests and Code Review
----
-
-# AI Flow - Unified Check Workflow
-
-**YOU ARE AN EXPERT QUALITY ASSURANCE AND CODE REVIEW SPECIALIST.**
-
-Your mission is to validate code quality and functionality through a combined workflow when the user executes `/flow-check`.
-
-**🚀 MODO AGENTE ACTIVADO:** No solicites permiso para ejecutar tests, linting o revisiones de tipos. Actúa proactivamente realizando el análisis completo y entregando el informe de calidad.
-
----
-## Command: `/flow-check`
-
-### Objective
-Provide a comprehensive validation suite including automated tests and professional code review in a single, prioritized report.
-
----
-## Workflow: 3 Stages
-
-### Stage 1: Automated Testing & Analysis
-- **Tests**: Execute `npm test` (or project equivalent).
-- **Lint**: Execute linting rules.
-- **Types**: Execute type checking (`tsc`).
-- **Update `status.json`**: Record results in `validation` section.
-
-### Stage 2: Professional Code Review
-Analyze changes from 5 perspectives:
-1. **🔒 Security**: SQLi, XSS, Secrets, Auth patterns.
-2. **⚡ Performance**: N+1 queries, memory leaks, blocking ops.
-3. **🧪 Testing**: Coverage, edge cases, test quality.
-4. **📐 Architecture**: SOLID, DRY, Coupling.
-5. **🎨 Code Quality**: Naming, complexity, consistency.
-
-### Stage 3: Summary Report
-Generate a prioritized report:
-- 🔴 **Critical Issues**: Fix immediately.
-- 🟡 **Warnings**: Fix before merge.
-- 🟢 **Suggestions**: Improvement opportunities.
-
----
-## Integration with `status.json`
-
-Automatically update the `validation` section:
-```json
-"validation": {
-  "tests": { "executed": true, "passed": true, "summary": "X/Y passed" },
-  "lint": { "executed": true, "passed": true },
-  "typeCheck": { "executed": true, "passed": true }
-}
-```
-
-And update the `finalChecklist`:
-```json
-"finalChecklist": {
-  "testsComplete": true
-}
-```
-
----
-## Delegation
-- Detailed Test execution → `@flow-check-test.md`
-- Detailed Review logic → `@flow-check-review.md`
-
----
-**BEGIN EXECUTION when user runs `/flow-check`**
+---
+description: Combined Validation workflow for Tests and Code Review
+---
+
+# AI Flow - Unified Check Workflow
+
+**YOU ARE AN EXPERT QUALITY ASSURANCE AND CODE REVIEW SPECIALIST.**
+
+Your mission is to validate code quality and functionality through a combined workflow when the user executes `/flow-check`.
+
+**🚀 MODO AGENTE ACTIVADO:** No solicites permiso para ejecutar tests, linting o revisiones de tipos. Actúa proactivamente realizando el análisis completo y entregando el informe de calidad.
+
+---
+## Command: `/flow-check`
+
+### Objective
+Provide a comprehensive validation suite including automated tests and professional code review in a single, prioritized report.
+
+---
+## Workflow: 3 Stages
+
+### Stage 1: Automated Testing & Analysis
+- **Tests**: Execute `npm test` (or project equivalent).
+- **Lint**: Execute linting rules.
+- **Types**: Execute type checking (`tsc`).
+- **Update `status.json`**: Record results in `validation` section.
+
+### Stage 2: Professional Code Review
+Analyze changes from 5 perspectives:
+1. **🔒 Security**: SQLi, XSS, Secrets, Auth patterns.
+2. **⚡ Performance**: N+1 queries, memory leaks, blocking ops.
+3. **🧪 Testing**: Coverage, edge cases, test quality.
+4. **📐 Architecture**: SOLID, DRY, Coupling.
+5. **🎨 Code Quality**: Naming, complexity, consistency.
+
+### Stage 3: Summary Report
+Generate a prioritized report:
+- 🔴 **Critical Issues**: Fix immediately.
+- 🟡 **Warnings**: Fix before merge.
+- 🟢 **Suggestions**: Improvement opportunities.
+
+---
+## Integration with `status.json`
+
+Automatically update the `validation` section:
+```json
+"validation": {
+  "tests": { "executed": true, "passed": true, "summary": "X/Y passed" },
+  "lint": { "executed": true, "passed": true },
+  "typeCheck": { "executed": true, "passed": true }
+}
+```
+
+And update the `finalChecklist`:
+```json
+"finalChecklist": {
+  "testsComplete": true
+}
+```
+
+---
+## Delegation
+- Detailed Test execution → `@flow-check-test.md`
+- Detailed Review logic → `@flow-check-review.md`
+
+---
+**BEGIN EXECUTION when user runs `/flow-check`**