| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 1 | 3 | 0% |
| Commands | 0 | 0 | 0 | — |
| Section tags | 0 | 0 | 1 | 0% |
What each file covers
Sections
0 shared · 1 only in A · 3 only in B- − Introduction
- + Coding Guidelines
- + General Principles
- + Testing
Commands
neither file has anySection tags
0 shared · 0 only in A · 1 only in B- + test
Line diff
sakatai11/todoApp-next · .clinerules/introduction.md
@@ −1 @@
1# Introduction
2
3This document outlines the development guidelines for Cline.
4All development must follow these standards.
5
6| Mode | Role | When to Switch Automatically |
7| --------- | ----------------------- | ------------------------------------------------------- |
8| PM | Requirements & Planning | When discussing new features or clarifying requirements |
9| Architect | Design & Tech Decisions | When design or technical judgment is required |
10| Code | Implementation & Tests | When writing or fixing code |
11| PMO | QA & Final Checks | When work is completed or requires quality checks |
12
13You must automatically switch to the most appropriate mode based on the task and context, and execute with maximum efficiency toward achieving the goal.
14
sakatai11/todoApp-next · .clinerules/coding-guidelines.md
@@ +1 @@
1# Coding Guidelines
2
3## General Principles
4
5- Keep code simple and readable
6- Use meaningful naming (variables, functions, classes)
7- One responsibility per function
8- Proper error handling
9- Comment only when necessary
10
11## Testing
12
13- Include unit tests for all major features
14- Consider edge cases
15- Ensure tests are executable
16
@@ −1 +1 @@
1−# Introduction
1+# Coding Guidelines
22
3−This document outlines the development guidelines for Cline.
4−All development must follow these standards.
3+## General Principles
54
6−| Mode | Role | When to Switch Automatically |
7−| --------- | ----------------------- | ------------------------------------------------------- |
8−| PM | Requirements & Planning | When discussing new features or clarifying requirements |
9−| Architect | Design & Tech Decisions | When design or technical judgment is required |
10−| Code | Implementation & Tests | When writing or fixing code |
11−| PMO | QA & Final Checks | When work is completed or requires quality checks |
5+- Keep code simple and readable
6+- Use meaningful naming (variables, functions, classes)
7+- One responsibility per function
8+- Proper error handling
9+- Comment only when necessary
1210
13−You must automatically switch to the most appropriate mode based on the task and context, and execute with maximum efficiency toward achieving the goal.
11+## Testing
12+
13+- Include unit tests for all major features
14+- Consider edge cases
15+- Ensure tests are executable
1416
