ai-flow-dev 2.1.7 β 2.1.9
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +18 -13
- package/dist/cli.js +9 -8
- package/dist/cli.js.map +1 -1
- package/package.json +1 -1
- package/prompts/backend/flow-build-phase-0.md +57 -39
- package/prompts/backend/flow-build-phase-1.md +209 -18
- package/prompts/backend/flow-build-phase-10.md +25 -9
- package/prompts/backend/flow-build-phase-2.md +20 -2
- package/prompts/backend/flow-build-phase-3.md +19 -0
- package/prompts/backend/flow-build-phase-4.md +26 -3
- package/prompts/backend/flow-build-phase-5.md +20 -1
- package/prompts/backend/flow-build-phase-6.md +22 -2
- package/prompts/backend/flow-build-phase-7.md +24 -263
- package/prompts/backend/flow-build-phase-8.md +106 -47
- package/prompts/backend/flow-build-phase-9.md +61 -12
- package/prompts/backend/flow-build.md +34 -7
- package/prompts/frontend/flow-build-phase-1.md +187 -53
- package/prompts/mobile/flow-build-phase-1.md +196 -62
- package/templates/AGENT.template.md +1 -1
|
@@ -1,17 +1,12 @@
|
|
|
1
|
-
|
|
1
|
+
## PHASE 9: Implementation Roadmap (5-10 min)
|
|
2
2
|
|
|
3
|
-
**
|
|
3
|
+
> **Order for this phase:** OPTIONAL. Executed after Phase 8 or on demand.
|
|
4
4
|
|
|
5
|
-
|
|
5
|
+
> **π Scope-based behavior:**
|
|
6
|
+
> - **All Scopes:** Generate a complete Implementation Roadmap with atomic tasks.
|
|
6
7
|
|
|
7
|
-
|
|
8
|
-
|
|
9
|
-
- Phase 8 completed (all documentation generated)
|
|
10
|
-
- Files exist: `docs/data-model.md`, `docs/api.md`, `docs/architecture.md`, `specs/security.md`
|
|
11
|
-
|
|
12
|
-
## Duration: 60-90 minutes
|
|
13
|
-
|
|
14
|
-
---
|
|
8
|
+
### Objective
|
|
9
|
+
Translate all architectural and business specifications into a prioritized, actionable implementation plan (Roadmap) with clear milestones and tasks.
|
|
15
10
|
|
|
16
11
|
## Context Variables (Extract from docs)
|
|
17
12
|
|
|
@@ -409,5 +404,59 @@ PHASE 9 COMPLETE
|
|
|
409
404
|
βββ Coverage: 100% (all components have [E][R][S][C][T][D])
|
|
410
405
|
βββ Ready for: /flow-dev-feature
|
|
411
406
|
|
|
412
|
-
Next: Open docs/roadmap.md and start with EP-000
|
|
407
|
+
Next: Open docs/roadmap.md and start with EP-000, or continue to Phase 10 for detailed User Stories.
|
|
408
|
+
|
|
409
|
+
**OFFER PHASE 10:**
|
|
410
|
+
|
|
411
|
+
```
|
|
412
|
+
---
|
|
413
|
+
β
PHASE 9 COMPLETE: IMPLEMENTATION ROADMAP GENERATED
|
|
414
|
+
---
|
|
415
|
+
π― Roadmap created in docs/roadmap.md
|
|
416
|
+
π Total Story Points: {{SP}}
|
|
417
|
+
ποΈ Epics defined: {{EPICS_COUNT}}
|
|
418
|
+
---
|
|
419
|
+
π Optional: Generate Detailed User Stories?
|
|
420
|
+
---
|
|
421
|
+
Phase 10 will convert your roadmap features into detailed User Stories with:
|
|
422
|
+
|
|
423
|
+
β
Gherkin-style Acceptance Criteria (Given/When/Then)
|
|
424
|
+
β
Functional, Error, Edge, and Security scenarios
|
|
425
|
+
β
Technical details inherited from patterns
|
|
426
|
+
β
Ready-to-use QA Test Cases with data
|
|
427
|
+
β
Definition of Done (DoD) checklist
|
|
428
|
+
|
|
429
|
+
β±οΈ Estimated time: 30-60 minutes
|
|
430
|
+
|
|
431
|
+
Would you like to continue to Phase 10?
|
|
432
|
+
|
|
433
|
+
A) β
Yes, generate User Stories now (recommended)
|
|
434
|
+
β Best for Sprint planning and QA alignment
|
|
435
|
+
β Will generate {{FEATURES_COUNT}} User Stories
|
|
436
|
+
|
|
437
|
+
B) βοΈ Skip for now (you can run Phase 10 later)
|
|
438
|
+
β You can start coding directly from roadmap
|
|
439
|
+
β Run Phase 10 anytime: /flow-build fase 10
|
|
440
|
+
|
|
441
|
+
Your choice (A/B): __
|
|
413
442
|
```
|
|
443
|
+
|
|
444
|
+
---
|
|
445
|
+
|
|
446
|
+
## π Generated Documents
|
|
447
|
+
|
|
448
|
+
After Phase 9, generate/update:
|
|
449
|
+
|
|
450
|
+
- `docs/roadmap.md` - Technical implementation plan
|
|
451
|
+
|
|
452
|
+
---
|
|
453
|
+
|
|
454
|
+
**Next Phase:** Phase 10 - Agile Planning (User Stories)
|
|
455
|
+
|
|
456
|
+
Read: `.ai-flow/prompts/backend/flow-build-phase-10.md`
|
|
457
|
+
|
|
458
|
+
---
|
|
459
|
+
|
|
460
|
+
**Last Updated:** 2025-12-20
|
|
461
|
+
**Version:** 2.1.8
|
|
462
|
+
|
|
@@ -16,14 +16,14 @@ Your mission is to guide the user through creating **comprehensive, production-r
|
|
|
16
16
|
|
|
17
17
|
Buscar en el mensaje del usuario patrones como:
|
|
18
18
|
|
|
19
|
-
- "fase 0", "fase 1", "fase 2", ..., "fase
|
|
19
|
+
- "fase 0", "fase 1", "fase 2", ..., "fase 10"
|
|
20
20
|
- "phase 0", "phase 1", etc.
|
|
21
21
|
- "ejecutar fase N"
|
|
22
22
|
- "run phase N"
|
|
23
23
|
|
|
24
24
|
### Comportamiento
|
|
25
25
|
|
|
26
|
-
**Si se detecta "fase N" (donde N = 0-
|
|
26
|
+
**Si se detecta "fase N" (donde N = 0-10):**
|
|
27
27
|
|
|
28
28
|
1. **Validar que la fase existe para backend:**
|
|
29
29
|
- Fase 0: Context Discovery (opcional, solo proyectos existentes)
|
|
@@ -36,6 +36,7 @@ Buscar en el mensaje del usuario patrones como:
|
|
|
36
36
|
- Fase 7: Operations & Deployment
|
|
37
37
|
- Fase 8: Project Setup & Final Documentation
|
|
38
38
|
- Fase 9: Implementation Roadmap (opcional)
|
|
39
|
+
- Fase 10: User Stories Generation (opcional)
|
|
39
40
|
|
|
40
41
|
2. **Si la fase es vΓ‘lida:**
|
|
41
42
|
- Leer el archivo: `.ai-flow/prompts/backend/flow-build-phase-N.md`
|
|
@@ -45,14 +46,14 @@ Buscar en el mensaje del usuario patrones como:
|
|
|
45
46
|
|
|
46
47
|
3. **Si la fase es invΓ‘lida:**
|
|
47
48
|
- Mostrar mensaje de error amigable
|
|
48
|
-
- Listar las fases vΓ‘lidas (0-
|
|
49
|
+
- Listar las fases vΓ‘lidas (0-10) con descripciΓ³n de una lΓnea
|
|
49
50
|
|
|
50
51
|
**Si NO se detecta "fase N":**
|
|
51
52
|
|
|
52
53
|
- Ejecutar el flujo completo normal (todas las fases en orden)
|
|
53
54
|
- Comenzar con Mode Selection (Interactive vs Smart Auto-Suggest)
|
|
54
55
|
- Continuar con Scope Selection (MVP/Production-Ready/Enterprise)
|
|
55
|
-
- Ejecutar Phases 0-
|
|
56
|
+
- Ejecutar Phases 0-10 segΓΊn corresponda
|
|
56
57
|
|
|
57
58
|
### Ejemplo de Lista de Fases VΓ‘lidas
|
|
58
59
|
|
|
@@ -73,6 +74,7 @@ Si el usuario especifica una fase invΓ‘lida, mostrar:
|
|
|
73
74
|
/flow-build fase 7 - Operations & Deployment (deployment, monitoreo, logging)
|
|
74
75
|
/flow-build fase 8 - Project Setup & Final Documentation (inicializar proyecto)
|
|
75
76
|
/flow-build fase 9 - Implementation Roadmap (plan con Story Points - opcional)
|
|
77
|
+
/flow-build fase 10 - User Stories Generation (Gherkin AC & Test Cases - opcional)
|
|
76
78
|
---
|
|
77
79
|
π‘ Tip: Usa /flow-build sin argumentos para ejecutar todas las fases en orden.
|
|
78
80
|
```
|
|
@@ -368,6 +370,8 @@ Execute phases sequentially by reading each file in order:
|
|
|
368
370
|
7. **Phase 6 (Testing Strategy):** Read `.ai-flow/prompts/backend/flow-build-phase-6-testing.md`
|
|
369
371
|
8. **Phase 7 (Operations & Deployment):** Read `.ai-flow/prompts/backend/flow-build-phase-7-operations.md`
|
|
370
372
|
9. **Phase 8 (Project Setup & Final Documentation):** Read `.ai-flow/prompts/backend/flow-build-phase-8.md`
|
|
373
|
+
10. **Phase 9 (Implementation Roadmap):** Read `.ai-flow/prompts/backend/flow-build-phase-9.md`
|
|
374
|
+
11. **Phase 10 (User Stories Generation):** Read `.ai-flow/prompts/backend/flow-build-phase-10.md`
|
|
371
375
|
|
|
372
376
|
### For Individual Phases
|
|
373
377
|
|
|
@@ -565,6 +569,26 @@ Read .ai-flow/prompts/backend/flow-build-phase-4-security.md and execute only Ph
|
|
|
565
569
|
|
|
566
570
|
**Skip if:** You prefer to start coding immediately without a detailed roadmap
|
|
567
571
|
---
|
|
572
|
+
### Phase 10: User Stories Generation (Optional)
|
|
573
|
+
|
|
574
|
+
**File:** `backend/flow-build-phase-10.md`
|
|
575
|
+
**Duration:** 30-60 minutes
|
|
576
|
+
**Key Steps:**
|
|
577
|
+
|
|
578
|
+
- Load context from Phase 9 roadmap
|
|
579
|
+
- Generate detailed User Stories for selected Epics/Features
|
|
580
|
+
- Create Gherkin-style Acceptance Criteria (Given/When/Then)
|
|
581
|
+
- Inherit technical tasks from roadmap
|
|
582
|
+
- Generate QA Test Cases with specific data
|
|
583
|
+
- Update roadmap with links to User Stories
|
|
584
|
+
|
|
585
|
+
**Generates:**
|
|
586
|
+
|
|
587
|
+
- `docs/user-stories/EP-XXX/HU-XXX-YYY.md` (User Story)
|
|
588
|
+
- `docs/user-stories/EP-XXX/tests/TC-XXX-YYY.md` (Test Cases)
|
|
589
|
+
|
|
590
|
+
**Skip if:** You don't need detailed user stories or Gherkin AC for your workflow
|
|
591
|
+
---
|
|
568
592
|
## π Quick Start Guide
|
|
569
593
|
|
|
570
594
|
### For New Projects
|
|
@@ -842,7 +866,7 @@ Continue with Phase 8?
|
|
|
842
866
|
|
|
843
867
|
A) β
Yes, continue to Phase 8 (recommended) - 10-15 min
|
|
844
868
|
β Initialize project + Generate final docs
|
|
845
|
-
β Then option to continue to Phase 9 (roadmap)
|
|
869
|
+
β Then option to continue to Phase 9 (roadmap) and Phase 10 (user stories)
|
|
846
870
|
|
|
847
871
|
B) No, I'll review documentation first
|
|
848
872
|
|
|
@@ -868,15 +892,18 @@ Your choice (A): __
|
|
|
868
892
|
3. (Optional) Continue to Phase 9: Implementation Roadmap (15-30 min)
|
|
869
893
|
β Generates complete implementation plan with Story Points
|
|
870
894
|
β Includes Epics, Features, Tasks, and execution order
|
|
871
|
-
4.
|
|
895
|
+
4. (Optional) Continue to Phase 10: User Stories Generation (30-60 min)
|
|
896
|
+
β Generates Gherkin AC, technical details, and QA test cases
|
|
897
|
+
5. Start implementing: /feature <feature-name>
|
|
872
898
|
β Implements features following your architecture
|
|
873
899
|
|
|
874
900
|
π‘ Tip: All phases are independent and re-executable.
|
|
875
901
|
---
|
|
876
902
|
```
|
|
877
903
|
---
|
|
904
|
+
_Version: 4.1 (Phase 10 integrated - User Stories Generation with Gherkin AC)_
|
|
905
|
+
_Last Updated: 2025-12-20_
|
|
878
906
|
_Version: 4.0 (Phase 9 integrated - Implementation Roadmap with Story Points)_
|
|
879
|
-
_Last Updated: 2025-12-09_
|
|
880
907
|
_Version: 3.0 (Unified workflow: Phase 8 integrates project setup + final docs generation)_
|
|
881
908
|
_AI Flow - Transform your idea into production-ready code in minutes_
|
|
882
909
|
|
|
@@ -1,22 +1,131 @@
|
|
|
1
1
|
# Phase 1: Discovery & UX Requirements
|
|
2
2
|
|
|
3
3
|
**Duration:** 15-20 minutes
|
|
4
|
-
**Questions:** ~
|
|
4
|
+
**Questions:** ~11 questions
|
|
5
5
|
**Output:** project-brief.md, parts of AGENT.md
|
|
6
|
-
---
|
|
6
|
+
---
|
|
7
7
|
## π― Objective
|
|
8
8
|
|
|
9
|
-
Understand the **user-facing aspects** of the application:
|
|
9
|
+
Understand the **user-facing aspects** and core goal of the application:
|
|
10
10
|
|
|
11
|
-
1. What
|
|
12
|
-
2.
|
|
13
|
-
3.
|
|
14
|
-
4. What
|
|
15
|
-
5. What
|
|
16
|
-
|
|
11
|
+
1. What is the core goal and purpose of the project?
|
|
12
|
+
2. What type of application is being built?
|
|
13
|
+
3. Who are the target users?
|
|
14
|
+
4. What are the key user journeys?
|
|
15
|
+
5. What devices and browsers must be supported?
|
|
16
|
+
6. What are the UX priorities?
|
|
17
|
+
---
|
|
17
18
|
## π Questions
|
|
18
19
|
|
|
19
|
-
### Question 1.1:
|
|
20
|
+
### Question 1.1: Project Name & Description (with Smart Refinement)
|
|
21
|
+
|
|
22
|
+
> **π§ 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.
|
|
23
|
+
|
|
24
|
+
```
|
|
25
|
+
What is the project name?
|
|
26
|
+
|
|
27
|
+
Provide an initial description of your project.
|
|
28
|
+
(Don't worry about perfection - we'll refine it together if needed!)
|
|
29
|
+
|
|
30
|
+
Example: "A frontend dashboard for managing inventory in real-time"
|
|
31
|
+
```
|
|
32
|
+
|
|
33
|
+
**π AI Internal: Ambiguity Analysis**
|
|
34
|
+
|
|
35
|
+
After receiving the description, silently analyze for these criteria:
|
|
36
|
+
|
|
37
|
+
| Criterion | Check For | Score +1 if present |
|
|
38
|
+
|-----------|-----------|---------------------|
|
|
39
|
+
| **WHO** | Specific user type mentioned (not just "users") | "store managers", "traders", "students" |
|
|
40
|
+
| **WHAT** | Specific action/function (not just "view", "show") | "compare prices", "edit profiles", "visualize data" |
|
|
41
|
+
| **WHY** | Purpose or value mentioned | "to increase conversion", "to save time", "to improve UX" |
|
|
42
|
+
| **DOMAIN** | Industry/vertical indicated | "fintech", "e-commerce", "social media" |
|
|
43
|
+
| **DETAIL** | Description has 10+ meaningful words | Not counting articles |
|
|
44
|
+
|
|
45
|
+
**Scoring Rules:**
|
|
46
|
+
- Score 4-5: β
Accept immediately β Proceed to 1.2
|
|
47
|
+
- Score 0-3: β οΈ Enter refinement loop β Ask ONLY missing criteria
|
|
48
|
+
|
|
49
|
+
---
|
|
50
|
+
|
|
51
|
+
**π Conditional Refinement Loop (only if score < 4)**
|
|
52
|
+
|
|
53
|
+
> **CRITICAL**: Only ask about criteria that are MISSING. Do NOT repeat questions already answered. Respond in the SAME LANGUAGE the developer used.
|
|
54
|
+
|
|
55
|
+
```
|
|
56
|
+
[LANGUAGE: Match the developer's language]
|
|
57
|
+
|
|
58
|
+
π I'd like to understand your project better.
|
|
59
|
+
|
|
60
|
+
Your description: "[original description]"
|
|
61
|
+
|
|
62
|
+
[ONLY show questions for MISSING criteria:]
|
|
63
|
+
|
|
64
|
+
[If WHO is missing:]
|
|
65
|
+
1οΈβ£ WHO will use this application?
|
|
66
|
+
A) End consumers (B2C)
|
|
67
|
+
B) Business users (B2B)
|
|
68
|
+
C) Internal team / Admin
|
|
69
|
+
D) Other: __
|
|
70
|
+
|
|
71
|
+
[If WHAT is missing:]
|
|
72
|
+
2οΈβ£ WHAT is the core UX action users will perform?
|
|
73
|
+
A) Browse & Shop
|
|
74
|
+
B) Manage & Configure
|
|
75
|
+
C) Read & Consume
|
|
76
|
+
D) Create & Publish
|
|
77
|
+
E) Analyze & Visualize
|
|
78
|
+
F) Other: __
|
|
79
|
+
|
|
80
|
+
[If WHY is missing:]
|
|
81
|
+
3οΈβ£ WHY is this project needed?
|
|
82
|
+
A) Launch new product
|
|
83
|
+
B) Replace legacy UI
|
|
84
|
+
C) Better mobile experience
|
|
85
|
+
D) Specific new feature
|
|
86
|
+
E) Other: __
|
|
87
|
+
|
|
88
|
+
[If DOMAIN is missing:]
|
|
89
|
+
4οΈβ£ What INDUSTRY/DOMAIN is this for?
|
|
90
|
+
A) E-commerce/Retail
|
|
91
|
+
B) Fitness/Health
|
|
92
|
+
C) Finance/Payments
|
|
93
|
+
D) Education
|
|
94
|
+
E) Social/Community
|
|
95
|
+
F) Business tools (CRM, ERP)
|
|
96
|
+
G) Other: __
|
|
97
|
+
|
|
98
|
+
Your answers: __
|
|
99
|
+
```
|
|
100
|
+
|
|
101
|
+
---
|
|
102
|
+
|
|
103
|
+
**β¨ Generate Professional Description Options**
|
|
104
|
+
|
|
105
|
+
After gathering missing info, generate 3 polished versions:
|
|
106
|
+
|
|
107
|
+
```
|
|
108
|
+
[LANGUAGE: Match the developer's language]
|
|
109
|
+
|
|
110
|
+
β¨ Based on your input, here are 3 professional descriptions:
|
|
111
|
+
|
|
112
|
+
A) Concise (for package.json):
|
|
113
|
+
"[Generated 1-line description]"
|
|
114
|
+
|
|
115
|
+
B) Descriptive (for README.md):
|
|
116
|
+
"[Generated 2-3 line description with UX focus]"
|
|
117
|
+
|
|
118
|
+
C) Creative (for Marketing/Landing):
|
|
119
|
+
"[Generated catchy description]"
|
|
120
|
+
|
|
121
|
+
Which do you prefer? (1-3, or 4 to edit, 5 to start over)
|
|
122
|
+
```
|
|
123
|
+
|
|
124
|
+
**Your choice:**
|
|
125
|
+
|
|
126
|
+
---
|
|
127
|
+
|
|
128
|
+
### Question 1.2: Application Type
|
|
20
129
|
|
|
21
130
|
**What type of frontend application are you building?**
|
|
22
131
|
|
|
@@ -51,10 +160,26 @@ E) **Static Site (SSG)**
|
|
|
51
160
|
- Best for: Blogs, documentation, landing pages
|
|
52
161
|
|
|
53
162
|
**Your answer:**
|
|
54
|
-
---
|
|
55
|
-
### Question 1.
|
|
163
|
+
---
|
|
164
|
+
### Question 1.3: Target Users (Confirmation + Expansion)
|
|
165
|
+
|
|
166
|
+
```
|
|
167
|
+
[If WHO was captured in 1.1, show:]
|
|
168
|
+
|
|
169
|
+
β
Based on your description, your target users are: [WHO from 1.1]
|
|
170
|
+
|
|
171
|
+
Describe your user personas more deeply (3-5 bullet points):
|
|
172
|
+
|
|
173
|
+
- Demographics (age, tech-savviness, etc.)
|
|
174
|
+
- Use cases / goals
|
|
175
|
+
- Device preferences
|
|
176
|
+
- Accessibility needs
|
|
56
177
|
|
|
57
|
-
|
|
178
|
+
---
|
|
179
|
+
|
|
180
|
+
[If WHO was NOT captured in 1.1, ask normally:]
|
|
181
|
+
|
|
182
|
+
Who are your primary target users?
|
|
58
183
|
|
|
59
184
|
Describe your user personas (3-5 bullet points):
|
|
60
185
|
|
|
@@ -62,6 +187,7 @@ Describe your user personas (3-5 bullet points):
|
|
|
62
187
|
- Use cases / goals
|
|
63
188
|
- Device preferences
|
|
64
189
|
- Accessibility needs
|
|
190
|
+
```
|
|
65
191
|
|
|
66
192
|
**Example:**
|
|
67
193
|
|
|
@@ -73,12 +199,22 @@ Describe your user personas (3-5 bullet points):
|
|
|
73
199
|
```
|
|
74
200
|
|
|
75
201
|
**Your answer:**
|
|
76
|
-
---
|
|
77
|
-
### Question 1.
|
|
202
|
+
---
|
|
203
|
+
### Question 1.4: Key User Journeys (Confirmation + Expansion)
|
|
204
|
+
|
|
205
|
+
```
|
|
206
|
+
[If WHAT was captured in 1.1, show:]
|
|
207
|
+
|
|
208
|
+
β
Based on your description, a core journey is: [WHAT from 1.1]
|
|
209
|
+
|
|
210
|
+
What are the 3-5 most critical user flows?
|
|
78
211
|
|
|
79
|
-
|
|
212
|
+
---
|
|
80
213
|
|
|
81
|
-
|
|
214
|
+
[If WHAT was NOT captured in 1.1, ask normally:]
|
|
215
|
+
|
|
216
|
+
What are the 3-5 most critical user flows?
|
|
217
|
+
```
|
|
82
218
|
|
|
83
219
|
**Example:**
|
|
84
220
|
|
|
@@ -90,8 +226,8 @@ List the core journeys users will take through your app.
|
|
|
90
226
|
```
|
|
91
227
|
|
|
92
228
|
**Your answer:**
|
|
93
|
-
---
|
|
94
|
-
### Question 1.
|
|
229
|
+
---
|
|
230
|
+
### Question 1.5: Device & Browser Support
|
|
95
231
|
|
|
96
232
|
**What devices and browsers must you support?**
|
|
97
233
|
|
|
@@ -122,8 +258,8 @@ D) **Desktop-First**
|
|
|
122
258
|
- Best for: Admin panels, dashboards, B2B tools
|
|
123
259
|
|
|
124
260
|
**Your answer:**
|
|
125
|
-
---
|
|
126
|
-
### Question 1.
|
|
261
|
+
---
|
|
262
|
+
### Question 1.6: Responsive Strategy
|
|
127
263
|
|
|
128
264
|
**How will you handle different screen sizes?**
|
|
129
265
|
|
|
@@ -150,8 +286,8 @@ D) **Fixed Width (Desktop Only)**
|
|
|
150
286
|
- Best for: Internal tools, admin panels (desktop-only users)
|
|
151
287
|
|
|
152
288
|
**Your answer:**
|
|
153
|
-
---
|
|
154
|
-
### Question 1.
|
|
289
|
+
---
|
|
290
|
+
### Question 1.7: Internationalization (i18n)
|
|
155
291
|
|
|
156
292
|
**Do you need multi-language support?**
|
|
157
293
|
|
|
@@ -180,8 +316,8 @@ D) **Right-to-Left (RTL) Support**
|
|
|
180
316
|
**Your answer:**
|
|
181
317
|
|
|
182
318
|
**If multi-language selected, list target languages:**
|
|
183
|
-
---
|
|
184
|
-
### Question 1.
|
|
319
|
+
---
|
|
320
|
+
### Question 1.8: Authentication Requirements
|
|
185
321
|
|
|
186
322
|
**What authentication method will you use?**
|
|
187
323
|
|
|
@@ -219,8 +355,8 @@ F) **No Authentication**
|
|
|
219
355
|
- Best for: Marketing sites, public tools
|
|
220
356
|
|
|
221
357
|
**Your answer:**
|
|
222
|
-
---
|
|
223
|
-
### Question 1.
|
|
358
|
+
---
|
|
359
|
+
### Question 1.9: Data Privacy & Compliance
|
|
224
360
|
|
|
225
361
|
**What data privacy requirements do you have?**
|
|
226
362
|
|
|
@@ -257,8 +393,8 @@ F) **Multiple Regulations**
|
|
|
257
393
|
- Most restrictive controls apply
|
|
258
394
|
|
|
259
395
|
**Your answer:**
|
|
260
|
-
---
|
|
261
|
-
### Question 1.
|
|
396
|
+
---
|
|
397
|
+
### Question 1.10: Offline Support
|
|
262
398
|
|
|
263
399
|
**Do users need offline access?**
|
|
264
400
|
|
|
@@ -287,8 +423,8 @@ D) **Offline-First**
|
|
|
287
423
|
- Best for: Mobile apps, unreliable networks
|
|
288
424
|
|
|
289
425
|
**Your answer:**
|
|
290
|
-
---
|
|
291
|
-
### Question 1.
|
|
426
|
+
---
|
|
427
|
+
### Question 1.11: Performance Priorities
|
|
292
428
|
|
|
293
429
|
**What are your performance priorities?** (Select top 3)
|
|
294
430
|
|
|
@@ -327,25 +463,27 @@ F) **Perceived Performance**
|
|
|
327
463
|
- Best for: User experience
|
|
328
464
|
|
|
329
465
|
**Your answer (top 3):**
|
|
330
|
-
---
|
|
466
|
+
---
|
|
331
467
|
## π Phase 1 Summary
|
|
332
468
|
|
|
333
469
|
Before proceeding to Phase 2, confirm the following:
|
|
334
470
|
|
|
335
471
|
```
|
|
336
|
-
---
|
|
472
|
+
---
|
|
337
473
|
π PHASE 1 SUMMARY: DISCOVERY & UX
|
|
338
|
-
---
|
|
339
|
-
|
|
340
|
-
|
|
341
|
-
|
|
342
|
-
|
|
343
|
-
|
|
344
|
-
|
|
345
|
-
|
|
346
|
-
|
|
347
|
-
|
|
348
|
-
|
|
474
|
+
---
|
|
475
|
+
Project Name: [Answer from 1.1]
|
|
476
|
+
Project Description: [Answer from 1.1]
|
|
477
|
+
Application Type: [Answer from 1.2]
|
|
478
|
+
Target Users: [Answer from 1.3]
|
|
479
|
+
Key User Journeys: [Answer from 1.4]
|
|
480
|
+
Device/Browser Support: [Answer from 1.5]
|
|
481
|
+
Responsive Strategy: [Answer from 1.6]
|
|
482
|
+
Internationalization: [Answer from 1.7]
|
|
483
|
+
Authentication: [Answer from 1.8]
|
|
484
|
+
Data Privacy: [Answer from 1.9]
|
|
485
|
+
Offline Support: [Answer from 1.10]
|
|
486
|
+
Performance Priorities: [Answer from 1.11]
|
|
349
487
|
|
|
350
488
|
Is this correct? (Y/n)
|
|
351
489
|
```
|
|
@@ -353,7 +491,7 @@ Is this correct? (Y/n)
|
|
|
353
491
|
If **Yes:** Proceed to Phase 2
|
|
354
492
|
|
|
355
493
|
If **No:** Allow user to correct specific answers
|
|
356
|
-
---
|
|
494
|
+
---
|
|
357
495
|
## π Document Generation (Partial)
|
|
358
496
|
|
|
359
497
|
At the end of Phase 1, generate or update:
|
|
@@ -439,7 +577,7 @@ At the end of Phase 1, generate or update:
|
|
|
439
577
|
- Authentication: {{AUTH_METHOD}}
|
|
440
578
|
- Compliance: {{DATA_PRIVACY_COMPLIANCE}}
|
|
441
579
|
```
|
|
442
|
-
---
|
|
580
|
+
---
|
|
443
581
|
## π Next Steps
|
|
444
582
|
|
|
445
583
|
```
|
|
@@ -453,11 +591,7 @@ Next: Phase 2 - Components & Framework
|
|
|
453
591
|
|
|
454
592
|
Read: .ai-flow/prompts/frontend/flow-build-phase-2-components.md
|
|
455
593
|
```
|
|
456
|
-
---
|
|
457
|
-
**Last Updated:** 2025-
|
|
458
|
-
|
|
459
|
-
**Version:** 1.2.0
|
|
460
|
-
|
|
461
|
-
|
|
462
|
-
|
|
594
|
+
---
|
|
595
|
+
**Last Updated:** 2025-12-XX
|
|
463
596
|
|
|
597
|
+
**Version:** 1.3.0
|