| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 1 | 1 | 0% |
| Commands | 0 | 0 | 0 | — |
| Section tags | 0 | 0 | 1 | 0% |
What each file covers
Sections
0 shared · 1 only in A · 1 only in B- − Introduction
- + Best Practices
Commands
neither file has anySection tags
0 shared · 0 only in A · 1 only in B- + code-style
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/best-practices.md
@@ +1 @@
1# Best Practices
2
3- Build reusable and general-purpose components
4- Implement basic performance optimization
5- Follow basic accessibility standards
6- Use useMemo/useCallback to avoid unnecessary re-renders
7- Optimize for Core Web Vitals
8
@@ −1 +1 @@
1−# Introduction
1+# Best Practices
22
3−This document outlines the development guidelines for Cline.
4−All 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−
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.
3+- Build reusable and general-purpose components
4+- Implement basic performance optimization
5+- Follow basic accessibility standards
6+- Use useMemo/useCallback to avoid unnecessary re-renders
7+- Optimize for Core Web Vitals
148
