AI SummaryCursor Rules for managing task lists in Markdown to track project progress during development. Helps developers and AI assistants maintain structured task tracking across features.
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to add the "mcp-nodemailer — Cursor Rules" prompt rules to my project. Repository: https://github.com/decloudz/mcp-nodemailer Please read the repo to find the rules/prompt file, then: 1. Download it to the correct location (.cursorrules, .windsurfrules, .github/prompts/, or project root — based on the file type) 2. If there's an existing rules file, merge the new rules in rather than overwriting 3. Confirm what was added
Description
Cursor Rules for mcp-nodemailer
Task List Management
Guidelines for creating and managing task lists in Markdown files to track project progress
Task List Creation
• Create task lists in a markdown file (in the project root): • Use TASKS.md or a descriptive name relevant to the feature (e.g., ASSISTANT_CHAT.md) • Include a clear title and description of the feature being implemented • Structure the file with these sections: `markdown # Feature Name Implementation Brief description of the feature and its purpose. ## Completed Tasks • [x] Task 1 that has been completed • [x] Task 2 that has been completed ## In Progress Tasks • [ ] Task 3 currently being worked on • [ ] Task 4 to be completed soon ## Future Tasks • [ ] Task 5 planned for future implementation • [ ] Task 6 planned for future implementation ## Implementation Plan Detailed description of how the feature will be implemented. ### Relevant Files • path/to/file1.ts - Description of purpose • path/to/file2.ts - Description of purpose `
Task List Maintenance
• Update the task list as you progress: • Mark tasks as completed by changing [ ] to [x] • Add new tasks as they are identified • Move tasks between sections as appropriate • Keep "Relevant Files" section updated with: • File paths that have been created or modified • Brief descriptions of each file's purpose • Status indicators (e.g., ✅) for completed components • Add implementation details: • Architecture decisions • Data flow descriptions • Technical components needed • Environment configuration
AI Instructions
When working with task lists, the AI should: • Regularly update the task list file after implementing significant components • Mark completed tasks with [x] when finished • Add new tasks discovered during implementation • Maintain the "Relevant Files" section with accurate file paths and descriptions • Document implementation details, especially for complex features • When implementing tasks one by one, first check which task to implement next • After implementing a task, update the file to reflect progress
Discussion
Health Signals
My Fox Den
Community Rating
Sign in to rate this booster
Works With
Any AI assistant that accepts custom rules or system prompts