ai-flow-dev 2.1.2 → 2.1.4

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

@@ -3,9 +3,7 @@
 **Duration:** 15-20 minutes
 **Questions:** ~12 questions
 **Output:** docs/app-store.md, specs/build-configuration.md, specs/deployment.md, parts of ai-instructions.md
-
----
-
+---
 ## 🎯 Objective
 
 Define your app store deployment strategy:
@@ -15,9 +13,7 @@ Define your app store deployment strategy:
 3. How will you handle versioning?
 4. What code signing strategy?
 5. What beta testing approach?
-
----
-
+---
 ## 📋 Questions
 
 ### Question 7.1: Target App Stores
@@ -48,9 +44,7 @@ D) **Enterprise Distribution Only**
 - Best for: Enterprise apps
 
 **Your answer:**
-
----
-
+---
 ### Question 7.2: CI/CD Pipeline
 
 **What CI/CD tool will you use for builds and deployment?**
@@ -86,9 +80,7 @@ E) **Manual Builds**
 - Best for: Learning, small projects
 
 **Your answer:**
-
----
-
+---
 ### Question 7.3: Versioning Strategy
 
 **How will you version your app?**
@@ -122,9 +114,7 @@ C) **Build Number Only**
 
 - A) ⭐ **Incrementing integer** (1, 2, 3, ...)
 - B) **Based on version** (e.g., 1.2.3 → 10203)
-
----
-
+---
 ### Question 7.4: Code Signing Strategy
 
 **How will you handle code signing?**
@@ -132,7 +122,6 @@ C) **Build Number Only**
 **For iOS:**
 
 - A) ⭐ **Automatic Signing** (Recommended)
-
   - Xcode manages certificates
   - Easier for most developers
   - Best for: Most apps
@@ -145,7 +134,6 @@ C) **Build Number Only**
 **For Android:**
 
 - A) ⭐ **Automatic Signing** (Recommended)
-
   - Gradle manages keystores
   - Easier for most developers
   - Best for: Most apps
@@ -160,16 +148,13 @@ C) **Build Number Only**
 **Keystore management:**
 
 - A) ⭐ **Store in CI/CD secrets** (Recommended)
-
   - GitHub Secrets, Bitrise Secrets, etc.
   - Secure, automated
 
 - B) **Store locally**
   - Manual management
   - Best for: Small teams
-
----
-
+---
 ### Question 7.5: Beta Testing Strategy
 
 **How will you handle beta testing?**
@@ -203,9 +188,7 @@ E) **No Beta Testing**
 - Best for: MVPs, internal apps
 
 **Your answer:**
-
----
-
+---
 ### Question 7.6: Release Strategy
 
 **What release strategy will you use?**
@@ -228,9 +211,7 @@ C) **Full Release**
 - Best for: Small updates, bug fixes
 
 **Your answer:**
-
----
-
+---
 ### Question 7.7: App Store Metadata
 
 **What metadata will you prepare for stores?**
@@ -251,9 +232,7 @@ C) **Full Release**
 - [ ] Feature graphic (Android)
 
 **Your answer:**
-
----
-
+---
 ### Question 7.8: Screenshot Automation
 
 **Will you automate screenshot generation?**
@@ -275,9 +254,7 @@ C) **No - Manual Screenshots**
 - Best for: Small teams, infrequent updates
 
 **Your answer:**
-
----
-
+---
 ### Question 7.9: App Review Preparation
 
 **How will you prepare for app review?**
@@ -301,9 +278,7 @@ C) **No - Manual Screenshots**
 - [ ] Test in internal testing first
 
 **Your answer:**
-
----
-
+---
 ### Question 7.10: Update Frequency
 
 **How often will you release updates?**
@@ -329,9 +304,7 @@ D) **Monthly**
 - Best for: Stable apps
 
 **Your answer:**
-
----
-
+---
 ### Question 7.11: Rollback Strategy
 
 **How will you handle rollbacks?**
