| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 4 | 1 | 0% |
| Commands | 0 | 0 | 0 | — |
| Section tags | 0 | 3 | 0 | 0% |
What each file covers
Sections
0 shared · 4 only in A · 1 only in B- − Tech Stack
- − Frontend
- − Backend
- − Development Tools
- + Introduction
Commands
neither file has anySection tags
0 shared · 3 only in A · 0 only in B- − test
- − lint-format
- − testing-strategy
Line diff
sakatai11/todoApp-next · .clinerules/tech-stack.md
@@ −1 @@
1# Tech Stack
2
3Unless otherwise specified, follow the defined stack and common best practices.
4
5## Frontend
6
7Use the following only when necessary:
8
9- Language: TypeScript
10- Framework: Next.js (App Router)
11- UI: MUI, Tailwind CSS
12- State Management: React Hooks
13- Auth: NextAuth.js, Firebase Authentication (via Firebase Admin SDK)
14- Lint/Format: ESLint, Prettier
15- Drag & Drop: dnd-kit
16- Data Fetching: SWR
17- Validation: Zod
18
19## Backend
20
21- Language: Node.js (TypeScript)
22- API: REST
23- Database: Firestore (via Firebase Admin SDK)
24
25## Development Tools
26
27- Hosting: Vercel
28- Testing: Vitest
29- Linting: ESLint
30- Formatting: Prettier
31- Mocking: MSW (Mock Service Worker)
32
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
@@ −1 +1 @@
1−# Tech Stack
1+# Introduction
22
3−Unless otherwise specified, follow the defined stack and common best practices.
3+This document outlines the development guidelines for Cline.
4+All development must follow these standards.
45
5−## Frontend
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 |
612
7−Use the following only when necessary:
8−
9−- Language: TypeScript
10−- Framework: Next.js (App Router)
11−- UI: MUI, Tailwind CSS
12−- State Management: React Hooks
13−- Auth: NextAuth.js, Firebase Authentication (via Firebase Admin SDK)
14−- Lint/Format: ESLint, Prettier
15−- Drag & Drop: dnd-kit
16−- Data Fetching: SWR
17−- Validation: Zod
18−
19−## Backend
20−
21−- Language: Node.js (TypeScript)
22−- API: REST
23−- Database: Firestore (via Firebase Admin SDK)
24−
25−## Development Tools
26−
27−- Hosting: Vercel
28−- Testing: Vitest
29−- Linting: ESLint
30−- Formatting: Prettier
31−- Mocking: MSW (Mock Service Worker)
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.
3214
