| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 1 | 12 | 16 | 3% |
| Commands | 0 | 0 | 0 | — |
| Section tags | 0 | 2 | 1 | 0% |
What each file covers
Sections
1 shared · 12 only in A · 16 only in B- − 🔄 Active Context
- − Current Focus
- − Recent Changes
- − Current Challenges
- − Active Decisions
- − Key Patterns & Preferences
- − Code Patterns
- − Architectural Decisions
- − Team Preferences
- − Learnings & Insights
- − Open Questions
- − Notes
- + 📊 Progress
- + Project Status
- + Completed Features
- + In-Progress Features
- + Pending Features
- + Known Issues
- + Critical
- + High Priority
- + Medium Priority
- + Low Priority
- + Technical Debt
- + Recent Milestones
- + Upcoming Milestones
- + Performance Metrics
- + Decision Log
- + Lessons Learned
- Next Steps
Commands
neither file has anySection tags
0 shared · 2 only in A · 1 only in B- − code-style
- − architecture
- + performance
Line diff
ruvnet/rUv-dev · .clinerules/🔄_activeContext.md
@@ −1 @@
1# 🔄 Active Context
2
3## Current Focus
4The current focus is on integrating the SPARC methodology into the `.clinerules/` folder structure. This includes updating core rule files, enhancing the memory bank system, and ensuring the system supports structured development workflows through the SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) approach.
5
6## Recent Changes
7- Integrated SPARC methodology principles into core rule files
8- Enhanced coding standards with SPARC-based modular development guidelines
9- Updated system patterns documentation to reflect SPARC workflow
10- Created visual workflow diagrams for SPARC methodology integration
11- Maintained the existing directory structure while enhancing content
12
13## Current Challenges
14- Ensuring emoji file names work correctly across different file systems
15- Making sure the rule management script is user-friendly and intuitive
16- Balancing comprehensiveness with simplicity in the rule files
17- Ensuring the memory bank system provides sufficient context without overwhelming users
18
19## Active Decisions
20- Using emoji prefixes for memory bank files to make them visually distinct
21- Organizing rules into logical categories (general, code-specific, testing)
22- Using a bash script for rule management rather than a more complex solution
23- Keeping core rule files separate from context-specific rules in the bank
24
25## Key Patterns & Preferences
26
27### Code Patterns
28- Markdown formatting for all rule files
29- Consistent section headings across similar rule files
30- Bullet points for individual rules within sections
31- Descriptive file names that reflect content
32
33### Architectural Decisions
34- Directory-based approach rather than a single file
35- Separation of core rules from context-specific rules
36- Memory bank system for persistent context
37- Command-line tool for rule management
38
39### Team Preferences
40- Preference for clarity and simplicity in rule descriptions
41- Focus on practical, actionable guidelines rather than abstract principles
42- Emphasis on flexibility and contextual activation
43
44## Learnings & Insights
45- The directory structure approach provides much more flexibility than a single file
46- Emoji prefixes make memory bank files more visually distinct and memorable
47- Separating rules by context allows for more focused guidance
48- The management script makes it easier to activate and deactivate rules as needed
49
50## Next Steps
511. Test the rule management script with different rule combinations
522. Expand the rule bank with additional context-specific rule sets
533. Develop integration with the Cline UI for visual rule management
544. Create rule templates for common project types
555. Implement rule versioning and change tracking
56
57## Open Questions
58- How can we best handle rule conflicts when multiple rule files are activated?
59- What's the optimal balance between comprehensive rules and keeping things simple?
60- How can we measure the effectiveness of the new approach compared to the old one?
61
62## Notes
63The current implementation focuses on the core functionality. Future enhancements will include more sophisticated rule management, integration with the Cline UI, and additional rule templates for common project types.
64
ruvnet/rUv-dev · .clinerules/📊_progress.md
@@ +1 @@
1# 📊 Progress
2
3## Project Status
4[Provide a high-level overview of the current project status]
5
6## Completed Features
7[List features that have been completed]
8
9- [Feature 1] - [Completion date] - [Brief description]
10- [Feature 2] - [Completion date] - [Brief description]
11- [Feature 3] - [Completion date] - [Brief description]
12
13## In-Progress Features
14[List features that are currently being worked on]
15
16- [Feature 4] - [Start date] - [Expected completion] - [Current status]
17- [Feature 5] - [Start date] - [Expected completion] - [Current status]
18
19## Pending Features
20[List features that are planned but not yet started]
21
22- [Feature 6] - [Priority] - [Dependencies]
23- [Feature 7] - [Priority] - [Dependencies]
24
25## Known Issues
26[List known issues or bugs]
27
28### Critical
29- [Issue 1] - [Impact] - [Workaround if available]
30- [Issue 2] - [Impact] - [Workaround if available]
31
32### High Priority
33- [Issue 3] - [Impact] - [Workaround if available]
34- [Issue 4] - [Impact] - [Workaround if available]
35
36### Medium Priority
37- [Issue 5] - [Impact] - [Workaround if available]
38- [Issue 6] - [Impact] - [Workaround if available]
39
40### Low Priority
41- [Issue 7] - [Impact] - [Workaround if available]
42- [Issue 8] - [Impact] - [Workaround if available]
43
44## Technical Debt
45[List areas of technical debt that need to be addressed]
46
47- [Debt 1] - [Impact] - [Plan to address]
48- [Debt 2] - [Impact] - [Plan to address]
49
50## Recent Milestones
51[List recently achieved milestones]
52
53- [Milestone 1] - [Date achieved] - [Significance]
54- [Milestone 2] - [Date achieved] - [Significance]
55
56## Upcoming Milestones
57[List upcoming milestones]
58
59- [Milestone 3] - [Target date] - [Current status]
60- [Milestone 4] - [Target date] - [Current status]
61
62## Performance Metrics
63[List key performance metrics and their current values]
64
65- [Metric 1]: [Current value] ([Target value]) - [Trend]
66- [Metric 2]: [Current value] ([Target value]) - [Trend]
67
68## Decision Log
69[Document important decisions that have shaped the project]
70
71- [Date] - [Decision] - [Rationale] - [Alternatives considered]
72- [Date] - [Decision] - [Rationale] - [Alternatives considered]
73
74## Lessons Learned
75[Document important lessons learned during the project]
76
77- [Lesson 1]
78- [Lesson 2]
79
80## Next Steps
81[Outline the immediate next steps for the project]
82
831. [Step 1]
842. [Step 2]
853. [Step 3]
86
@@ −1 +1 @@
1−# 🔄 Active Context
1+# 📊 Progress
22
3−## Current Focus
4−The current focus is on integrating the SPARC methodology into the `.clinerules/` folder structure. This includes updating core rule files, enhancing the memory bank system, and ensuring the system supports structured development workflows through the SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) approach.
3+## Project Status
4+[Provide a high-level overview of the current project status]
55
6−## Recent Changes
7−- Integrated SPARC methodology principles into core rule files
8−- Enhanced coding standards with SPARC-based modular development guidelines
9−- Updated system patterns documentation to reflect SPARC workflow
10−- Created visual workflow diagrams for SPARC methodology integration
11−- Maintained the existing directory structure while enhancing content
6+## Completed Features
7+[List features that have been completed]
128
13−## Current Challenges
14−- Ensuring emoji file names work correctly across different file systems
15−- Making sure the rule management script is user-friendly and intuitive
16−- Balancing comprehensiveness with simplicity in the rule files
17−- Ensuring the memory bank system provides sufficient context without overwhelming users
9+- [Feature 1] - [Completion date] - [Brief description]
10+- [Feature 2] - [Completion date] - [Brief description]
11+- [Feature 3] - [Completion date] - [Brief description]
1812
19−## Active Decisions
20−- Using emoji prefixes for memory bank files to make them visually distinct
21−- Organizing rules into logical categories (general, code-specific, testing)
22−- Using a bash script for rule management rather than a more complex solution
23−- Keeping core rule files separate from context-specific rules in the bank
13+## In-Progress Features
14+[List features that are currently being worked on]
2415
25−## Key Patterns & Preferences
16+- [Feature 4] - [Start date] - [Expected completion] - [Current status]
17+- [Feature 5] - [Start date] - [Expected completion] - [Current status]
2618
27−### Code Patterns
28−- Markdown formatting for all rule files
29−- Consistent section headings across similar rule files
30−- Bullet points for individual rules within sections
31−- Descriptive file names that reflect content
19+## Pending Features
20+[List features that are planned but not yet started]
3221
33−### Architectural Decisions
34−- Directory-based approach rather than a single file
35−- Separation of core rules from context-specific rules
36−- Memory bank system for persistent context
37−- Command-line tool for rule management
22+- [Feature 6] - [Priority] - [Dependencies]
23+- [Feature 7] - [Priority] - [Dependencies]
3824
39−### Team Preferences
40−- Preference for clarity and simplicity in rule descriptions
41−- Focus on practical, actionable guidelines rather than abstract principles
42−- Emphasis on flexibility and contextual activation
25+## Known Issues
26+[List known issues or bugs]
4327
44−## Learnings & Insights
45−- The directory structure approach provides much more flexibility than a single file
46−- Emoji prefixes make memory bank files more visually distinct and memorable
47−- Separating rules by context allows for more focused guidance
48−- The management script makes it easier to activate and deactivate rules as needed
28+### Critical
29+- [Issue 1] - [Impact] - [Workaround if available]
30+- [Issue 2] - [Impact] - [Workaround if available]
4931
50−## Next Steps
51−1. Test the rule management script with different rule combinations
52−2. Expand the rule bank with additional context-specific rule sets
53−3. Develop integration with the Cline UI for visual rule management
54−4. Create rule templates for common project types
55−5. Implement rule versioning and change tracking
32+### High Priority
33+- [Issue 3] - [Impact] - [Workaround if available]
34+- [Issue 4] - [Impact] - [Workaround if available]
5635
57−## Open Questions
58−- How can we best handle rule conflicts when multiple rule files are activated?
59−- What's the optimal balance between comprehensive rules and keeping things simple?
60−- How can we measure the effectiveness of the new approach compared to the old one?
36+### Medium Priority
37+- [Issue 5] - [Impact] - [Workaround if available]
38+- [Issue 6] - [Impact] - [Workaround if available]
6139
62−## Notes
63−The current implementation focuses on the core functionality. Future enhancements will include more sophisticated rule management, integration with the Cline UI, and additional rule templates for common project types.
40+### Low Priority
41+- [Issue 7] - [Impact] - [Workaround if available]
42+- [Issue 8] - [Impact] - [Workaround if available]
43+
44+## Technical Debt
45+[List areas of technical debt that need to be addressed]
46+
47+- [Debt 1] - [Impact] - [Plan to address]
48+- [Debt 2] - [Impact] - [Plan to address]
49+
50+## Recent Milestones
51+[List recently achieved milestones]
52+
53+- [Milestone 1] - [Date achieved] - [Significance]
54+- [Milestone 2] - [Date achieved] - [Significance]
55+
56+## Upcoming Milestones
57+[List upcoming milestones]
58+
59+- [Milestone 3] - [Target date] - [Current status]
60+- [Milestone 4] - [Target date] - [Current status]
61+
62+## Performance Metrics
63+[List key performance metrics and their current values]
64+
65+- [Metric 1]: [Current value] ([Target value]) - [Trend]
66+- [Metric 2]: [Current value] ([Target value]) - [Trend]
67+
68+## Decision Log
69+[Document important decisions that have shaped the project]
70+
71+- [Date] - [Decision] - [Rationale] - [Alternatives considered]
72+- [Date] - [Decision] - [Rationale] - [Alternatives considered]
73+
74+## Lessons Learned
75+[Document important lessons learned during the project]
76+
77+- [Lesson 1]
78+- [Lesson 2]
79+
80+## Next Steps
81+[Outline the immediate next steps for the project]
82+
83+1. [Step 1]
84+2. [Step 2]
85+3. [Step 3]
6486
