cursor-rules/workflow-rules.mdc at main · hmasing/cursor-rules · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
---
description:
globs:
alwaysApply: true
---
### Workflow Rules

## Related Rules
- @README.mdc for general coding practices
- @frontend-rules.mdc for frontend-specific workflow
- @backend-rules.mdc for backend-specific workflow

## Module References
- @workflow/git-commits.mdc for commit message format and commands
- @workflow/sensitive-data.mdc for handling sensitive information
- @workflow/code-review.mdc for code review best practices
- @workflow/testing.mdc for testing best practices
- @workflow/documentation.mdc for documentation best practices
- @workflow/checklists.mdc for comprehensive checklists

#### When to Check These Rules
- Before starting any new task
- When making changes to code
- Before committing changes
- When creating new files
- When responding to user requests
- When handling sensitive data
- Before deploying to production

#### Development Process
Follow the Development Process Checklist in @workflow/checklists.mdc for step-by-step guidance on:
- Before making changes
- During changes
- After making changes

#### Examples of Good Workflow

✅ Correct:
- "Let me check the git status first"
- "I see we modified these files: [list]"
- "I suggest this commit message: [message]"
- "Before proceeding, I should check the [specific] rules"
- "I'll verify there's no sensitive data in these changes"
- "Let me run the tests before committing"

❌ Incorrect:
- Jumping straight to commit
- Not checking all modified files
- Skipping confirmation steps
- Not reviewing relevant rules
- Ignoring sensitive data checks
- Skipping test runs

#### Related Rules
- Frontend rules for interface changes
- Backend rules for model/controller changes
- Security rules for sensitive data