Repository navigation
Expand file tree
/
Copy pathWorkFlow
More file actions
273 lines (169 loc) · 3.95 KB
/
Copy pathWorkFlow
File metadata and controls
273 lines (169 loc) · 3.95 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
# MarketLens – AI Development Workflow
## Objective
Build MarketLens with production-grade quality while minimizing unnecessary token consumption. Prioritize efficient communication without sacrificing architecture, maintainability, scalability, or code quality.
---
# Core Principles
## 1. Think Before Generating
- Analyze the entire task before writing code.
- Avoid unnecessary explanations.
- Output only what is required.
- Never regenerate files that do not need changes.
---
## 2. Preserve Code Quality
Token optimization must NEVER reduce code quality.
Maintain:
- Clean Architecture
- SOLID Principles
- DRY
- KISS
- Separation of Concerns
- Type Safety
- Proper Error Handling
- Reusable Components
- Scalable Folder Structure
- Security Best Practices
Always write production-ready code.
---
## 3. Incremental Development
Never generate the whole project again.
Instead:
- Modify only affected files.
- Mention unchanged files without rewriting them.
- Generate the smallest valid diff possible.
Example:
✅ Update:
- backend/api/predict.py
No changes:
- auth/
- models/
- database/
---
## 4. No Duplicate Code
Before creating:
- Components
- Hooks
- Services
- Utilities
- Types
- APIs
Check whether they already exist.
Reuse instead of recreating.
---
## 5. Keep Responses Compact
Avoid:
- Long introductions
- Repeating previous context
- Explaining obvious code
- Restating requirements
Only explain decisions when necessary.
---
## 6. Maintain Project Context
Assume previous files still exist.
Never rewrite:
- package.json
- tsconfig.json
- next.config
- requirements.txt
- Docker files
- Existing APIs
unless explicitly requested.
---
## 7. Follow Existing Architecture
Do not invent new structures.
Respect existing:
- naming conventions
- folder structure
- coding style
- design system
- theme
- APIs
---
## 8. Reuse Existing Dependencies
Before installing anything:
Check whether the project already contains an equivalent library.
Do not install duplicate packages.
---
## 9. Output Format
Always use:
### Files Changed
- file/path
### Reason
One short paragraph.
### Code
Only the modified code.
---
## 10. No Placeholder Code
Avoid:
TODO
Coming Soon
Dummy implementations
Pseudo code
Mock business logic
If a feature is implemented, implement it completely.
---
## 11. Ask Only When Necessary
Do not interrupt development for minor assumptions.
Ask questions only if the answer would significantly affect architecture or functionality.
---
## 12. Performance First
Optimize for:
- Fast rendering
- Small bundle size
- Lazy loading
- Code splitting
- Memoization where appropriate
- Efficient database queries
- API caching when useful
---
## 13. Production Standards
Every feature should include:
- Validation
- Error handling
- Loading states
- Empty states
- Responsive UI
- Accessibility
- Type safety
- Logging where appropriate
---
## 14. Consistency
Always follow the same coding style.
No mixed conventions.
No unnecessary abstractions.
No overengineering.
---
# Token Optimization Rules
Instead of rewriting entire files:
✅ show only modified sections.
Avoid explaining code unless requested.
Avoid repeating project summaries.
Avoid generating documentation unless requested.
Avoid generating installation commands repeatedly.
Never regenerate components that already exist.
Never regenerate APIs that are unchanged.
---
# Project Goal
Project Name:
MarketLens
Objective:
Develop a full-stack AI-powered stock market platform with:
- Stock price prediction
- Real-time market data
- Interactive charts
- Technical indicators
- Portfolio tracking
- Watchlist
- Authentication
- AI insights
- News sentiment analysis
- Responsive web app
- Mobile app
The final result should be production-ready, scalable, maintainable, and deployment-ready.
---
# Response Priority
1. Correctness
2. Maintainability
3. Scalability
4. Performance
5. Token Efficiency
Token efficiency must NEVER reduce software quality.