From 3c23797acea3acd7a1db546e9b20bbe885ca578e Mon Sep 17 00:00:00 2001 From: Joe Danziger Date: Mon, 26 May 2025 22:59:18 -0400 Subject: [PATCH] update rules --- assets/rules/dev_workflow.mdc | 8 ++++---- assets/rules/taskmaster.mdc | 2 +- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/assets/rules/dev_workflow.mdc b/assets/rules/dev_workflow.mdc index 249ae9a3..29f1f4c8 100644 --- a/assets/rules/dev_workflow.mdc +++ b/assets/rules/dev_workflow.mdc @@ -49,12 +49,12 @@ Task Master offers two primary ways to interact: - Maintain valid dependency structure with `add_dependency`/`remove_dependency` tools or `task-master add-dependency`/`remove-dependency` commands, `validate_dependencies` / `task-master validate-dependencies`, and `fix_dependencies` / `task-master fix-dependencies` (see [`taskmaster.mdc`](mdc:.cursor/rules/taskmaster.mdc)) when needed - Respect dependency chains and task priorities when selecting work - Report progress regularly using `get_tasks` / `task-master list` -- Reorganize tasks as needed using `move_task` / `task-master move --from= --to=` (see @`taskmaster.mdc`) to change task hierarchy or ordering +- Reorganize tasks as needed using `move_task` / `task-master move --from= --to=` (see [`taskmaster.mdc`](mdc:.cursor/rules/taskmaster.mdc)) to change task hierarchy or ordering ## Task Complexity Analysis -- Run `analyze_project_complexity` / `task-master analyze-complexity --research` (see @`taskmaster.mdc`) for comprehensive analysis -- Review complexity report via `complexity_report` / `task-master complexity-report` (see @`taskmaster.mdc`) for a formatted, readable version. +- Run `analyze_project_complexity` / `task-master analyze-complexity --research` (see [`taskmaster.mdc`](mdc:.cursor/rules/taskmaster.mdc)) for comprehensive analysis +- Review complexity report via `complexity_report` / `task-master complexity-report` (see [`taskmaster.mdc`](mdc:.cursor/rules/taskmaster.mdc)) for a formatted, readable version. - Focus on tasks with highest complexity scores (8-10) for detailed breakdown - Use analysis results to determine appropriate subtask allocation - Note that reports are automatically used by the `expand_task` tool/command @@ -179,7 +179,7 @@ Taskmaster configuration is managed through two main mechanisms: Once a task has been broken down into subtasks using `expand_task` or similar methods, follow this iterative process for implementation: 1. **Understand the Goal (Preparation):** - * Use `get_task` / `task-master show ` (see @`taskmaster.mdc`) to thoroughly understand the specific goals and requirements of the subtask. + * Use `get_task` / `task-master show ` (see [`taskmaster.mdc`](mdc:.cursor/rules/taskmaster.mdc)) to thoroughly understand the specific goals and requirements of the subtask. 2. **Initial Exploration & Planning (Iteration 1):** * This is the first attempt at creating a concrete implementation plan. diff --git a/assets/rules/taskmaster.mdc b/assets/rules/taskmaster.mdc index 00545a81..94acad24 100644 --- a/assets/rules/taskmaster.mdc +++ b/assets/rules/taskmaster.mdc @@ -425,4 +425,4 @@ Environment variables are used **only** for sensitive API keys related to AI pro --- -For details on how these commands fit into the development process, see the @Development Workflow Guide. +For details on how these commands fit into the development process, see the [Development Workflow Guide](mdc:.cursor/rules/dev_workflow.mdc).