This system prompt configures Cursor to work with three core documentation files that form the backbone of project management and development tracking. The files work in concert to maintain project coherence and documentation accuracy.
Sign in to like and favorite skills
I want you to act as an English translator, spelling corrector and improver. I will speak to you in any language and you will detect the language, translate it and answer in the corrected and improved...
Act as a Game Description Writer. You are responsible for crafting an engaging and informative overview of the mobile game '${gameName:Bake Merge Bounty}'. Your task is to highlight the core gameplay...
You are a specialized assistant for Google VEO3 video generation, designed to help users create, enhance, and optimize text prompts for high-quality video output. Your expertise encompasses the complete VEO3 prompting framework, technical specifications, and creative best practices.
This system prompt configures Cursor to work with three core documentation files that form the backbone of project management and development tracking. The files work in concert to maintain project coherence and documentation accuracy.
Before any operation, locate the core documentation files in the following order:
Search common locations:
# Primary locations ./task-log.md ./src/*/dev/task-log.md ./docs/task-log.md # Dev documentation ./src/*/dev/dev-notes.md ./dev-notes.md ./docs/dev-notes.md # Project structure ./src/*/dev/file-tree.md ./file-tree.md ./docs/file-tree.md
If files not found, search workspace:
find . -name "task-log.md" -o -name "dev-notes.md" -o -name "file-tree.md"
File creation hierarchy if not found: a. Root directory:
task-log.mddev-notes.mdfile-tree.mdfile-tree.mddev-notes.mdtask-log.md- 🔴 Not Started - 🟡 In Progress - 🟢 Completed - ⭕️ Blocked - 🔵 Testing - ✅ Verified
File Update Order: a.
file-tree.mddev-notes.mdtask-log.mdCross-referencing Requirements:
Documentation Standards:
Before Task:
1. Review task-log.md → Task details 2. Check file-tree.md → Implementation context 3. Consult dev-notes.md → Technical requirements
During Task:
1. Record commands used 2. Document technical decisions 3. Track performance metrics 4. Note configuration changes
After Task:
1. Update task-log.md → Progress 2. Update file-tree.md → Structure 3. Update dev-notes.md → Details
Task Progress Update:
## Task Progress - [Date] ### Current Implementation 🎯 Task: [Task Name] 📊 Progress: [Percentage] #### Changes Made - [Status] [Component] #### Technical Metrics - [Metric]: [Value] #### Next Steps 1. [Next Task]
Implementation Details:
## Implementation Notes - [Date] ### [Component] Enhancement ✨ New Features: - [Feature] * [Details] 🔧 Configuration: ```json { "setting": "value" }
📊 Performance Impact:
undefined
Task Completion:
## Task Completion Summary - [Date] ### Task Overview 🎯 Task: [Name] 📂 Files Modified: - `[path]` - [summary] ### Implementation Details ✨ Changes Made: [Details] ### Testing & Commands ✅ Tests: [Results] 🖥️ Commands: ```bash [commands]
🎯 Purpose: [Impact]
➡️ Follow-up: [Tasks]
undefined
Task Organization:
Documentation Updates:
Technical Documentation:
Documentation Sync:
Progress Tracking:
Technical Verification:
Task Documentation:
Progress Tracking:
Technical Documentation:
Remember: This system prompt ensures consistent project documentation and management across all development activities in Cursor.