.cursorrules (deprecated)

1# AI Assistant Technical Instructions
2 
3You are an AI assistant with advanced problem-solving capabilities. Please follow these instructions to execute tasks efficiently and accurately.
4 
5First, confirm the instructions received from the user:
6 
7<instructions>
8{{instructions}}
9</instructions>
10 
11Please proceed with the following process based on these instructions:
12 
13---
14 
15## 1. Instruction Analysis and Planning
16 
17<Task Analysis>
18- Summarize the main tasks concisely
19- Review the specified tech stack and consider implementation methods within those constraints  
20  **Note: Do not change versions listed in the tech stack without approval**
21- Identify key requirements and constraints
22- List potential challenges
23- Enumerate specific steps for task execution in detail
24- Determine the optimal execution order for these steps
25 
26### Preventing Duplicate Implementation
27 
28Before implementation, verify:
29- Existence of similar functionality
30- Functions or components with identical or similar names
31- Duplicate API endpoints
32- Identification of processes that can be shared
33 
34Take sufficient time for this section as it guides the entire subsequent process. Conduct thorough and comprehensive analysis.
35</Task Analysis>
36 
37---
38 
39## 2. Task Execution
40 
41- Execute identified steps one by one
42- Report progress concisely after completing each step
43- Pay attention to the following during implementation:
44  - Adherence to proper directory structure
45  - Consistency in naming conventions
46  - Appropriate placement of shared processes
47 
48---
49 
50## 3. Quality Control and Problem Resolution
51 
52- Quickly verify the execution results of each task
53- If errors or inconsistencies occur, address them through the following process:
54  a. Problem isolation and cause identification (log analysis, debug information verification)
55  b. Creation and implementation of countermeasures
56  c. Post-fix operation verification
57  d. Debug log confirmation and analysis
58 
59- Record verification results in the following format:
60  a. Verification items and expected results
61  b. Actual results and discrepancies
62  c. Required countermeasures (if applicable)
63 
64---
65 
66## 4. Final Confirmation
67 
68- Evaluate the entire deliverable once all tasks are completed
69- Verify consistency with original instructions and make adjustments as needed
70- Perform final confirmation that there are no duplicates in implemented functions
71 
72---
73 
74## 5. Results Report
75 
76Please report final results in the following format:
77 
78markdown
79# Execution Results Report
80 
81## Overview
82 
83[Brief description of overall summary]
84 
85## Execution Steps
86 
871. [Step 1 description and results]
882. [Step 2 description and results]
89...
90 
91## Final Deliverables
92 
93[Details of deliverables, links if applicable]
94 
95## Issue Resolution (if applicable)
96 
97- Problems encountered and responses
98- Future considerations
99 
100## Notes & Improvement Suggestions
101 
102- [List any observations or suggestions for improvement]
103 
104---
105 
106## Important Notes
107 
108- Always confirm any unclear points before beginning work
109- Report and obtain approval for any important decisions as they arise
110- Report unexpected problems immediately and propose solutions
111- **Do not make changes that are not explicitly instructed.** If changes seem necessary, first report them as proposals and implement only after approval
112- **UI/UX design changes (layout, colors, fonts, spacing, etc.) are prohibited** unless approved after presenting justification
113- **Do not arbitrarily change versions listed in the tech stack** (APIs, frameworks, libraries, etc.). If changes are necessary, clearly explain the reason and wait for approval before making any changes
114 
115---
116 
117# Tech Stack
118 
119## Core Technologies
120 
121- **AI Model: GPT-4**
122 
123## Frontend
124 
125- Flutter: ^3.22.0
126 
127### State Management
128 
129- Riverpod: ^2.6.1
130 
131## BaaS
132 
133- Firebase
134 
135---
136 
137## Project Structure
138 
139Please implement following this directory structure:
140 
141lib/features/products/
142├── data/
143│   ├── models/
144│   │   ├── product_dto.dart
145│   │   └── product_category_dto.dart
146│   └── product_repository.dart
147├── presentation/
148│   ├── screens/
149│   │   ├── product_list_screen.dart
150│   │   └── product_details_screen.dart
151│   ├── controllers/
152│   │   └── product_list_controller.dart
153│   ├── widgets/
154│       └── product_card.dart
155├── domain/
156│   ├── models/
157│   │   ├── product.dart
158│   │   └── product_category.dart
159│   └── get_products_use_case.dart
160└── shared/
161    └── models/
162        └── address.dart
163 
164## Placement Rules
165 
166### Flutter Project Structure Placement Rules
167 
168This document outlines the placement rules for files and folders within the recommended Flutter project structure, focusing on scalability, maintainability, and adherence to Clean Architecture principles.
169 
170#### Top-Level Structure
171 
172lib/
173├── features/
174├── models/
175├── providers/
176├── routes/
177├── core/
178├── app.dart
179└── main.dart
180 
181*   **lib/**: Contains all Dart code.
182*   **features/**: Feature-specific code.
183*   **models/**: Global models (use sparingly).
184*   **providers/**: Global providers (minimize use).
185*   **routes/**: App navigation.
186*   **core/**: Core app logic (networking, errors, DI).
187*   **app.dart**: Root widget.
188*   **main.dart**: Entry point.
189 
190#### features/ Structure
191 
192lib/features/
193└── <feature_name>/
194├── data/
195│   ├── models/
196│   └── <feature_name>_repository.dart
197├── presentation/
198│   ├── screens/
199│   ├── controllers/
200│   ├── widgets/
201├── domain/
202│   ├── models/
203│   └── <feature_name>.dart
204├── use_cases/
205└── shared/
206└── models/
207 
208*   **<feature_name>/**: A feature (e.g., authentication, products).
209*   **data/**: Data access.
210    *   **models/**: Data Transfer Objects (DTOs).
211    *   **<feature_name>_repository.dart**: Data access logic.
212*   **presentation/**: UI.
213    *   **screens/**: UI screens (<feature_name>_<screen_name>_screen.dart).
214    *   **controllers/**: State management (<feature_name>_controller.dart).
215    *   **widgets/**: Feature-specific widgets (<widget_name>.dart).
216*   **domain/**: Business logic.
217    *   **models/**: Domain models.
218    *   **<feature_name>.dart**: Main entity.
219*   **use_cases/**: User interactions (<use_case_name>.dart).
220*   **shared/models/**: Models shared between *related* features.
221 
222#### shared/ (Top-Level) Structure
223 
224lib/shared/
225├── providers/
226├── widgets/
227├── models/
228└── services/
229 
230*   **providers/**: Providers shared across *unrelated* features.
231*   **widgets/**: Widgets shared across *unrelated* features.
232*   **models/**: Models shared across *unrelated* features (use cautiously).
233*   **services/**: Utility classes.
234 
235#### models/ (Top-Level) Structure
236 
237lib/models/
238└── <model_name>.dart
239 
240*   Global models (use sparingly).
241 
242#### providers/ (Top-Level) Structure
243 
244lib/providers/
245└── <provider_name>.dart
246 
247*   Global providers (minimize use).
248 
249#### core/ Structure
250 
251lib/core/
252├── network/
253│   └── api_client.dart
254├── errors/
255│   └── exceptions.dart
256└── di/
257└── injection.dart
258 
259*   **network/**: Networking code.
260*   **errors/**: Error handling.
261*   **di/**: Dependency injection.
262 
263## Naming Conventions
264 
265*   **Files:** snake_case (e.g., product_list_screen.dart).
266*   **Classes:** PascalCase (e.g., ProductListScreen).
267*   **Variables/Functions:** camelCase (e.g., productList).
268 
269## Key Principles
270 
271*   **Feature Isolation:** Self-contained feature code.
272*   **Separation of Concerns:** Separate data, logic, and UI.
273*   **Single Responsibility:** One purpose per class/file.
274*   **DRY:** Avoid code duplication.
275*   **Prefer Feature-Specific:** Prioritize feature-level placement.
276 
277Please adhere to the above content when executing tasks.
278 
279