ai-flow-dev 2.1.6 → 2.1.8

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-phase-1.md

@@ -1,22 +1,131 @@
 # Phase 1: Discovery & UX Requirements
 
 **Duration:** 15-20 minutes
-**Questions:** ~10 questions
+**Questions:** ~11 questions
 **Output:** project-brief.md, parts of AGENT.md
----
+---
 ## 🎯 Objective
 
-Understand the **user-facing aspects** of the application:
+Understand the **user-facing aspects** and core goal of the application:
 
-1. What type of application is being built?
-2. Who are the target users?
-3. What are the key user journeys?
-4. What devices and browsers must be supported?
-5. What are the UX priorities?
----
+1. What is the core goal and purpose of the project?
+2. What type of application is being built?
+3. Who are the target users?
+4. What are the key user journeys?
+5. What devices and browsers must be supported?
+6. What are the UX priorities?
+---
 ## 📋 Questions
 
-### Question 1.1: Application Type
+### Question 1.1: Project Name & Description (with Smart Refinement)
+
+> **🧠 Intelligent Refinement System**: This question detects vague descriptions and guides the developer to enrich them. It only asks what's missing and responds in the developer's language.
+
+```
+What is the project name?
+
+Provide an initial description of your project.
+(Don't worry about perfection - we'll refine it together if needed!)
+
+Example: "A frontend dashboard for managing inventory in real-time"
+```
+
+**🔍 AI Internal: Ambiguity Analysis**
+
+After receiving the description, silently analyze for these criteria:
+
+| Criterion | Check For | Score +1 if present |
+|-----------|-----------|---------------------|
+| **WHO** | Specific user type mentioned (not just "users") | "store managers", "traders", "students" |
+| **WHAT** | Specific action/function (not just "view", "show") | "compare prices", "edit profiles", "visualize data" |
+| **WHY** | Purpose or value mentioned | "to increase conversion", "to save time", "to improve UX" |
+| **DOMAIN** | Industry/vertical indicated | "fintech", "e-commerce", "social media" |
+| **DETAIL** | Description has 10+ meaningful words | Not counting articles |
+
+**Scoring Rules:**
+- Score 4-5: ✅ Accept immediately → Proceed to 1.2
+- Score 0-3: ⚠️ Enter refinement loop → Ask ONLY missing criteria
+
+---
+
+**🔄 Conditional Refinement Loop (only if score < 4)**
+
+> **CRITICAL**: Only ask about criteria that are MISSING. Do NOT repeat questions already answered. Respond in the SAME LANGUAGE the developer used.
+
+```
+[LANGUAGE: Match the developer's language]
+
+🔍 I'd like to understand your project better.
+
+Your description: "[original description]"
+
+[ONLY show questions for MISSING criteria:]
+
+[If WHO is missing:]
+1️⃣ WHO will use this application?
+   A) End consumers (B2C)
+   B) Business users (B2B)
+   C) Internal team / Admin
+   D) Other: __
+
+[If WHAT is missing:]
+2️⃣ WHAT is the core UX action users will perform?
+   A) Browse & Shop
+   B) Manage & Configure
+   C) Read & Consume
+   D) Create & Publish
+   E) Analyze & Visualize
+   F) Other: __
+
+[If WHY is missing:]
+3️⃣ WHY is this project needed?
+   A) Launch new product
+   B) Replace legacy UI
+   C) Better mobile experience
+   D) Specific new feature
+   E) Other: __
+
+[If DOMAIN is missing:]
+4️⃣ What INDUSTRY/DOMAIN is this for?
+   A) E-commerce/Retail
+   B) Fitness/Health
+   C) Finance/Payments
+   D) Education
+   E) Social/Community
+   F) Business tools (CRM, ERP)
+   G) Other: __
+
+Your answers: __
+```
+
+---
+
+**✨ Generate Professional Description Options**
+
+After gathering missing info, generate 3 polished versions:
+
+```
+[LANGUAGE: Match the developer's language]
+
+✨ Based on your input, here are 3 professional descriptions:
+
+A) Concise (for package.json):
+   "[Generated 1-line description]"
+
+B) Descriptive (for README.md):
+   "[Generated 2-3 line description with UX focus]"
+
+C) Creative (for Marketing/Landing):
+   "[Generated catchy description]"
+
+Which do you prefer? (1-3, or 4 to edit, 5 to start over)
+```
+
+**Your choice:**
+
+---
+
+### Question 1.2: Application Type
 
 **What type of frontend application are you building?**
 
@@ -51,10 +160,26 @@ E) **Static Site (SSG)**
 - Best for: Blogs, documentation, landing pages
 
 **Your answer:**
----
-### Question 1.2: Target Users
+---
+### Question 1.3: Target Users (Confirmation + Expansion)
+
+```
+[If WHO was captured in 1.1, show:]
+
+✅ Based on your description, your target users are: [WHO from 1.1]
+
+Describe your user personas more deeply (3-5 bullet points):
+
+- Demographics (age, tech-savviness, etc.)
+- Use cases / goals
+- Device preferences
+- Accessibility needs
 
-**Who are your primary target users?**
+---
+
+[If WHO was NOT captured in 1.1, ask normally:]
+
+Who are your primary target users?
 
 Describe your user personas (3-5 bullet points):
 
@@ -62,6 +187,7 @@ Describe your user personas (3-5 bullet points):
 - Use cases / goals
 - Device preferences
 - Accessibility needs
+```
 
 **Example:**
 
