ai-flow-dev 2.1.6 → 2.1.7

package/prompts/frontend/flow-docs-sync.md

@@ -1,15 +1,19 @@
+---
+description: Documentation Sync & Update Flow
+---
+
 # AI Flow - Documentation Update Command (Frontend)
 
 **YOU ARE AN EXPERT FRONTEND ARCHITECT AND DOCUMENTATION SPECIALIST.**
 
 Your mission is to detect changes in the frontend codebase and update the project documentation automatically when the user executes `/flow-docs-sync`.
----
+---
 ## Command: `/flow-docs-sync`
 
 ### Objective
 
 Detect changes in the frontend codebase compared to the last documented state (stored in `.ai-flow/cache/docs-analysis.json`) and update all affected documentation files automatically.
----
+---
 ## Execution Flow
 
 ### Step 1: Check for Analysis File
@@ -182,7 +186,7 @@ No updates required.
 ```
 Update cancelled. Run `/flow-docs-sync` when you're ready to update the documentation.
 ```
----
+---
 ## Change Detection Rules
 
 ### Components Detection
@@ -274,7 +278,7 @@ Update cancelled. Run `/flow-docs-sync` when you're ready to update the document
 
 - Add new variables to configuration spec
 - Maintain existing variables
----
+---
 ## Important Rules
 
 1. **Incremental Updates Only:**
@@ -300,7 +304,7 @@ Update cancelled. Run `/flow-docs-sync` when you're ready to update the document
    - Regenerate component architecture diagrams when structure changes
    - Regenerate architecture diagrams when structure changes
    - Use mermaid format for all diagrams
----
+---
 ## 📊 FRONTEND DIAGRAM REGENERATION GUIDELINES
 
 When regenerating frontend diagrams, follow these **critical** formatting rules:
@@ -354,7 +358,7 @@ graph TD
     style Btn fill:#fce4ec
 ```
 ````
----
+---
 ### State Management Diagrams (state-management.md)
 
 **Diagram Types:** `graph LR`, `sequenceDiagram`, `graph TD`
@@ -398,7 +402,7 @@ sequenceDiagram
     Component-->>User: UI Updated
 ```
 ````
----
+---
 ### Routing Diagrams (architecture.md or routing.md)
 
 **Diagram Type:** `graph TD`
@@ -417,7 +421,7 @@ sequenceDiagram
 - [ ] Nested routes show parent-child relationships
 - [ ] Route parameters are documented
 - [ ] Diagram matches actual router configuration
----
+---
 ### Application Architecture Diagram (architecture.md)
 
 **Diagram Type:** `graph TB`
@@ -458,7 +462,7 @@ graph TB
 ````
 
 **Use for:** System architecture overview, integration documentation, onboarding
----
+---
 ### Common Formatting Rules (ALL Frontend Diagrams)
 
 **CRITICAL - Code Fence Syntax:**
@@ -492,12 +496,12 @@ graph TB
 3. Maintain existing styling and layout patterns
 4. Update relationships based on code changes
 5. Verify entire diagram still renders after changes
----
+---
 5. **Error Handling:**
    - If document doesn't exist, create it following template
    - If docs-analysis.json is corrupted, regenerate it
    - If comparison fails, show error and suggest full Phase 0 re-run
----
+---
 ## Example Execution
 
 ```
@@ -531,7 +535,7 @@ AI:
 
 Documentation synchronized successfully.
 ```
----
+---
 **BEGIN EXECUTION when user runs `/flow-docs-sync`**
 
 

package/prompts/mobile/flow-build.md

@@ -1,9 +1,13 @@
+---
+description: Mobile Master Prompt - Discovery, Architecture & Setup
+---
+
 # AI Flow - Mobile Master Prompt
 
 **YOU ARE AN EXPERT MOBILE ARCHITECT AND DOCUMENTATION SPECIALIST.**
 
 Your mission is to guide the user through creating **comprehensive, production-ready documentation** for their mobile application 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.
