Rename all workflow rules to verb-workflow-name format and update tiles accordingly

tjementum · tjementum · commit f25dde92189f · 2025-05-28T15:22:59.000+02:00
diff --git a/.cursor/rules/workflows/commit-changes.mdc b/.cursor/rules/workflows/commit-changes.mdc
@@ -3,7 +3,7 @@ description: Workflow for writing effective git commit messages
 globs: 
 alwaysApply: false
 ---
-# Git Commit Workflow
+# Commite Changes Workflow
 
 Follow these steps to commit changes:
 
diff --git a/.cursor/rules/workflows/create-prd.mdc b/.cursor/rules/workflows/create-prd.mdc
@@ -3,6 +3,8 @@ description: Workflow for creating a product requirement description (PRD)
 globs: 
 alwaysApply: false
 ---
+# Create PRD Workflow
+
 The user will provide a description of a new feature. Your job is to work with the user to do research and create a high-level PRD using language that is easy to understand for non-technical people.
 
 The output will be a `./task-manager/[prd-title]/prd.md` file with the high-level PRD description and overview of product increments needed to implement the feature.
diff --git a/.cursor/rules/workflows/implement-product-increment.mdc b/.cursor/rules/workflows/implement-product-increment.mdc
@@ -3,7 +3,7 @@ description: Workflow for implementing tasks for a product increment
 globs: 
 alwaysApply: false
 ---
-# Implement tasks within a product increment
+# Implement Product Increment Workflow
 
 The user will provide a link to files with a PRD and a product increment description, or links to a backlog item in [PRODUCT_MANAGEMENT_TOOL] with the PRD and a link to a product increment. Your job is to implement the tasks defined in the product increment. If no product increment is provided, inspect all product increments to find the first product increment that has not been fully completed.
 
diff --git a/.cursor/rules/workflows/plan-product-increment.mdc b/.cursor/rules/workflows/plan-product-increment.mdc
@@ -3,6 +3,8 @@ description: Workflow for creating small product increments based on a product r
 globs: 
 alwaysApply: false
 ---
+# Plan Product Increment Workflow
+
 The user will provide a link to a product requirement description (PRD) or a link to a backlog item in [PRODUCT_MANAGEMENT_TOOL], and ask you to create technical tasks for one product increment.
 
 The goal is to create a `./task-manager/[prd-title]/[#-increment-title].md` file with low-level technical tasks and, when approved, create matching tasks in [PRODUCT_MANAGEMENT_TOOL].
diff --git a/.cursor/rules/workflows/prepare-pull-request.mdc b/.cursor/rules/workflows/prepare-pull-request.mdc
@@ -3,7 +3,7 @@ description: Workflow for writing pull request titles and descriptions
 globs: 
 alwaysApply: false
 ---
-# Pull Request Workflow
+# Prepare Pull Request Workflow
 
 Follow these steps to create pull request titles and descriptions:
 
diff --git a/.cursor/rules/workflows/review-code.mdc b/.cursor/rules/workflows/review-code.mdc
@@ -3,7 +3,7 @@ description: Workflow for code review of branches, uncommitted changes, or files
 globs: 
 alwaysApply: false
 ---
-# Code Review Workflow
+# Review Code Workflow
 
 Follow these steps carefully to review files *one by one*:
 
diff --git a/.cursor/rules/workflows/update-ai-rules.mdc b/.cursor/rules/workflows/update-ai-rules.mdc
@@ -3,7 +3,7 @@ description: Workflow for creating and maintaining AI rules
 globs: 
 alwaysApply: false
 ---
-# AI Rules Workflow
+# Update AI Rules Workflow
 
 Follow these steps to create and update AI rules files. Rules should be created in appropriate subfolders of the `.cursor/` directory, with clear file names that reflect their purpose (e.g., `.cursor/rules/backend/strongly-typed-ids.mdc`, `.cursor/rules/frontend/tanstack-query-api-integration.mdc`).
 