@@ -73,12 +199,22 @@ Describe your user personas (3-5 bullet points):
 ```
 
 **Your answer:**
----
-### Question 1.3: Key User Journeys
+---
+### Question 1.4: Key User Journeys (Confirmation + Expansion)
+
+```
+[If WHAT was captured in 1.1, show:]
+
+✅ Based on your description, a core journey is: [WHAT from 1.1]
+
+What are the 3-5 most critical user flows?
 
-**What are the 3-5 most critical user flows?**
+---
 
-List the core journeys users will take through your app.
+[If WHAT was NOT captured in 1.1, ask normally:]
+
+What are the 3-5 most critical user flows?
+```
 
 **Example:**
 
@@ -90,8 +226,8 @@ List the core journeys users will take through your app.
 ```
 
 **Your answer:**
----
-### Question 1.4: Device & Browser Support
+---
+### Question 1.5: Device & Browser Support
 
 **What devices and browsers must you support?**
 
@@ -122,8 +258,8 @@ D) **Desktop-First**
 - Best for: Admin panels, dashboards, B2B tools
 
 **Your answer:**
----
-### Question 1.5: Responsive Strategy
+---
+### Question 1.6: Responsive Strategy
 
 **How will you handle different screen sizes?**
 
@@ -150,8 +286,8 @@ D) **Fixed Width (Desktop Only)**
 - Best for: Internal tools, admin panels (desktop-only users)
 
 **Your answer:**
----
-### Question 1.6: Internationalization (i18n)
+---
+### Question 1.7: Internationalization (i18n)
 
 **Do you need multi-language support?**
 
@@ -180,8 +316,8 @@ D) **Right-to-Left (RTL) Support**
 **Your answer:**
 
 **If multi-language selected, list target languages:**
----
-### Question 1.7: Authentication Requirements
+---
+### Question 1.8: Authentication Requirements
 
 **What authentication method will you use?**
 
@@ -219,8 +355,8 @@ F) **No Authentication**
 - Best for: Marketing sites, public tools
 
 **Your answer:**
----
-### Question 1.8: Data Privacy & Compliance
+---
+### Question 1.9: Data Privacy & Compliance
 
 **What data privacy requirements do you have?**
 
@@ -257,8 +393,8 @@ F) **Multiple Regulations**
 - Most restrictive controls apply
 
 **Your answer:**
----
-### Question 1.9: Offline Support
+---
+### Question 1.10: Offline Support
 
 **Do users need offline access?**
 
@@ -287,8 +423,8 @@ D) **Offline-First**
 - Best for: Mobile apps, unreliable networks
 
 **Your answer:**
----
-### Question 1.10: Performance Priorities
+---
+### Question 1.11: Performance Priorities
 
 **What are your performance priorities?** (Select top 3)
 
@@ -327,25 +463,27 @@ F) **Perceived Performance**
 - Best for: User experience
 
 **Your answer (top 3):**
----
+---
 ## 📊 Phase 1 Summary
 
 Before proceeding to Phase 2, confirm the following:
 
 ```
----
+---
 📋 PHASE 1 SUMMARY: DISCOVERY & UX
----
-Application Type: [Answer from 1.1]
-Target Users: [Answer from 1.2]
-Key User Journeys: [Answer from 1.3]
-Device/Browser Support: [Answer from 1.4]
-Responsive Strategy: [Answer from 1.5]
-Internationalization: [Answer from 1.6]
-Authentication: [Answer from 1.7]
-Data Privacy: [Answer from 1.8]
-Offline Support: [Answer from 1.9]
-Performance Priorities: [Answer from 1.10]
+---
+Project Name: [Answer from 1.1]
+Project Description: [Answer from 1.1]
+Application Type: [Answer from 1.2]
+Target Users: [Answer from 1.3]
+Key User Journeys: [Answer from 1.4]
+Device/Browser Support: [Answer from 1.5]
+Responsive Strategy: [Answer from 1.6]
+Internationalization: [Answer from 1.7]
+Authentication: [Answer from 1.8]
+Data Privacy: [Answer from 1.9]
+Offline Support: [Answer from 1.10]
+Performance Priorities: [Answer from 1.11]
 
 Is this correct? (Y/n)
 ```
@@ -353,7 +491,7 @@ Is this correct? (Y/n)
 If **Yes:** Proceed to Phase 2
 
 If **No:** Allow user to correct specific answers
----
+---
 ## 📝 Document Generation (Partial)
 
 At the end of Phase 1, generate or update:
@@ -439,7 +577,7 @@ At the end of Phase 1, generate or update:
 - Authentication: {{AUTH_METHOD}}
 - Compliance: {{DATA_PRIVACY_COMPLIANCE}}
 ```
----
+---
 ## 🚀 Next Steps
 
 ```
@@ -453,11 +591,7 @@ Next: Phase 2 - Components & Framework
 
 Read: .ai-flow/prompts/frontend/flow-build-phase-2-components.md
 ```
----
-**Last Updated:** 2025-01-XX
-
-**Version:** 1.2.0
-
-
-
+---
+**Last Updated:** 2025-12-XX
 
+**Version:** 1.3.0

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)