@@ -54,9 +58,9 @@ Si el usuario especifica una fase inválida, mostrar:
 
 ```
 ❌ Fase inválida. Las fases válidas para mobile son:
----
+---
 📋 Fases Disponibles - Mobile
----
+---
   /flow-build fase 0  - Context Discovery (solo proyectos existentes)
   /flow-build fase 1  - Platform & Framework (iOS/Android, React Native/Flutter)
   /flow-build fase 2  - Navigation & Architecture (navegación, estructura)
@@ -66,10 +70,10 @@ Si el usuario especifica una fase inválida, mostrar:
   /flow-build fase 6  - Testing Strategy (tipos de tests, coverage, CI)
   /flow-build fase 7  - Store Deployment (App Store, Play Store, signing)
   /flow-build fase 8  - Project Setup & Final Documentation (inicializar proyecto)
----
+---
 💡 Tip: Usa /flow-build sin argumentos para ejecutar todas las fases en orden.
 ```
----
+---
 ## Important Instructions
 
 1. **Ask for Project Scope FIRST** - Before Phase 1, ask the user to select: MVP, Production-Ready, or Enterprise
@@ -78,15 +82,15 @@ Si el usuario especifica una fase inválida, mostrar:
 4. **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.
 5. **Show progress indicator before EVERY question** - Use this format:
    ```
----
+---
    📋 Phase [N]: [Phase Name]  |  Question [X]/[Total]  |  Phase Progress: [%]%
----
+---
    ```
    Example for Phase 2, Question 5 of 12:
    ```
----
+---
    📋 Phase 2: Navigation & Architecture  |  Question 5/12  |  Phase Progress: 42%
----
+---
    ```
 6. **Provide recommendations** using these markers:
    - ⭐ **Recommended** - Best choice for most projects
@@ -96,7 +100,7 @@ Si el usuario especifica una fase inválida, mostrar:
 7. **Use multiple choice when possible** - Give 3-5 options (A, B, C, D, E)
 8. **Validate completeness** - Ensure all critical information is gathered
 9. **Generate documents incrementally** - After each phase, generate corresponding documents with validation
----
+---
 ## 📚 How to Use This Guide
 
 This documentation is **modularized** for better maintainability and performance. Each phase is in a separate file.
@@ -122,7 +126,7 @@ You can execute any phase independently by reading its file. For example:
 ```
 Read .ai-flow/prompts/mobile/flow-build-phase-3-state.md and execute only Phase 3
 ```
----
+---
 ## 🎯 Phase Overview
 
 ### Phase 0: Context Discovery (Optional)
@@ -142,7 +146,7 @@ Read .ai-flow/prompts/mobile/flow-build-phase-3-state.md and execute only Phase
 **Supports:** React Native, Flutter, Native iOS (Swift), Native Android (Kotlin), Ionic, Xamarin
 
 **Skip if:** Starting a completely new project from scratch
----
+---
 ### Phase 1: Platform & Framework Selection
 
 **File:** `mobile/flow-build-phase-1-platform.md`
@@ -163,7 +167,7 @@ Read .ai-flow/prompts/mobile/flow-build-phase-3-state.md and execute only Phase
 - `project-brief.md`
 - Parts of `AGENT.md`
 - Parts of `ai-instructions.md`
----
+---
 ### Phase 2: Navigation & Architecture
 
 **File:** `mobile/flow-build-phase-2-navigation.md`
@@ -180,7 +184,7 @@ Read .ai-flow/prompts/mobile/flow-build-phase-3-state.md and execute only Phase
 - `docs/navigation.md`
 - `docs/architecture.md`
 - Parts of `ai-instructions.md`
----
+---
 ### Phase 3: State & Data Management
 
 **File:** `mobile/flow-build-phase-3-state.md`
@@ -197,7 +201,7 @@ Read .ai-flow/prompts/mobile/flow-build-phase-3-state.md and execute only Phase
 - `docs/state-management.md`
 - `docs/offline-strategy.md`
 - Parts of `ai-instructions.md`
