Cursor rule

1---
2description:
3globs:
4alwaysApply: true
5---
6# Task List Management
7 
8Guidelines for managing task lists in markdown files to track progress on completing a PRD and its technical specification
9 
10## Task Implementation
11 
12<critical>
13**MANDATORY REQUIREMENTS:**
14- **ALWAYS** check dependent files APIs before write tests to avoid write wrong code
15- **ALWAYS** verify against PRD and tech specs - NEVER make assumptions
16- **NEVER** use workarounds, especially in tests - implement proper solutions
17- **MUST** follow all established project standards:
18    - Architecture patterns: `.cursor/rules/architecture.mdc`
19    - Go coding standards: `.cursor/rules/go-coding-standards.mdc`
20    - Testing requirements: `.cursor/rules/testing-standards.mdc`
21    - API standards: `.cursor/rules/api-standards.mdc`
22    - Security & quality: `.cursor/rules/quality-security.mdc`
23- **MUST** run `make lint` and `make test` before completing ANY subtask
24- **MUST** follow `.cursor/rules/task-review.mdc` workflow for parent tasks
25**Enforcement:** Violating these standards results in immediate task rejection.
26</critical>
27 
28<completion_protocol>
291. When you finish a **sub‑task**, immediately mark it as completed by changing `[ ]` to `[x]`.
302. If **all** subtasks underneath a parent task are now `[x]`, also mark the **parent task** as completed.
31- Stop after each sub‑task and wait for the user's go‑ahead.
32</completion_protocol>
33 
34## Task List Maintenance
35 
36<maintenance_rules>
371. **Update the task list as you work:**
38   - Mark tasks and subtasks as completed (`[x]`) per the protocol above.
39   - Add new tasks as they emerge.
40 
412. **Maintain the "Relevant Files" section:**
42   - List every file created or modified.
43   - Give each file a one‑line description of its purpose.
44</maintenance_rules>
45 
46## AI Instructions
47 
48<ai_workflow>
49When working with task lists, the AI must:
50 
511. Regularly update the task list file after finishing any significant work.
522. Follow the completion protocol:
53   - Mark each finished **sub‑task** `[x]`.
54   - Mark the **parent task** `[x]` once **all** its subtasks are `[x]`.
553. Add newly discovered tasks.
564. Keep "Relevant Files" accurate and up to date.
575. Before starting work, check which sub‑task is next.
586. After implementing a sub‑task, update the file and then pause for user approval.
597. **ALWAYS** use the task.mdc file as the primary reference for implementation
608. **NEVER** skip test assertions defined in the task requirements
61</ai_workflow>
62