@@ -352,9 +325,7 @@ C) **No Rollback Plan**
 - Best for: Very small apps
 
 **Your answer:**
-
----
-
+---
 ### Question 7.12: Monitoring & Analytics
 
 **What monitoring will you use post-deployment?**
@@ -381,18 +352,15 @@ D) **Custom Analytics**
 - Best for: Advanced analytics
 
 **Your answer:**
-
----
-
+---
 ## ✅ Phase 7 Completion
 
 After answering all questions, summarize:
 
 ```
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+---
 ✅ Phase 7 Complete: Store Deployment
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
+---
 Selected Deployment Strategy:
 - Stores: {{TARGET_STORES}}
 - CI/CD: {{CICD_PIPELINE}}
@@ -407,9 +375,7 @@ Generated Documents:
 ✅ specs/build-configuration.md
 ✅ specs/deployment.md
 ✅ .env.example
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
+---
 📊 Progress Summary:
 
 Phases 1-7 completed:
@@ -426,11 +392,9 @@ Phases 1-7 completed:
 
 Remaining:
 ⏭️  Phase 8: Project setup & final documentation
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+---
 🎯 Next: Phase 8 - Project Setup & Final Documentation
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
+---
 Phase 8 will:
 - 🔍 Detect project state (new vs existing)
 - 🚀 Initialize framework (optional, for new projects)
@@ -441,9 +405,11 @@ Phase 8 will:
 
 Continue to Phase 8? (yes/no)
 ```
-
----
-
+---
 **Last Updated:** 2025-12-09
 
 **Version:** 2.0.0 (Unified workflow with Phase 8)
+
+
+
+

package/prompts/mobile/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
 
 ```
@@ -56,9 +52,7 @@ Found:
 
 Recommendation: [Next action based on state]
 ```
-
----
-
+---
 ## 8.2: Framework Initialization (Optional)
 
 **Only if:** Project state = "New Project"
@@ -215,9 +209,7 @@ You can initialize manually later with:
 
 Proceeding to documentation generation...
 ```
-
----
-
+---
 ## 8.3: Generate Final Documentation
 
 ```
@@ -299,9 +291,7 @@ Generating...
 ```
 ✅ Generated: docs/contributing.md
 ```
-
----
-
+---
 ## 8.3.4: Generate .gitignore
 
 **IMPORTANT:** Generate a comprehensive `.gitignore` file based on the mobile framework selected in previous phases.
@@ -458,9 +448,7 @@ Thumbs.db
 ✅ Generated: .gitignore
    Patterns included: [React Native | Flutter] + Platform-specific
 ```
-
----
-
+---
 ## 8.4: Generate AGENT.md (Master Index)
 
 - **Template:** `.ai-flow/templates/AGENT.template.md`
@@ -545,9 +533,7 @@ Thumbs.db
 ```
 ✅ Generated: .ai-flow/AGENT.md (Master Index)
 ```
-
----
-
+---
 ## 8.5: Generate README.md (Intelligent Merge)
 
 - **Template:** `.ai-flow/templates/README.template.md`
@@ -590,9 +576,7 @@ Thumbs.db
 ✅ Generated: .ai-flow/README.md
    [If merged] Merged with framework's setup instructions
 ```
-
----
-
+---
 ## 8.6: Create Tool-Specific Configs
 
 **Based on AI tool selection from Phase 1:**
@@ -706,9 +690,7 @@ Master index: `.ai-flow/AGENT.md`
 ✅ Generated tool-specific configs:
    [List generated files based on selection]
 ```
-
----
-
+---
 ## 8.7: Final Validation & Success Message
 
 ```
@@ -767,9 +749,7 @@ Phase 8:
 
 Tool-specific configs:
 ✅ [List generated configs]
-
----
-
+---
 📁 Project Structure:
 
 your-app/
@@ -797,9 +777,7 @@ your-app/
 ├── .env.example
 ├── .gitignore
 └── [tool configs]               # .clauderules, .cursorrules, etc.