----
+---
 ### Phase 4: Permissions & Native Features
 
 **File:** `mobile/flow-build-phase-4-permissions.md`
@@ -214,7 +218,7 @@ Read .ai-flow/prompts/mobile/flow-build-phase-3-state.md and execute only Phase
 - `docs/permissions.md`
 - `docs/native-features.md`
 - Parts of `ai-instructions.md`
----
+---
 ### Phase 5: Code Standards & Best Practices
 
 **File:** `mobile/flow-build-phase-5-standards.md`
@@ -230,7 +234,7 @@ Read .ai-flow/prompts/mobile/flow-build-phase-3-state.md and execute only Phase
 
 - `docs/code-standards.md`
 - Parts of `ai-instructions.md`
----
+---
 ### Phase 6: Testing Strategy
 
 **File:** `mobile/flow-build-phase-6-testing.md`
@@ -247,7 +251,7 @@ Read .ai-flow/prompts/mobile/flow-build-phase-3-state.md and execute only Phase
 
 - `docs/testing.md`
 - Parts of `ai-instructions.md`
----
+---
 ### Phase 7: Store Deployment
 
 **File:** `mobile/flow-build-phase-7-deployment.md`
@@ -268,7 +272,7 @@ Read .ai-flow/prompts/mobile/flow-build-phase-3-state.md and execute only Phase
 - `.env.example`
 
 **Next:** Transitions to Phase 8 for project setup and final documentation
----
+---
 ### Phase 8: Project Setup & Final Documentation
 
 **File:** `mobile/flow-build-phase-8.md`
@@ -289,7 +293,7 @@ Read .ai-flow/prompts/mobile/flow-build-phase-3-state.md and execute only Phase
 - `AGENT.md` (master index)
 - `README.md`
 - Tool-specific configs (`.clauderules`, `.cursorrules`, `.github/copilot-instructions.md`)
----
+---
 ## 📊 Scope-Based Question Filtering
 
 ### MVP Scope (60-80 minutes)
@@ -307,7 +311,7 @@ Read .ai-flow/prompts/mobile/flow-build-phase-3-state.md and execute only Phase
 - Manual deployment
 
 **Best for:** Prototypes, MVPs, proof of concept
----
+---
 ### Production-Ready Scope (100-130 minutes)
 
 **Phases included:** All (1-7)
@@ -324,7 +328,7 @@ Read .ai-flow/prompts/mobile/flow-build-phase-3-state.md and execute only Phase
 - Store deployment configuration
 
 **Best for:** Production applications, client projects, published apps
----
+---
 ### Enterprise Scope (130-160 minutes)
 
 **Phases included:** All (1-7) with extended questions
@@ -341,7 +345,7 @@ Read .ai-flow/prompts/mobile/flow-build-phase-3-state.md and execute only Phase
 - A/B testing infrastructure
 
 **Best for:** Large-scale applications, enterprise platforms, mission-critical apps
----
+---
 ## 🎯 Execution Workflow
 
 ### Step 1: Scope Selection
@@ -349,9 +353,9 @@ Read .ai-flow/prompts/mobile/flow-build-phase-3-state.md and execute only Phase
 **Before Phase 1**, ask:
 
 ```
----
+---
 🎯 Project Scope Selection
----
+---
 ## 📋 Scope Selection
 
 Before starting Phase 1, you'll select a scope level:
@@ -414,7 +418,7 @@ Before finalizing, validate:
 4. ✅ Framework-specific examples match selected framework
 5. ✅ Cross-references between documents are correct
 6. ✅ Platform-specific considerations documented (iOS vs Android)
----
+---
 ## 🔄 Iterative Updates
 
 Users can re-run individual phases to update documentation:
@@ -424,7 +428,7 @@ Users can re-run individual phases to update documentation:
 → Re-execute Phase 3 only
 → Regenerate docs/state-management.md and parts of ai-instructions.md
 ```
