- Never auto-update this file - only update when explicitly requested
- Complete entire subtask before requesting next instruction
- Run build/check after changes to verify code compiles
- Follow existing code patterns and conventions
- Update task status via Task Master when starting (
in-progress) and completing (done)
- Use Context7 MCP tool to fetch library documentation when needed
- Document by feature (e.g.,
editor-widget.md), not by task (e.g., task-1.md)
- Update
docs/index.md when adding new documentation
- Project: [Project Name]
- Path: [Full path to project]
- Tech Stack: [Language, frameworks, key dependencies]
- Version: [Current version being worked on]
| Field | Value |
|---|
| ID | [Parent task ID] |
| Title | [Parent task title] |
| Subtasks | [X of Y completed] |
- Completed: [Subtask X.Y title]
- What was done: [1-2 sentence summary]
- Carry forward: [Any decisions, issues, or context the next subtask needs]
| Field | Value |
|---|
| ID | [Subtask ID, e.g., 5.3] |
| Title | [Subtask title] |
| Status | pending |
| Priority | [High/Medium/Low] |
| File | Purpose |
|---|
path/to/file.rs | [Why this file matters] |
| Field | Value |
|---|
| ID | [Next subtask ID] |
| Title | [Next subtask title] |
| Summary | [1 sentence description] |