-
----
-
+---
 Next steps:
 
 1. ⭐ **Read `.ai-flow/AGENT.md`** - Master index of all documentation
@@ -817,9 +795,7 @@ Next steps:
    • Android: `npm run android` or `flutter run`
 6. 💾 **Initialize git** (if not done) - `git init && git add . && git commit -m "Initial commit with AI Flow docs"`
 7. 🧪 **Start developing!** - Your AI assistant now has complete project context
-
----
-
+---
 💡 **Remember:**
 - Documents are **living artifacts** - update them as project evolves
 - All AI assistants will reference these docs for future work
@@ -836,9 +812,7 @@ Your AI assistant (Claude, Cursor, Copilot) will now:
 
 Happy building! 🎉📱
 ```
-
----
-
+---
 ## EXECUTION CHECKLIST FOR AI ASSISTANT
 
 When executing Phase 8:
@@ -894,9 +868,10 @@ When executing Phase 8:
 - [ ] Show success message
 
 **ESTIMATED TIME:** 10-15 minutes
-
----
-
+---
 **CONTINUE TO:** End (Phase 8 is final phase)
 
 **SUCCESS:** Mobile app fully documented and ready for development! 🚀📱
+
+
+

package/prompts/mobile/flow-build.md

@@ -3,9 +3,7 @@
 **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.
@@ -56,11 +54,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)
@@ -70,14 +66,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
@@ -86,15 +78,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
@@ -104,9 +96,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.
@@ -132,9 +122,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)
@@ -154,9 +142,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`
@@ -177,9 +163,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`
@@ -196,9 +180,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`
@@ -215,9 +197,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`
@@ -234,9 +214,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`
@@ -252,9 +230,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`
@@ -271,9 +247,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`
@@ -294,9 +268,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`
@@ -317,9 +289,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)
@@ -337,9 +307,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)
@@ -356,9 +324,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
@@ -375,9 +341,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
@@ -385,33 +349,23 @@ Read .ai-flow/prompts/mobile/flow-build-phase-3-state.md and execute only Phase
 **Before Phase 1**, ask:
 
 ```
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+---
 🎯 Project Scope Selection
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-What scope level do you want for this documentation?
-
-A) 🚀 **MVP** (60-80 min) - Core features only, minimal setup
-   - Phases 1-4 (core questions)
-   - Single platform
-   - Basic navigation and state
-   - Minimal testing
-   - Best for: Prototypes, proof of concept
-
-B) ⭐ **Production-Ready** (100-130 min) - Complete professional setup
-   - All phases 1-7
-   - Multi-platform support
-   - Full tech stack
-   - Comprehensive testing
-   - CI/CD pipeline
-   - Best for: Production apps, published apps
-
-C) 🏆 **Enterprise** (130-160 min) - Advanced features and scalability
-   - All phases with extended questions
-   - Advanced architecture
-   - Complex offline sync
-   - Advanced security
-   - Best for: Large-scale, mission-critical apps
+---
+## 📋 Scope Selection
+
+Before starting Phase 1, you'll select a scope level:
+
+> 📎 **Reference:** See [prompts/shared/scope-levels.md](../shared/scope-levels.md) for detailed scope definitions (MVP, Production-Ready, Enterprise).
+
+### A) ⭐ MVP / Prototype
+**Focus:** Core functionality + basic tests. Best for POCs and internal tools.
+
+### B) 🚀 Production-Ready
+**Focus:** Production-grade with best practices. Best for SaaS and customer-facing apps.
+
+### C) 🏢 Enterprise / Mission-Critical
+**Focus:** Enterprise governance, compliance, and high scalability.
 
 Your choice (A/B/C):
 ```
@@ -460,9 +414,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:
@@ -472,9 +424,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:
@@ -506,9 +456,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:
@@ -530,9 +478,11 @@ 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)
+
+
+
+