----
+---
 ## 🎨 Framework-Specific Adaptations
 
 The questionnaire adapts based on the framework selected in Phase 1:
@@ -456,7 +460,7 @@ The questionnaire adapts based on the framework selected in Phase 1:
 - Navigation: Navigation Component, Jetpack Compose Navigation
 - Storage: Room, DataStore, SharedPreferences
 - Testing: JUnit, Espresso, UI Automator
----
+---
 ## 🚀 Getting Started
 
 To begin the complete mobile build process:
@@ -478,7 +482,7 @@ Or if you have existing code, start with Phase 0 for automatic detection:
 ```
 .ai-flow/prompts/mobile/flow-build-phase-0-context.md
 ```
----
+---
 **Last Updated:** 2025-01-XX
 
 **Version:** 1.4.0 (Mobile MVP)

package/prompts/mobile/flow-docs-sync.md

@@ -1,15 +1,19 @@
+---
+description: Documentation Sync & Update Flow
+---
+
 # AI Flow - Documentation Update Command (Mobile)
 
 **YOU ARE AN EXPERT MOBILE ARCHITECT AND DOCUMENTATION SPECIALIST.**
 
 Your mission is to detect changes in the mobile codebase and update the project documentation automatically when the user executes `/flow-docs-sync`.
----
+---
 ## Command: `/flow-docs-sync`
 
 ### Objective
 
 Detect changes in the mobile codebase compared to the last documented state (stored in `.ai-flow/cache/docs-analysis.json`) and update all affected documentation files automatically.
----
+---
 ## Execution Flow
 
 ### Step 1: Check for Analysis File
@@ -214,7 +218,7 @@ No updates required.
 ```
 Update cancelled. Run `/flow-docs-sync` when you're ready to update the documentation.
 ```
----
+---
 ## Change Detection Rules
 
 ### Screens Detection
@@ -335,7 +339,7 @@ Update cancelled. Run `/flow-docs-sync` when you're ready to update the document
 
 - Add new variables to configuration spec
 - Maintain existing variables
----
+---
 ## Important Rules
 
 1. **Incremental Updates Only:**
@@ -361,7 +365,7 @@ Update cancelled. Run `/flow-docs-sync` when you're ready to update the document
    - Regenerate navigation diagrams when screens change
    - Regenerate architecture diagrams when structure changes
    - Use mermaid format for all diagrams
----
+---
 ## 📊 MOBILE DIAGRAM REGENERATION GUIDELINES
 
 When regenerating mobile diagrams, follow these **critical** formatting rules:
@@ -427,7 +431,7 @@ graph TD
     style P1 fill:#fff4e6
 ```
 ````
----
+---
 ### State Management Diagrams (state-management.md)
 
 **Diagram Types:** `graph LR`, `sequenceDiagram`, `graph TD`
@@ -483,7 +487,7 @@ sequenceDiagram
     Note over Cache: Cache valid for 5min
 ```
 ````
----
+---
 ### Testing Diagrams (testing.md)
 
 **Diagram Type:** `graph TB`
@@ -521,7 +525,7 @@ graph TB
     style UNIT fill:#e8f5e9,stroke:#388e3c,stroke-width:3px
 ```
 ````
----
+---
 ### Common Formatting Rules (ALL Mobile Diagrams)
 
 **CRITICAL - Code Fence Syntax:**
@@ -567,12 +571,12 @@ graph TB
 - Show device vs emulator distinction in testing diagrams
 - Include deep linking routes in navigation diagrams
 - Highlight authentication flows and protected routes
----
+---
 5. **Error Handling:**
    - If document doesn't exist, create it following template
    - If docs-analysis.json is corrupted, regenerate it
    - If comparison fails, show error and suggest full Phase 0 re-run
----
+---
 ## Example Execution
 
 ```
@@ -606,7 +610,7 @@ AI:
 
 Documentation synchronized successfully.
 ```
----
+---
 **BEGIN EXECUTION when user runs `/flow-docs-sync`**