.cursorrules Node.js MongoDB JWT Express React

by @allxdamnxday

Tech Stack:

Backend: Node.js with Express.js  
Database: MongoDB with Mongoose ODM  
Frontend: React.js (for admin panel, if required)  
Authentication: JSON Web Tokens (JWT)  
Version Control: Git  
Deployment: Docker (optional)  

Precision in User Requirements:

Strictly adhere to specified user flow and game rules.  

Strategy: 

Summarize the pick submission process and outline the API endpoint and business logic in pseudocode before coding.  

Strategic Planning with Pseudocode:

Begin each feature with detailed pseudocode.  
Example: Provide pseudocode for the weekly scoring process, detailing steps from game result input to entry status updates.  

Code Quality:

Ensure secure, efficient code following RESTful API best practices.  
Implement proper error handling and input validation.  

User Flow:

Users browse available Pools  
Submit up to 3 Requests per Pool  
Complete payment for Requests  
Admin approves/rejects Requests  
Approved Requests become Entries  

Entry Management:

Each user can have up to 3 Entries per Pool  
Entries are numbered 1, 2, 3  
Picks are made and tracked separately for each Entry  

Pick Management:

Users make Picks for each Entry separately  
Picks can be updated until deadline (game start or 1PM Sunday of the current week of the pick)  

Scoring and Ranking:

Picks scored after games complete  
Win: Entry moves to next week  
Loss: Entry eliminated from Pool  
Each Entry ranked separately in Pool standings  

Results and Standings:

Users view Picks/scores for each Entry separately  
Pool standings show all Entries (multiple per User possible)  
Pool members can view all Picks after scoring  

Key Implementation Points:

Limit Requests to 3 per User per Pool  
Track Requests and Entries separately (numbered 1, 2, 3)  
Implement payment status tracking in Request model  
Create Entry only after admin approval and payment completion  
Admin interface for managing and approving Requests  
Implement state transitions (Request: pending -> approved -> Entry created)

Pool Management Platform

A comprehensive suite of tools for managing sports betting pools, focusing on user engagement, fair play, and secure transactions.

Core Features

Pool Management Platform:
Allows users to browse pools, submit requests, and manage entries with an admin panel for managing requests, payments, and entries.
Pick-and-Pay System:
Enables users to submit requests and securely complete payments, tracking payment status and automating entry creation upon approval.
Request Approval Dashboard:
An admin-focused dashboard for reviewing, approving, or rejecting user requests with status tracking for payments and request progression.

Entry & Scoring Management

Entry and Scoring System:
Handles entry creation post-approval, manages user picks, and automates scoring to update standings.
User Standings Display:
Presents detailed pool standings, showing user rankings and allowing them to view picks and scores.

Compliance & Planning Tools

Request and Entry Limitation Module:
Enforces limits on requests and entries per user to ensure compliance with system rules.
Pick Deadline Management Tool:
Allows users to make or update picks until a set deadline, ensuring fair play and timely submissions.
Pseudocode Strategy Planner:
Helps developers outline API endpoints and business logic in pseudocode for strategic planning.

Security & Payment Integration

Payment Status Integration:
Tracks and updates payment status to ensure entries are created only after payment completion and admin approval.
Secure Authentication Service:
A JWT-based authentication system ensuring secure access control for users and admins.

Key Technologies:

React.js (Frontend)
RESTful API (Backend)
JWT Authentication
Payment Gateways

Overview of .cursorrules prompt

The .cursorrules file provides a comprehensive blueprint for a software project involving a backend integrated with Node.js and Express.js, and a frontend potentially using React.js. It utilizes MongoDB with Mongoose for database management and employs JSON Web Tokens for authentication. Git is suggested for version control, with Docker being optional for deployment. The file emphasizes precision in user requirements, especially adhering to game rules and user flow, and recommends starting feature implementation with detailed pseudocode. It outlines the user journey through the application, from browsing pools to submitting requests, handling payments, and managing entries. It describes a structured process for administering requests, creating entries, and managing picks, while maintaining code quality through secure and efficient practices. Lastly, it offers guidance on implementing state transitions and tracking elements such as requests, entries, and payment status.

Updated: March 17, 2025

Developers could use this prompt to build a pool-based game application with user submissions, payment processing, and admin approval workflows, leveraging Node.js, MongoDB, and React.js for efficient user and entry management.

Usefull for: