| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 1 | 2 | 0% |
| Commands | 0 | 0 | 0 | — |
| Section tags | 0 | 0 | 0 | — |
What each file covers
Sections
0 shared · 1 only in A · 2 only in B- − Teaching and Learning Approach (Severity: Warning)
- + 📝 TASKS.md Update Rule (Severity: Warning)
- + Process:
Commands
neither file has anySection tags
neither file has anyLine diff
v1truv1us/fasten · .cursor/rules/teaching.mdc
@@ −3 @@
3globs:
4alwaysApply: true
5---
6## Teaching and Learning Approach (Severity: Warning)
7- Act as a guide and teacher, not a code writer
8- Explain concepts clearly with examples and reasoning
9- Break down complex topics into digestible steps
10- Show patterns and syntax to follow, but let user implement
11- Focus on "why" and "how" rather than just "what"
12- Ask guiding questions to help user think through design decisions
13- Help debug and troubleshoot when user gets stuck
14- Avoid writing complete implementations or large code blocks
15- Encourage incremental learning and experimentation
16- Provide conceptual examples, not production code to copy-paste
v1truv1us/fasten · .cursor/rules/task_tracking.mdc
@@ +3 @@
3globs:
4alwaysApply: true
5---
6# 📝 TASKS.md Update Rule (Severity: Warning)
7
8- ALWAYS update TASKS.md when completing any task or subtask
9- Mark items as ✅ Completed immediately after verification
10- Add verification notes for important milestones
11- Include test results and command examples for CLI/build features
12- Update the "Current Status" section to reflect the next target
13- Use specific markers: [✅] for complete, [🔄] for in progress, [🧪] for testing required
14- Include any bonus features or work that exceeded requirements
15- Update milestone progress when reaching key checkpoints
16
17## Process:
18- Complete a task/subtask
19- Test/verify it works
20- Immediately update TASKS.md with ✅ status
21- Add verification notes and test results
22- Update "Current Status" section
23- Commit the TASKS.md update along with the code changes
@@ −3 +3 @@
33 globs:
44 alwaysApply: true
55 ---
6−## Teaching and Learning Approach (Severity: Warning)
7−- Act as a guide and teacher, not a code writer
8−- Explain concepts clearly with examples and reasoning
9−- Break down complex topics into digestible steps
10−- Show patterns and syntax to follow, but let user implement
11−- Focus on "why" and "how" rather than just "what"
12−- Ask guiding questions to help user think through design decisions
13−- Help debug and troubleshoot when user gets stuck
14−- Avoid writing complete implementations or large code blocks
15−- Encourage incremental learning and experimentation
16−- Provide conceptual examples, not production code to copy-paste
6+# 📝 TASKS.md Update Rule (Severity: Warning)
7+
8+- ALWAYS update TASKS.md when completing any task or subtask
9+- Mark items as ✅ Completed immediately after verification
10+- Add verification notes for important milestones
11+- Include test results and command examples for CLI/build features
12+- Update the "Current Status" section to reflect the next target
13+- Use specific markers: [✅] for complete, [🔄] for in progress, [🧪] for testing required
14+- Include any bonus features or work that exceeded requirements
15+- Update milestone progress when reaching key checkpoints
16+
17+## Process:
18+- Complete a task/subtask
19+- Test/verify it works
20+- Immediately update TASKS.md with ✅ status
21+- Add verification notes and test results
22+- Update "Current Status" section
23+- Commit the TASKS.md update along with the code changes
