geminize 1.0.0 → 1.2.0
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.
- checksums.yaml +4 -4
- data/.cursor/mcp.json +3 -0
- data/.cursor/rules/isolation_rules/Core/command-execution.mdc +235 -0
- data/.cursor/rules/isolation_rules/Core/complexity-decision-tree.mdc +187 -0
- data/.cursor/rules/isolation_rules/Core/creative-phase-enforcement.mdc +145 -0
- data/.cursor/rules/isolation_rules/Core/creative-phase-metrics.mdc +195 -0
- data/.cursor/rules/isolation_rules/Core/file-verification.mdc +198 -0
- data/.cursor/rules/isolation_rules/Core/platform-awareness.mdc +71 -0
- data/.cursor/rules/isolation_rules/Level3/planning-comprehensive.mdc +159 -0
- data/.cursor/rules/isolation_rules/Level3/task-tracking-intermediate.mdc +135 -0
- data/.cursor/rules/isolation_rules/Phases/CreativePhase/creative-phase-architecture.mdc +187 -0
- data/.cursor/rules/isolation_rules/main.mdc +123 -0
- data/.cursor/rules/isolation_rules/visual-maps/archive-mode-map.mdc +277 -0
- data/.cursor/rules/isolation_rules/visual-maps/creative-mode-map.mdc +224 -0
- data/.cursor/rules/isolation_rules/visual-maps/implement-mode-map.mdc +321 -0
- data/.cursor/rules/isolation_rules/visual-maps/plan-mode-map.mdc +269 -0
- data/.cursor/rules/isolation_rules/visual-maps/qa-mode-map.mdc +495 -0
- data/.cursor/rules/isolation_rules/visual-maps/reflect-mode-map.mdc +234 -0
- data/.cursor/rules/isolation_rules/visual-maps/van-mode-map.mdc +902 -0
- data/.cursor/rules/isolation_rules/visual-maps/van_mode_split/van-complexity-determination.mdc +60 -0
- data/.cursor/rules/isolation_rules/visual-maps/van_mode_split/van-file-verification.mdc +49 -0
- data/.cursor/rules/isolation_rules/visual-maps/van_mode_split/van-mode-map.mdc +49 -0
- data/.cursor/rules/isolation_rules/visual-maps/van_mode_split/van-platform-detection.mdc +50 -0
- data/.cursor/rules/isolation_rules/visual-maps/van_mode_split/van-qa-checks/build-test.mdc +117 -0
- data/.cursor/rules/isolation_rules/visual-maps/van_mode_split/van-qa-checks/config-check.mdc +103 -0
- data/.cursor/rules/isolation_rules/visual-maps/van_mode_split/van-qa-checks/dependency-check.mdc +147 -0
- data/.cursor/rules/isolation_rules/visual-maps/van_mode_split/van-qa-checks/environment-check.mdc +104 -0
- data/.cursor/rules/isolation_rules/visual-maps/van_mode_split/van-qa-checks/file-verification.mdc +1 -0
- data/.cursor/rules/isolation_rules/visual-maps/van_mode_split/van-qa-main.mdc +142 -0
- data/.cursor/rules/isolation_rules/visual-maps/van_mode_split/van-qa-utils/common-fixes.mdc +92 -0
- data/.cursor/rules/isolation_rules/visual-maps/van_mode_split/van-qa-utils/mode-transitions.mdc +101 -0
- data/.cursor/rules/isolation_rules/visual-maps/van_mode_split/van-qa-utils/reports.mdc +149 -0
- data/.cursor/rules/isolation_rules/visual-maps/van_mode_split/van-qa-utils/rule-calling-guide.mdc +66 -0
- data/.cursor/rules/isolation_rules/visual-maps/van_mode_split/van-qa-utils/rule-calling-help.mdc +19 -0
- data/.cursor/rules/isolation_rules/visual-maps/van_mode_split/van-qa-validation.md.old +363 -0
- data/.env.example +7 -0
- data/.memory_bank/activeContext.md +102 -0
- data/.memory_bank/progress.md +93 -0
- data/.memory_bank/projectbrief.md +45 -0
- data/.memory_bank/systemPatterns.md +90 -0
- data/.memory_bank/tasks.md +142 -0
- data/.memory_bank/techContext.md +73 -0
- data/.tool-versions +1 -0
- data/CHANGELOG.md +42 -0
- data/README.md +223 -5
- data/examples/function_calling.rb +218 -0
- data/examples/models_api.rb +125 -0
- data/examples/safety_settings.rb +82 -0
- data/lib/geminize/configuration.rb +4 -4
- data/lib/geminize/model_info.rb +87 -8
- data/lib/geminize/models/content_request_extensions.rb +219 -0
- data/lib/geminize/models/content_request_safety.rb +123 -0
- data/lib/geminize/models/content_response_extensions.rb +120 -0
- data/lib/geminize/models/function_declaration.rb +112 -0
- data/lib/geminize/models/function_response.rb +70 -0
- data/lib/geminize/models/model.rb +101 -109
- data/lib/geminize/models/model_list.rb +70 -28
- data/lib/geminize/models/safety_setting.rb +102 -0
- data/lib/geminize/models/tool.rb +47 -0
- data/lib/geminize/models/tool_config.rb +52 -0
- data/lib/geminize/module_extensions.rb +228 -0
- data/lib/geminize/module_safety.rb +135 -0
- data/lib/geminize/request_builder.rb +29 -0
- data/lib/geminize/version.rb +1 -1
- data/lib/geminize.rb +83 -14
- metadata +57 -2
@@ -0,0 +1,495 @@
|
|
1
|
+
---
|
2
|
+
description: QA Mode
|
3
|
+
globs: qa-mode-map.mdc
|
4
|
+
alwaysApply: false
|
5
|
+
---
|
6
|
+
|
7
|
+
|
8
|
+
> **TL;DR:** This enhanced QA mode provides comprehensive validation at any stage of development. It automatically detects the current phase, validates Memory Bank consistency, verifies task tracking, and performs phase-specific technical validation to ensure project quality throughout the development lifecycle.
|
9
|
+
|
10
|
+
## 🔍 ENHANCED QA MODE PROCESS FLOW
|
11
|
+
|
12
|
+
```mermaid
|
13
|
+
graph TD
|
14
|
+
Start["🚀 START QA MODE"] --> DetectPhase["🧭 PHASE DETECTION<br>Determine current project phase"]
|
15
|
+
|
16
|
+
%% Phase detection decision path
|
17
|
+
DetectPhase --> PhaseDetermination{"Current Phase?"}
|
18
|
+
PhaseDetermination -->|"VAN"| VANChecks["VAN Phase Validation"]
|
19
|
+
PhaseDetermination -->|"PLAN"| PLANChecks["PLAN Phase Validation"]
|
20
|
+
PhaseDetermination -->|"CREATIVE"| CREATIVEChecks["CREATIVE Phase Validation"]
|
21
|
+
PhaseDetermination -->|"IMPLEMENT"| IMPLEMENTChecks["IMPLEMENT Phase Validation"]
|
22
|
+
|
23
|
+
%% Universal checks that apply to all phases
|
24
|
+
DetectPhase --> UniversalChecks["🔍 UNIVERSAL VALIDATION"]
|
25
|
+
UniversalChecks --> MemoryBankCheck["1️⃣ MEMORY BANK VERIFICATION<br>Check consistency & updates"]
|
26
|
+
MemoryBankCheck --> TaskTrackingCheck["2️⃣ TASK TRACKING VERIFICATION<br>Validate tasks.md as source of truth"]
|
27
|
+
TaskTrackingCheck --> ReferenceCheck["3️⃣ REFERENCE VALIDATION<br>Verify cross-references between docs"]
|
28
|
+
|
29
|
+
%% Phase-specific validations feed into comprehensive report
|
30
|
+
VANChecks & PLANChecks & CREATIVEChecks & IMPLEMENTChecks --> PhaseSpecificResults["Phase-Specific Results"]
|
31
|
+
ReferenceCheck & PhaseSpecificResults --> ValidationResults{"✅ All Checks<br>Passed?"}
|
32
|
+
|
33
|
+
%% Results Processing
|
34
|
+
ValidationResults -->|"Yes"| SuccessReport["📝 GENERATE SUCCESS REPORT<br>All validations passed"]
|
35
|
+
ValidationResults -->|"No"| FailureReport["⚠️ GENERATE FAILURE REPORT<br>With specific fix instructions"]
|
36
|
+
|
37
|
+
%% Success Path
|
38
|
+
SuccessReport --> UpdateMB["📚 Update Memory Bank<br>Record successful validation"]
|
39
|
+
UpdateMB --> ContinueProcess["🚦 CONTINUE: Phase processes<br>can proceed"]
|
40
|
+
|
41
|
+
%% Failure Path
|
42
|
+
FailureReport --> IdentifyFixes["🔧 IDENTIFY REQUIRED FIXES"]
|
43
|
+
IdentifyFixes --> ApplyFixes["🛠️ APPLY FIXES"]
|
44
|
+
ApplyFixes --> Revalidate["🔄 Re-run validation"]
|
45
|
+
Revalidate --> ValidationResults
|
46
|
+
|
47
|
+
%% Style nodes for clarity
|
48
|
+
style Start fill:#4da6ff,stroke:#0066cc,color:white
|
49
|
+
style DetectPhase fill:#f6ad55,stroke:#c27022,color:white
|
50
|
+
style UniversalChecks fill:#f6546a,stroke:#c30052,color:white
|
51
|
+
style MemoryBankCheck fill:#10b981,stroke:#059669,color:white
|
52
|
+
style TaskTrackingCheck fill:#10b981,stroke:#059669,color:white
|
53
|
+
style ReferenceCheck fill:#10b981,stroke:#059669,color:white
|
54
|
+
style ValidationResults fill:#f6546a,stroke:#c30052,color:white
|
55
|
+
style SuccessReport fill:#10b981,stroke:#059669,color:white
|
56
|
+
style FailureReport fill:#f6ad55,stroke:#c27022,color:white
|
57
|
+
style ContinueProcess fill:#10b981,stroke:#059669,color:white,stroke-width:2px
|
58
|
+
style IdentifyFixes fill:#f6ad55,stroke:#c27022,color:white
|
59
|
+
```
|
60
|
+
|
61
|
+
## 🧭 PHASE DETECTION PROCESS
|
62
|
+
|
63
|
+
The enhanced QA mode first determines which phase the project is currently in:
|
64
|
+
|
65
|
+
```mermaid
|
66
|
+
graph TD
|
67
|
+
PD["Phase Detection"] --> CheckMB["Analyze Memory Bank Files"]
|
68
|
+
CheckMB --> CheckActive["Check activeContext.md<br>for current phase"]
|
69
|
+
CheckActive --> CheckProgress["Check progress.md<br>for recent activities"]
|
70
|
+
CheckProgress --> CheckTasks["Check tasks.md<br>for task status"]
|
71
|
+
|
72
|
+
CheckTasks --> PhaseResult{"Determine<br>Current Phase"}
|
73
|
+
PhaseResult -->|"VAN"| VAN["VAN Phase<br>Initialization"]
|
74
|
+
PhaseResult -->|"PLAN"| PLAN["PLAN Phase<br>Task Planning"]
|
75
|
+
PhaseResult -->|"CREATIVE"| CREATIVE["CREATIVE Phase<br>Design Decisions"]
|
76
|
+
PhaseResult -->|"IMPLEMENT"| IMPLEMENT["IMPLEMENT Phase<br>Implementation"]
|
77
|
+
|
78
|
+
VAN & PLAN & CREATIVE & IMPLEMENT --> LoadChecks["Load Phase-Specific<br>Validation Checks"]
|
79
|
+
|
80
|
+
style PD fill:#4da6ff,stroke:#0066cc,color:white
|
81
|
+
style PhaseResult fill:#f6546a,stroke:#c30052,color:white
|
82
|
+
style LoadChecks fill:#10b981,stroke:#059669,color:white
|
83
|
+
```
|
84
|
+
|
85
|
+
## 📝 UNIVERSAL MEMORY BANK VERIFICATION
|
86
|
+
|
87
|
+
This process ensures Memory Bank files are consistent and up-to-date regardless of phase:
|
88
|
+
|
89
|
+
```mermaid
|
90
|
+
graph TD
|
91
|
+
MBVS["Memory Bank<br>Verification"] --> CoreCheck["Check Core Files Exist"]
|
92
|
+
CoreCheck --> CoreFiles["Verify Required Files:<br>projectbrief.md<br>activeContext.md<br>tasks.md<br>progress.md"]
|
93
|
+
|
94
|
+
CoreFiles --> ContentCheck["Verify Content<br>Consistency"]
|
95
|
+
ContentCheck --> LastModified["Check Last Modified<br>Timestamps"]
|
96
|
+
LastModified --> CrossRef["Validate Cross-<br>References"]
|
97
|
+
|
98
|
+
CrossRef --> ConsistencyCheck{"All Files<br>Consistent?"}
|
99
|
+
ConsistencyCheck -->|"Yes"| PassMB["✅ Memory Bank<br>Verification Passed"]
|
100
|
+
ConsistencyCheck -->|"No"| FailMB["❌ Memory Bank<br>Inconsistencies Found"]
|
101
|
+
|
102
|
+
FailMB --> FixSuggestions["Generate Fix<br>Suggestions"]
|
103
|
+
|
104
|
+
style MBVS fill:#4da6ff,stroke:#0066cc,color:white
|
105
|
+
style ConsistencyCheck fill:#f6546a,stroke:#c30052,color:white
|
106
|
+
style PassMB fill:#10b981,stroke:#059669,color:white
|
107
|
+
style FailMB fill:#ff5555,stroke:#dd3333,color:white
|
108
|
+
```
|
109
|
+
|
110
|
+
## 📋 TASK TRACKING VERIFICATION
|
111
|
+
|
112
|
+
This process validates tasks.md as the single source of truth:
|
113
|
+
|
114
|
+
```mermaid
|
115
|
+
graph TD
|
116
|
+
TTV["Task Tracking<br>Verification"] --> CheckTasksFile["Check tasks.md<br>Existence & Format"]
|
117
|
+
CheckTasksFile --> VerifyReferences["Verify Task References<br>in Other Documents"]
|
118
|
+
VerifyReferences --> ProgressCheck["Check Consistency with<br>progress.md"]
|
119
|
+
ProgressCheck --> StatusCheck["Verify Task Status<br>Accuracy"]
|
120
|
+
|
121
|
+
StatusCheck --> TaskConsistency{"Tasks Properly<br>Tracked?"}
|
122
|
+
TaskConsistency -->|"Yes"| PassTasks["✅ Task Tracking<br>Verification Passed"]
|
123
|
+
TaskConsistency -->|"No"| FailTasks["❌ Task Tracking<br>Issues Found"]
|
124
|
+
|
125
|
+
FailTasks --> TaskFixSuggestions["Generate Task Tracking<br>Fix Suggestions"]
|
126
|
+
|
127
|
+
style TTV fill:#4da6ff,stroke:#0066cc,color:white
|
128
|
+
style TaskConsistency fill:#f6546a,stroke:#c30052,color:white
|
129
|
+
style PassTasks fill:#10b981,stroke:#059669,color:white
|
130
|
+
style FailTasks fill:#ff5555,stroke:#dd3333,color:white
|
131
|
+
```
|
132
|
+
|
133
|
+
## 🔄 REFERENCE VALIDATION PROCESS
|
134
|
+
|
135
|
+
This process ensures proper cross-referencing between documents:
|
136
|
+
|
137
|
+
```mermaid
|
138
|
+
graph TD
|
139
|
+
RV["Reference<br>Validation"] --> FindRefs["Find Cross-References<br>in Documents"]
|
140
|
+
FindRefs --> VerifyRefs["Verify Reference<br>Accuracy"]
|
141
|
+
VerifyRefs --> CheckBackRefs["Check Bidirectional<br>References"]
|
142
|
+
|
143
|
+
CheckBackRefs --> RefConsistency{"References<br>Consistent?"}
|
144
|
+
RefConsistency -->|"Yes"| PassRefs["✅ Reference Validation<br>Passed"]
|
145
|
+
RefConsistency -->|"No"| FailRefs["❌ Reference<br>Issues Found"]
|
146
|
+
|
147
|
+
FailRefs --> RefFixSuggestions["Generate Reference<br>Fix Suggestions"]
|
148
|
+
|
149
|
+
style RV fill:#4da6ff,stroke:#0066cc,color:white
|
150
|
+
style RefConsistency fill:#f6546a,stroke:#c30052,color:white
|
151
|
+
style PassRefs fill:#10b981,stroke:#059669,color:white
|
152
|
+
style FailRefs fill:#ff5555,stroke:#dd3333,color:white
|
153
|
+
```
|
154
|
+
|
155
|
+
## 🚨 PHASE-SPECIFIC VALIDATION PROCESSES
|
156
|
+
|
157
|
+
### VAN Phase Validation
|
158
|
+
|
159
|
+
```mermaid
|
160
|
+
graph TD
|
161
|
+
VAN["VAN Phase<br>Validation"] --> InitCheck["Check Initialization<br>Completeness"]
|
162
|
+
InitCheck --> PlatformCheck["Verify Platform<br>Detection"]
|
163
|
+
PlatformCheck --> ComplexityCheck["Validate Complexity<br>Determination"]
|
164
|
+
|
165
|
+
ComplexityCheck --> VANConsistency{"VAN Phase<br>Complete?"}
|
166
|
+
VANConsistency -->|"Yes"| PassVAN["✅ VAN Phase<br>Validation Passed"]
|
167
|
+
VANConsistency -->|"No"| FailVAN["❌ VAN Phase<br>Issues Found"]
|
168
|
+
|
169
|
+
style VAN fill:#4da6ff,stroke:#0066cc,color:white
|
170
|
+
style VANConsistency fill:#f6546a,stroke:#c30052,color:white
|
171
|
+
style PassVAN fill:#10b981,stroke:#059669,color:white
|
172
|
+
style FailVAN fill:#ff5555,stroke:#dd3333,color:white
|
173
|
+
```
|
174
|
+
|
175
|
+
### PLAN Phase Validation
|
176
|
+
|
177
|
+
```mermaid
|
178
|
+
graph TD
|
179
|
+
PLAN["PLAN Phase<br>Validation"] --> PlanCheck["Check Planning<br>Documentation"]
|
180
|
+
PlanCheck --> TaskBreakdown["Verify Task<br>Breakdown"]
|
181
|
+
TaskBreakdown --> ScopeCheck["Validate Scope<br>Definition"]
|
182
|
+
|
183
|
+
ScopeCheck --> PLANConsistency{"PLAN Phase<br>Complete?"}
|
184
|
+
PLANConsistency -->|"Yes"| PassPLAN["✅ PLAN Phase<br>Validation Passed"]
|
185
|
+
PLANConsistency -->|"No"| FailPLAN["❌ PLAN Phase<br>Issues Found"]
|
186
|
+
|
187
|
+
style PLAN fill:#4da6ff,stroke:#0066cc,color:white
|
188
|
+
style PLANConsistency fill:#f6546a,stroke:#c30052,color:white
|
189
|
+
style PassPLAN fill:#10b981,stroke:#059669,color:white
|
190
|
+
style FailPLAN fill:#ff5555,stroke:#dd3333,color:white
|
191
|
+
```
|
192
|
+
|
193
|
+
### CREATIVE Phase Validation
|
194
|
+
|
195
|
+
```mermaid
|
196
|
+
graph TD
|
197
|
+
CREATIVE["CREATIVE Phase<br>Validation"] --> DesignCheck["Check Design<br>Documents"]
|
198
|
+
DesignCheck --> ArchCheck["Verify Architectural<br>Decisions"]
|
199
|
+
ArchCheck --> PatternCheck["Validate Design<br>Patterns"]
|
200
|
+
|
201
|
+
PatternCheck --> CREATIVEConsistency{"CREATIVE Phase<br>Complete?"}
|
202
|
+
CREATIVEConsistency -->|"Yes"| PassCREATIVE["✅ CREATIVE Phase<br>Validation Passed"]
|
203
|
+
CREATIVEConsistency -->|"No"| FailCREATIVE["❌ CREATIVE Phase<br>Issues Found"]
|
204
|
+
|
205
|
+
style CREATIVE fill:#4da6ff,stroke:#0066cc,color:white
|
206
|
+
style CREATIVEConsistency fill:#f6546a,stroke:#c30052,color:white
|
207
|
+
style PassCREATIVE fill:#10b981,stroke:#059669,color:white
|
208
|
+
style FailCREATIVE fill:#ff5555,stroke:#dd3333,color:white
|
209
|
+
```
|
210
|
+
|
211
|
+
### IMPLEMENT Phase Technical Validation
|
212
|
+
|
213
|
+
This retains the original QA validation from the previous version:
|
214
|
+
|
215
|
+
```mermaid
|
216
|
+
graph TD
|
217
|
+
IMPLEMENT["IMPLEMENT Phase<br>Validation"] --> ReadDesign["Read Design Decisions"]
|
218
|
+
ReadDesign --> FourChecks["Four-Point Technical<br>Validation"]
|
219
|
+
|
220
|
+
FourChecks --> DepCheck["1️⃣ Dependency<br>Verification"]
|
221
|
+
DepCheck --> ConfigCheck["2️⃣ Configuration<br>Validation"]
|
222
|
+
ConfigCheck --> EnvCheck["3️⃣ Environment<br>Validation"]
|
223
|
+
EnvCheck --> MinBuildCheck["4️⃣ Minimal Build<br>Test"]
|
224
|
+
|
225
|
+
MinBuildCheck --> IMPLEMENTConsistency{"Technical<br>Prerequisites Met?"}
|
226
|
+
IMPLEMENTConsistency -->|"Yes"| PassIMPLEMENT["✅ IMPLEMENT Phase<br>Validation Passed"]
|
227
|
+
IMPLEMENTConsistency -->|"No"| FailIMPLEMENT["❌ IMPLEMENT Phase<br>Issues Found"]
|
228
|
+
|
229
|
+
style IMPLEMENT fill:#4da6ff,stroke:#0066cc,color:white
|
230
|
+
style FourChecks fill:#f6546a,stroke:#c30052,color:white
|
231
|
+
style IMPLEMENTConsistency fill:#f6546a,stroke:#c30052,color:white
|
232
|
+
style PassIMPLEMENT fill:#10b981,stroke:#059669,color:white
|
233
|
+
style FailIMPLEMENT fill:#ff5555,stroke:#dd3333,color:white
|
234
|
+
```
|
235
|
+
|
236
|
+
## 📋 UNIVERSAL VALIDATION COMMAND EXECUTION
|
237
|
+
|
238
|
+
### Memory Bank Verification Commands:
|
239
|
+
|
240
|
+
```bash
|
241
|
+
# Check Memory Bank file existence and recency
|
242
|
+
ls -la memory-bank/
|
243
|
+
find memory-bank/ -type f -mtime -7 | sort
|
244
|
+
|
245
|
+
# Check for consistency between files
|
246
|
+
grep -r "task" memory-bank/
|
247
|
+
grep -r "requirement" memory-bank/
|
248
|
+
```
|
249
|
+
|
250
|
+
### Task Tracking Verification Commands:
|
251
|
+
|
252
|
+
```bash
|
253
|
+
# Verify tasks.md as source of truth
|
254
|
+
test -f tasks.md && echo "✅ tasks.md exists" || echo "❌ tasks.md missing"
|
255
|
+
|
256
|
+
# Check references to tasks in other files
|
257
|
+
grep -r "Task" --include="*.md" .
|
258
|
+
grep -r "task" --include="*.md" . | grep -v "tasks.md" | wc -l
|
259
|
+
|
260
|
+
# Verify task status consistency
|
261
|
+
grep -i "completed\|done\|finished" tasks.md
|
262
|
+
grep -i "in progress\|started" tasks.md
|
263
|
+
```
|
264
|
+
|
265
|
+
### Reference Validation Commands:
|
266
|
+
|
267
|
+
```bash
|
268
|
+
# Find cross-references between files
|
269
|
+
grep -r "see\|refer\|reference" --include="*.md" .
|
270
|
+
|
271
|
+
# Check for broken references
|
272
|
+
for file in $(grep -l "see\|refer\|reference" --include="*.md" .); do
|
273
|
+
for ref in $(grep -o '[a-zA-Z0-9_-]*\.md' $file); do
|
274
|
+
test -f $ref || echo "❌ Broken reference: $ref in $file"
|
275
|
+
done
|
276
|
+
done
|
277
|
+
```
|
278
|
+
|
279
|
+
## 📋 1️⃣ DEPENDENCY VERIFICATION PROCESS (Original)
|
280
|
+
|
281
|
+
This validation point ensures all required packages are correctly installed.
|
282
|
+
|
283
|
+
### Command Execution:
|
284
|
+
|
285
|
+
```bash
|
286
|
+
# Check if packages are installed
|
287
|
+
npm list react react-dom tailwindcss postcss autoprefixer
|
288
|
+
|
289
|
+
# Verify package versions match requirements
|
290
|
+
npm list | grep -E "react|tailwind|postcss"
|
291
|
+
|
292
|
+
# Check for peer dependency warnings
|
293
|
+
npm ls --depth=0
|
294
|
+
```
|
295
|
+
|
296
|
+
### Validation Criteria:
|
297
|
+
- All required packages must be installed
|
298
|
+
- Versions must be compatible with requirements
|
299
|
+
- No critical peer dependency warnings
|
300
|
+
- Required dev dependencies must be present
|
301
|
+
|
302
|
+
### Common Fixes:
|
303
|
+
- `npm install [missing-package]` - Install missing packages
|
304
|
+
- `npm install [package]@[version]` - Fix version mismatches
|
305
|
+
- `npm install --save-dev [dev-dependency]` - Add development dependencies
|
306
|
+
|
307
|
+
## 📝 2️⃣ CONFIGURATION VALIDATION PROCESS (Original)
|
308
|
+
|
309
|
+
This validation point ensures configuration files are in the correct format for the project.
|
310
|
+
|
311
|
+
### Command Execution:
|
312
|
+
|
313
|
+
```bash
|
314
|
+
# Check package.json for module type
|
315
|
+
grep "\"type\":" package.json
|
316
|
+
|
317
|
+
# Verify configuration file extensions match module type
|
318
|
+
find . -name "*.config.*" | grep -E "\.(js|cjs|mjs)$"
|
319
|
+
|
320
|
+
# Test configuration syntax
|
321
|
+
node -c *.config.js || node -c *.config.cjs || node -c *.config.mjs
|
322
|
+
```
|
323
|
+
|
324
|
+
### Validation Criteria:
|
325
|
+
- Configuration file extensions must match module type in package.json
|
326
|
+
- File syntax must be valid
|
327
|
+
- Configuration must reference installed packages
|
328
|
+
|
329
|
+
### Common Fixes:
|
330
|
+
- Rename `.js` to `.cjs` for CommonJS in ES module projects
|
331
|
+
- Fix syntax errors in configuration files
|
332
|
+
- Adjust configuration to reference installed packages
|
333
|
+
|
334
|
+
## 🌐 3️⃣ ENVIRONMENT VALIDATION PROCESS (Original)
|
335
|
+
|
336
|
+
This validation point ensures the development environment is correctly set up.
|
337
|
+
|
338
|
+
### Command Execution:
|
339
|
+
|
340
|
+
```bash
|
341
|
+
# Check build tools
|
342
|
+
npm run --help
|
343
|
+
|
344
|
+
# Verify node version compatibility
|
345
|
+
node -v
|
346
|
+
|
347
|
+
# Check for environment variables
|
348
|
+
printenv | grep -E "NODE_|PATH|HOME"
|
349
|
+
|
350
|
+
# Verify access permissions
|
351
|
+
ls -la .
|
352
|
+
```
|
353
|
+
|
354
|
+
### Validation Criteria:
|
355
|
+
- Node.js version must be compatible with requirements
|
356
|
+
- Build commands must be defined in package.json
|
357
|
+
- Environment must have necessary access permissions
|
358
|
+
- Required environment variables must be set
|
359
|
+
|
360
|
+
### Common Fixes:
|
361
|
+
- Update Node.js version
|
362
|
+
- Add missing scripts to package.json
|
363
|
+
- Fix file permissions with chmod/icacls
|
364
|
+
- Set required environment variables
|
365
|
+
|
366
|
+
## 🔥 4️⃣ MINIMAL BUILD TEST PROCESS (Original)
|
367
|
+
|
368
|
+
This validation point tests a minimal build to ensure basic functionality works.
|
369
|
+
|
370
|
+
### Command Execution:
|
371
|
+
|
372
|
+
```bash
|
373
|
+
# Run a minimal build
|
374
|
+
npm run build -- --dry-run || npm run dev -- --dry-run
|
375
|
+
|
376
|
+
# Test entry point file existence
|
377
|
+
find src -name "main.*" -o -name "index.*"
|
378
|
+
|
379
|
+
# Validate HTML entry point
|
380
|
+
grep -i "script.*src=" index.html
|
381
|
+
```
|
382
|
+
|
383
|
+
### Validation Criteria:
|
384
|
+
- Build process must complete without errors
|
385
|
+
- Entry point files must exist and be correctly referenced
|
386
|
+
- HTML must reference the correct JavaScript entry point
|
387
|
+
- Basic rendering must work in a test environment
|
388
|
+
|
389
|
+
### Common Fixes:
|
390
|
+
- Fix entry point references in HTML
|
391
|
+
- Correct import paths in JavaScript
|
392
|
+
- Fix build configuration errors
|
393
|
+
- Update incorrect paths or references
|
394
|
+
|
395
|
+
## 📊 ENHANCED COMPREHENSIVE QA REPORT FORMAT
|
396
|
+
|
397
|
+
```
|
398
|
+
╔═════════════════════════ 🔍 ENHANCED QA VALIDATION REPORT ═════════════════════╗
|
399
|
+
│ │
|
400
|
+
│ Project: [Project Name] Date: [Current Date] │
|
401
|
+
│ Platform: [OS Platform] Detected Phase: [Current Phase] │
|
402
|
+
│ │
|
403
|
+
│ ━━━━━━━━━━━━━━━━━━━━━━━━ UNIVERSAL VALIDATION RESULTS ━━━━━━━━━━━━━━━━━━━━━━━ │
|
404
|
+
│ │
|
405
|
+
│ 1️⃣ MEMORY BANK VERIFICATION │
|
406
|
+
│ ✓ Core Files: [Status] │
|
407
|
+
│ ✓ Content Consistency: [Status] │
|
408
|
+
│ ✓ Last Modified: [Status] │
|
409
|
+
│ │
|
410
|
+
│ 2️⃣ TASK TRACKING VERIFICATION │
|
411
|
+
│ ✓ tasks.md Status: [Status] │
|
412
|
+
│ ✓ Task References: [Status] │
|
413
|
+
│ ✓ Status Consistency: [Status] │
|
414
|
+
│ │
|
415
|
+
│ 3️⃣ REFERENCE VALIDATION │
|
416
|
+
│ ✓ Cross-References: [Status] │
|
417
|
+
│ ✓ Reference Accuracy: [Status] │
|
418
|
+
│ │
|
419
|
+
│ ━━━━━━━━━━━━━━━━━━━━━━━ PHASE-SPECIFIC VALIDATION ━━━━━━━━━━━━━━━━━━━━━━━━━━━ │
|
420
|
+
│ │
|
421
|
+
│ [VAN/PLAN/CREATIVE/IMPLEMENT] PHASE VALIDATION │
|
422
|
+
│ ✓ [Phase-specific check 1]: [Status] │
|
423
|
+
│ ✓ [Phase-specific check 2]: [Status] │
|
424
|
+
│ ✓ [Phase-specific check 3]: [Status] │
|
425
|
+
│ │
|
426
|
+
│ [Technical validation section shown only for IMPLEMENT phase] │
|
427
|
+
│ │
|
428
|
+
│ ━━━━━━━━━━━━━━━━━━━━━━━━━━━ OVERALL STATUS ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ │
|
429
|
+
│ │
|
430
|
+
│ ✅ VALIDATION PASSED - Project quality verified for current phase │
|
431
|
+
│ │
|
432
|
+
╚═══════════════════════════════════════════════════════════════════════════════╝
|
433
|
+
```
|
434
|
+
|
435
|
+
## 🚫 ENHANCED FAILURE REPORT FORMAT
|
436
|
+
|
437
|
+
If validation fails, a detailed failure report is generated:
|
438
|
+
|
439
|
+
```
|
440
|
+
╔═════════════════════════ ⚠️ QA VALIDATION FAILURES ═════════════════════════════╗
|
441
|
+
│ │
|
442
|
+
│ Project: [Project Name] Date: [Current Date] │
|
443
|
+
│ Platform: [OS Platform] Detected Phase: [Current Phase] │
|
444
|
+
│ │
|
445
|
+
│ ━━━━━━━━━━━━━━━━━━━━━━━━━━ FAILED CHECKS ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ │
|
446
|
+
│ │
|
447
|
+
│ ❌ MEMORY BANK ISSUES │
|
448
|
+
│ • [Specific issue details] │
|
449
|
+
│ • [Specific issue details] │
|
450
|
+
│ │
|
451
|
+
│ ❌ TASK TRACKING ISSUES │
|
452
|
+
│ • [Specific issue details] │
|
453
|
+
│ • [Specific issue details] │
|
454
|
+
│ │
|
455
|
+
│ ❌ REFERENCE ISSUES │
|
456
|
+
│ • [Specific issue details] │
|
457
|
+
│ • [Specific issue details] │
|
458
|
+
│ │
|
459
|
+
│ ❌ [PHASE]-SPECIFIC ISSUES │
|
460
|
+
│ • [Specific issue details] │
|
461
|
+
│ • [Specific issue details] │
|
462
|
+
│ │
|
463
|
+
│ ━━━━━━━━━━━━━━━━━━━━━━━━━━━ REQUIRED FIXES ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ │
|
464
|
+
│ │
|
465
|
+
│ 1. [Specific fix instruction with command] │
|
466
|
+
│ 2. [Specific fix instruction with command] │
|
467
|
+
│ 3. [Specific fix instruction with command] │
|
468
|
+
│ │
|
469
|
+
│ ⚠️ VALIDATION FAILED - Please resolve issues before proceeding │
|
470
|
+
│ │
|
471
|
+
╚═════════════════════════════════════════════════════════════════════════════════╝
|
472
|
+
```
|
473
|
+
|
474
|
+
## 🔄 QA-ANYTIME ACTIVATION PROTOCOL
|
475
|
+
|
476
|
+
The enhanced QA mode can be activated at any time in the development process:
|
477
|
+
|
478
|
+
```mermaid
|
479
|
+
graph TD
|
480
|
+
Start["User Types: QA"] --> DetectContext["Detect Current Context"]
|
481
|
+
DetectContext --> RunQA["Run QA with Context-Aware Checks"]
|
482
|
+
RunQA --> GenerateReport["Generate Appropriate QA Report"]
|
483
|
+
GenerateReport --> UserResponse["Present Report to User"]
|
484
|
+
|
485
|
+
UserResponse --> FixNeeded{"Fixes<br>Needed?"}
|
486
|
+
FixNeeded -->|"Yes"| SuggestFixes["Display Fix Instructions"]
|
487
|
+
FixNeeded -->|"No"| ContinueWork["Continue Current Phase Work"]
|
488
|
+
|
489
|
+
style Start fill:#4da6ff,stroke:#0066cc,color:white
|
490
|
+
style FixNeeded fill:#f6546a,stroke:#c30052,color:white
|
491
|
+
style SuggestFixes fill:#ff5555,stroke:#dd3333,color:white
|
492
|
+
style ContinueWork fill:#10b981,stroke:#059669,color:white
|
493
|
+
```
|
494
|
+
|
495
|
+
This enhanced QA mode serves as a "quality guardian" throughout the development process, ensuring documentation is consistently maintained and all phase requirements are met before proceeding to the next phase.
|