.cursorrules (deprecated)

1Tech Stack:
2 
3Backend: Node.js with Express.js
4 
5Database: MongoDB with Mongoose ODM
6 
7Frontend: React.js (for admin panel, if required)
8 
9Authentication: JSON Web Tokens (JWT)
10 
11Version Control: Git
12 
13Deployment: Docker (optional)
14 
15Precision in User Requirements:
16 
17Strictly adhere to specified user flow and game rules.
18 
19Strategy: 
20 
21Summarize the pick submission process and outline the API endpoint and business logic in pseudocode before coding.
22 
23Strategic Planning with Pseudocode:
24 
25Begin each feature with detailed pseudocode.
26 
27Example: Provide pseudocode for the weekly scoring process, detailing steps from game result input to entry status updates.
28 
29Code Quality:
30 
31Ensure secure, efficient code following RESTful API best practices.
32 
33Implement proper error handling and input validation.
34 
35User Flow:
36 
37Users browse available Pools
38 
39Submit up to 3 Requests per Pool
40 
41Complete payment for Requests
42 
43Admin approves/rejects Requests
44 
45Approved Requests become Entries
46 
47Entry Management:
48 
49Each user can have up to 3 Entries per Pool
50 
51Entries are numbered 1, 2, 3
52 
53Picks are made and tracked separately for each Entry
54 
55Pick Management:
56 
57Users make Picks for each Entry separately
58 
59Picks can be updated until deadline (game start or 1PM Sunday of the current week of the pick)
60 
61Scoring and Ranking:
62 
63Picks scored after games complete
64 
65Win: Entry moves to next week
66 
67Loss: Entry eliminated from Pool
68 
69Each Entry ranked separately in Pool standings
70 
71Results and Standings:
72 
73Users view Picks/scores for each Entry separately
74 
75Pool standings show all Entries (multiple per User possible)
76 
77Pool members can view all Picks after scoring
78 
79Key Implementation Points:
80 
81Limit Requests to 3 per User per Pool
82 
83Track Requests and Entries separately (numbered 1, 2, 3)
84 
85Implement payment status tracking in Request model
86 
87Create Entry only after admin approval and payment completion
88 
89Admin interface for managing and approving Requests
90 
91Implement state transitions (Request: pending -> approved -> Entry created)
92 
93