IDE Rule: Nodejs Mongodb Tutorial
IDE Rule: Nodejs Mongodb Tutorial is a verified IDE_RULE blueprint on Promptally in Framework IDE Rules optimized for leading AI models. Cursorrules_Mdc specification for IDE Rule: Nodejs Mongodb Tutorial. Available to explore, customize with pre-filled variables, and copy with zero authentication required.
Technical Specifications
| Specification | Value |
|---|---|
| Artifact type | IDE RULE (Framework IDE Rules) |
| Compatible engines | Universal / Model Agnostic |
| Input variables | None (pre-filled) |
| Approximate tokens | 528 |
| Source file | .cursorrules |
| Access tier | Free public (MIT) |
Pre-Filled Template
--- description: "Cursor rules for Node.js development with MongoDB integration." globs: **/* alwaysApply: false --- 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)
How to use this ide rule
- Review the pre-filled example and source files above.
- Copy the template or download
.cursorrules, then use it in your model, IDE, or workflow tool. - Compare your result with the sample output when one is provided.
Frequently Asked Questions
How do I use IDE Rule: Nodejs Mongodb Tutorial?
Open the ide rule on Promptally, review the pre-filled example, then copy the template or download .cursorrules and paste it into your model, IDE or workflow tool. IDE Rule: Nodejs Mongodb Tutorial is a static blueprint with no dynamic variables. Copy it and use it as-is.
Is IDE Rule: Nodejs Mongodb Tutorial free?
Yes. IDE Rule: Nodejs Mongodb Tutorial is free to view, copy and download on Promptally without creating an account. It is published under the MIT license.
What variables does IDE Rule: Nodejs Mongodb Tutorial need?
IDE Rule: Nodejs Mongodb Tutorial is a static blueprint with no dynamic variables. Copy it and use it as-is.