ai-flow-dev 2.1.6 → 2.1.7

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

@@ -1,9 +1,13 @@
+---
+description: General Development Task Flow
+---
+
 # AI Flow - Work Management
 
 **YOU ARE AN EXPERT PROJECT MANAGER AND WORKFLOW COORDINATOR.**
 
 Your mission is to manage work in progress, resume interrupted work, and archive completed work when the user executes `/work`.
----
+---
 ## Command: `/work`
 
 ### Objective
@@ -21,7 +25,7 @@ Manage work in progress efficiently:
 - **`/work show [name]`** → Show details of specific task
 - **`/work resume [name]`** → Resume paused work
 - **`/work archive [name]`** → Archive completed work
----
+---
 ## Workflow: `/work` (List Active Work)
 
 ### Step 1: Scan Work Directory
@@ -52,9 +56,9 @@ E) Exit
 **Example output:**
 
 ```
----
+---
 📋 Work Management
----
+---
 Active work in .ai-flow/work/:
 
 1. 🚀 feature-notifications
@@ -82,7 +86,7 @@ Active work in .ai-flow/work/:
    Branch: refactor/auth-cleanup
    Started: 2025-01-20 11:00
    Last updated: 2025-01-20 11:05
----
+---
 What would you like to do?
 A) Show details of a task
 B) Resume a task
@@ -90,7 +94,7 @@ C) Archive a task
 D) Clean up (archive all completed)
 E) Exit
 ```
----
+---
 ## Workflow: `/work show [name]`
 
 ### Step 1: Read Task Files
@@ -125,9 +129,9 @@ C) Back to list
 **Example output:**
 
 ```
----
+---
 📄 Task Details: feature-notifications
----
+---
 **Overview:**
 Real-time notification system using WebSockets
 
@@ -171,13 +175,13 @@ Real-time notification system using WebSockets
 - src/routes/index.ts (registered routes)
 
 **Next step:** Update API documentation (task 13/18)
----
+---
 What would you like to do?
 A) Resume this task
 B) Archive this task
 C) Back to list
 ```
----
+---
 ## Workflow: `/work resume [name]`
 
 ### Step 1: Load Complete Context
@@ -235,9 +239,9 @@ git checkout feature/notifications-websocket
 **Read previous mode from `status.json` and suggest as default:**
 
 ```
----
+---
 ⚙️  Resume Implementation Mode
----
+---
 Previous mode: Phase-by-phase
 Progress: 12/18 tasks (67%)
 Remaining: 6 tasks (Phase 2: 3 tasks left, Phase 3: 3 tasks)
@@ -267,9 +271,9 @@ Execute based on selected mode:
 Continue automatically until all tasks complete:
 
 ```
----
+---
 ⚙️  Resuming: feature-notifications (Auto Mode)
----
+---
 Loading context...
 ✅ Read spec.md, plan.md, tasks.md
 ✅ Analyzed completed code (12/18 tasks done)
@@ -291,9 +295,9 @@ All tasks completed! ✅
 Continue phase by phase with pauses:
 
 ```
----
+---
 ⚙️  Resuming: feature-notifications (Phase-by-phase Mode)
----
+---
 Loading context...
 ✅ Read spec.md, plan.md, tasks.md
 ✅ Phase 1 already complete (10/10 tasks)
@@ -304,9 +308,9 @@ Task 2.3: Create EmailService ✅
 Task 2.4: Implement password hashing ✅
 ...
 Task 2.15: Add error handling ✅
----
+---
 ✅ Phase 2 Complete (15/15 tasks)
----
+---
 Continue to Phase 3? (Y/n/pause)
 > Y
 ```
@@ -316,9 +320,9 @@ Continue to Phase 3? (Y/n/pause)
 Ask for confirmation before each task:
 
 ```
----
+---
 ⚙️  Resuming: feature-notifications (Task-by-task Mode)
----
+---
 Loading context...
 ✅ Loaded context (12/18 tasks complete)
 
@@ -334,9 +338,9 @@ Proceed? (Y/n/skip/pause)
 Save progress and exit without changes:
 
 ```
----
+---
 💾 Progress Saved
----
+---
 Current progress: 12/18 tasks (67%)
 Status: Paused
 
@@ -351,7 +355,7 @@ No changes made. To resume: /work resume feature-notifications
   - Current progress
   - Last task completed
   - Reason for pause (if paused)
----
+---
 ## Workflow: `/work archive [name]`
 
 ### Step 1: Verify Completion
@@ -442,9 +446,9 @@ Create final summary with:
 **Example output:**
 
 ```
----
+---
 🗄️  Archiving: feature-notifications
----
+---
 ✅ All 18 tasks completed
 ✅ All tests passed
 ✅ All changes committed
@@ -456,9 +460,9 @@ Updating documentation...
 ✅ Updated docs/api.md (added 3 endpoints)
 ✅ Updated docs/data-model.md (added Notification entity)
 ✅ Updated .env.example (added REDIS_URL)
----
+---
 📦 Git Summary
----
+---
 Branch: feature/notifications-websocket (from main)
 Commits: 4
 
@@ -472,7 +476,7 @@ Tests added: 24
 All validations passed ✅
 
 🚀 Ready to create Pull Request
----
+---
 Suggested PR command:
 
 gh pr create \
@@ -484,9 +488,9 @@ Or open in browser:
 https://github.com/yourorg/yourrepo/compare/main...feature/notifications-websocket
 
 ⚠️  Note: PR creation is manual. Review commits before creating PR.
----
+---
 ✅ Archive Complete!
----
+---
 Summary:
 - Feature: Real-time notifications with WebSockets
 - 8 files created, 2 modified
@@ -497,7 +501,7 @@ Summary:
 
 Archived: .ai-flow/archive/2025-01/feature-notifications/
 ```
----
+---
 ## Clean Up (Archive All Completed)
 
 When user selects "D) Clean up":
@@ -511,9 +515,9 @@ When user selects "D) Clean up":
 **Example output:**
 
 ```
----
+---
 🗄️  Cleanup: Archive All Completed
----
+---
 Found 2 completed tasks:
 - feature-user-profile (18/18 tasks)
 - fix-validation-error (6/6 tasks)
@@ -529,13 +533,13 @@ Archiving feature-user-profile...
 Archiving fix-validation-error...
 ✅ Moved to archive
 ✅ No docs to update (bug fix)
----
+---
 ✅ Cleanup Complete!
----
+---
 Archived 2 tasks
 .ai-flow/work/ is now clean
 ```
----
+---
 ## Git Integration
 
 ### Overview
@@ -689,7 +693,7 @@ What would you like to do? (1/2/3/4)
 
 ```bash
 🔧 Commit remaining changes
----
+---
 Pre-commit validation:
   ✓ Lint passed
   ✓ Type check passed
@@ -726,9 +730,9 @@ Proceeding with archive...
 When archiving, show comprehensive Git summary:
 
 ```bash
----
+---
 📦 Git Summary
----
+---
 Branch: feature/notifications-websocket
 Source: main
 Commits: 5 (all committed ✅)
@@ -749,7 +753,7 @@ All validations passed ✅
 No uncommitted changes ✅
 
 🚀 Ready to create Pull Request
----
+---
 Suggested PR command:
 
 gh pr create \
@@ -894,9 +898,9 @@ git checkout feature/notifications-websocket
 # Switched to branch 'feature/notifications-websocket'
 
 ✅ On correct branch. Loading context...
----
+---
 ⚙️  Resume Implementation Mode
----
+---
 Feature: Real-time notifications
 Progress: 12/18 tasks (67%)
 Previous mode: Phase-by-phase
@@ -948,7 +952,7 @@ Work management inherits Git strategy from original command:
 | `/refactor-quick` | Single commit at end, current branch, no PR                  |
 
 **Key principle:** Resume doesn't change strategy, only continues it.
----
+---
 ## Important Rules
 
 ### 1. Context Preservation
@@ -996,16 +1000,16 @@ When archiving:
 - After archiving, work/ should only have active work
 - Archive/ organizes by year-month
 - Easy to find historical work
----
+---
 ## Example: Complete Resume Flow
 
 ### User paused a complex feature after Phase 1:
 
 ```
 User runs: /work resume feature-auth-system
----
+---
 ⚙️  Resume Implementation Mode
----
+---
 Loading context...
 ✅ Read spec.md, plan.md, tasks.md, status.json
 ✅ Analyzed completed code
@@ -1025,9 +1029,9 @@ How do you want to continue?
 4. 💾 Save progress and exit again
 
 Your choice (2): 2
----
+---
 ⚙️  Resuming: feature-auth-system (Phase-by-phase Mode)
----
+---
 PHASE 2/5: Business Logic
 
 Task 2.1: Create AuthService ✅
@@ -1045,9 +1049,9 @@ Task 2.12: Error handling for auth ✅
 Task 2.13: Input validation schemas ✅
 Task 2.14: Business rule enforcement ✅
 Task 2.15: Service integration tests ✅
----
+---
 ✅ Phase 2 Complete (15/15 tasks)
----
+---
 📁 Files created:
 - src/services/AuthService.ts
 - src/services/TokenService.ts
@@ -1059,9 +1063,9 @@ Overall progress: 25/52 tasks (48%)
 
 Continue to Phase 3? (Y/n/pause)
 > pause
----
+---
 💾 Progress Saved
----
+---
 Current progress: 25/52 tasks (48%)
 Completed: Phases 1-2
 Next: Phase 3 - API Layer
@@ -1069,7 +1073,7 @@ Status: Paused after Phase 2 completion
 
 To resume: /work resume feature-auth-system
 ```
----
+---
 **BEGIN EXECUTION when user runs `/work`, `/work show [name]`, `/work resume [name]`, or `/work archive [name]`**
 
 

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

@@ -1,15 +1,19 @@
+---
+description: Documentation Sync & Update Flow
+---
+
 # AI Flow - Documentation Update Command
 
 **YOU ARE AN EXPERT TECHNICAL ARCHITECT AND DOCUMENTATION SPECIALIST.**
 
 Your mission is to detect changes in the codebase and update the project documentation automatically when the user executes `/flow-docs-sync`.
----
+---
 ## Command: `/flow-docs-sync`
 
 ### Objective
 
 Detect changes in the 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
@@ -78,7 +82,7 @@ First, check if `.ai-flow/cache/docs-analysis.json` exists:
 
 No se requiere ninguna actualización.
 ```
----
+---
 ## 📊 MERMAID DIAGRAM REGENERATION GUIDELINES
 
 > 📎 **Reference:** See [prompts/shared/mermaid-guidelines.md](../shared/mermaid-guidelines.md) for all Mermaid diagram formatting rules (ER, Architecture, Flow).
@@ -86,20 +90,20 @@ No se requiere ninguna actualización.
 ### ER Diagrams (data-model.md)
 
 > 📎 **Reference:** See [prompts/shared/mermaid-guidelines.md](../shared/mermaid-guidelines.md) for ER diagram syntax, relationship notation, and common mistakes.
----
+---
 ### Architecture Diagrams (architecture.md)
 
 > 📎 **Reference:** See [prompts/shared/mermaid-guidelines.md](../shared/mermaid-guidelines.md) for architecture diagram syntax, node shapes, and styling.
----
----
+---
+---
 ### Business Flow Diagrams (project-brief.md)
 
 > 📎 **Reference:** See [prompts/shared/mermaid-guidelines.md](../shared/mermaid-guidelines.md) for business flow syntax, decision points, and styling.
----
+---
 ### Common Formatting Rules (ALL Diagrams)
 
 > 📎 **Reference:** See [prompts/shared/mermaid-guidelines.md](../shared/mermaid-guidelines.md) for critical code fence syntax and indentation rules.
----
+---
 - Do NOT indent the entire code block
 
 **Validation Steps:**
@@ -118,7 +122,7 @@ No se requiere ninguna actualización.
 4. Add new elements in logical positions
 5. Preserve comments or notes if present
 6. Verify the entire diagram still renders after changes
----
+---
 ### Step 4: Update Documents (If User Confirms)
 
 **If user responds "Y", "Yes", "y", "yes", or similar:**
@@ -201,7 +205,7 @@ No se requiere ninguna actualización.
 ```
 Actualización cancelada. Ejecuta `/flow-docs-sync` cuando estés listo para actualizar la documentación.
 ```
----
+---
 ## Change Detection Rules
 
 ### Endpoints Detection
@@ -280,7 +284,7 @@ Actualización cancelada. Ejecuta `/flow-docs-sync` cuando estés listo para act
 - Add new variables to configuration spec
 - Add examples to `.env.example`
 - Maintain existing variables
----
+---
 ## Important Rules
 
 1. **Incremental Updates Only:**
@@ -307,7 +311,7 @@ Actualización cancelada. Ejecuta `/flow-docs-sync` cuando estés listo para act
    - 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
 
 ```
@@ -341,7 +345,7 @@ AI:
 
 Documentación sincronizada exitosamente.
 ```
----
+---
 **BEGIN EXECUTION when user runs `/flow-docs-sync`**
 
 

package/prompts/frontend/flow-build.md

@@ -1,9 +1,13 @@
+---
+description: Frontend Master Prompt - Discovery, Architecture & Setup
+---
+
 # AI Flow - Frontend Master Prompt
 
 **YOU ARE AN EXPERT FRONTEND ARCHITECT AND DOCUMENTATION SPECIALIST.**
 
 Your mission is to guide the user through creating **comprehensive, production-ready documentation** for their frontend 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.
@@ -54,9 +58,9 @@ Si el usuario especifica una fase inválida, mostrar:
 
 ```
 ❌ Fase inválida. Las fases válidas para frontend son:
----
+---
 📋 Fases Disponibles - Frontend
----
+---
   /flow-build fase 0  - Context Discovery (solo proyectos existentes)
   /flow-build fase 1  - Discovery & UX (tipo de app, usuarios, journeys)
   /flow-build fase 2  - Components & Framework (React/Vue/Angular, 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  - Performance & Deployment (optimización, deployment)
   /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: Components & Framework  |  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/frontend/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/frontend/flow-build-phase-3-state.md and execute only Phas
 **Supports:** React, Vue, Angular, Svelte, Solid + meta-frameworks (Next.js, Nuxt, SvelteKit, etc.)
 
 **Skip if:** Starting a completely new project from scratch
----
+---
 ### Phase 1: Discovery & UX Requirements
 
 **File:** `frontend/flow-build-phase-1-discovery.md`
@@ -158,7 +162,7 @@ Read .ai-flow/prompts/frontend/flow-build-phase-3-state.md and execute only Phas
 
 - `project-brief.md`
 - Parts of `AGENT.md`
----
+---
 ### Phase 2: Components & Framework
 
 **File:** `frontend/flow-build-phase-2-components.md`
@@ -175,7 +179,7 @@ Read .ai-flow/prompts/frontend/flow-build-phase-3-state.md and execute only Phas
 - `docs/components.md`
 - `docs/architecture.md`
 - Parts of `ai-instructions.md`
----
+---
 ### Phase 3: State Management
 
 **File:** `frontend/flow-build-phase-3-state.md`
@@ -191,7 +195,7 @@ Read .ai-flow/prompts/frontend/flow-build-phase-3-state.md and execute only Phas
 
 - `docs/state-management.md`
 - Parts of `ai-instructions.md`
----
+---
 ### Phase 4: Styling & Design System
 
 **File:** `frontend/flow-build-phase-4-styling.md`
@@ -207,7 +211,7 @@ Read .ai-flow/prompts/frontend/flow-build-phase-3-state.md and execute only Phas
 
 - `docs/styling.md`
 - Parts of `ai-instructions.md`
----
+---
 ### Phase 5: Code Standards & Best Practices
 
 **File:** `frontend/flow-build-phase-5-standards.md`
@@ -223,7 +227,7 @@ Read .ai-flow/prompts/frontend/flow-build-phase-3-state.md and execute only Phas
 
 - `docs/code-standards.md`
 - Parts of `ai-instructions.md`
----
+---
 ### Phase 6: Testing Strategy
 
 **File:** `frontend/flow-build-phase-6-testing.md`
@@ -239,7 +243,7 @@ Read .ai-flow/prompts/frontend/flow-build-phase-3-state.md and execute only Phas
 
 - `docs/testing.md`
 - Parts of `ai-instructions.md`
----
+---
 ### Phase 7: Performance & Deployment
 
 **File:** `frontend/flow-build-phase-7-deployment.md`
@@ -259,7 +263,7 @@ Read .ai-flow/prompts/frontend/flow-build-phase-3-state.md and execute only Phas
 - `.env.example`
 
 **Next:** Transitions to Phase 8 for project setup and final documentation
----
+---
 ### Phase 8: Project Setup & Final Documentation
 
 **File:** `frontend/flow-build-phase-8.md`
@@ -280,7 +284,7 @@ Read .ai-flow/prompts/frontend/flow-build-phase-3-state.md and execute only Phas
 - `AGENT.md` (master index)
 - `README.md`
 - Tool-specific configs (`.clauderules`, `.cursorrules`, `.github/copilot-instructions.md`)
----
+---
 ## 📊 Scope-Based Question Filtering
 
 ### MVP Scope (50-70 minutes)
@@ -296,7 +300,7 @@ Read .ai-flow/prompts/frontend/flow-build-phase-3-state.md and execute only Phas
 - Basic testing (smoke tests only)
 
 **Best for:** Proof of concept, prototypes, MVPs
----
+---
 ### Production-Ready Scope (90-120 minutes)
 
 **Phases included:** All (1-7)
@@ -311,7 +315,7 @@ Read .ai-flow/prompts/frontend/flow-build-phase-3-state.md and execute only Phas
 - Deployment pipeline
 
 **Best for:** Production applications, SaaS products, client projects
----
+---
 ### Enterprise Scope (120-150 minutes)
 
 **Phases included:** All (1-7) with extended questions
@@ -327,7 +331,7 @@ Read .ai-flow/prompts/frontend/flow-build-phase-3-state.md and execute only Phas
 - Advanced monitoring and observability
 
 **Best for:** Large-scale applications, enterprise platforms, mission-critical systems
----
+---
 ## 🎯 Execution Workflow
 
 ### Step 1: Scope Selection
@@ -335,9 +339,9 @@ Read .ai-flow/prompts/frontend/flow-build-phase-3-state.md and execute only Phas
 **Before Phase 1**, ask:
 
 ```
----
+---
 🎯 Project Scope Selection
----
+---
 ## 📋 Scope Selection
 
 Before starting Phase 1, you'll select a scope level:
@@ -396,7 +400,7 @@ Before finalizing, validate:
 3. ✅ No contradictions between documents
 4. ✅ Framework-specific examples match selected framework
 5. ✅ Cross-references between documents are correct
----
+---
 ## 🔄 Iterative Updates
 
 Users can re-run individual phases to update documentation:
@@ -406,7 +410,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 UI framework selected in Phase 2:
@@ -445,7 +449,7 @@ The questionnaire adapts based on the UI framework selected in Phase 2:
 - Forms: Modular Forms
 - Styling: Tailwind, Solid Styled
 - Testing: Solid Testing Library
----
+---
 ## 🚀 Getting Started
 
 To begin the complete frontend build process:
@@ -467,7 +471,7 @@ Or if you have existing code, start with Phase 0 for automatic detection:
 ```
 .ai-flow/prompts/frontend/flow-build-phase-0-context.md
 ```
----
+---
 **Last Updated:** 2025-01-XX
 
 **Version:** 1.2.0 (Frontend MVP)