| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 1 | 5 | 0% |
| Commands | 0 | 0 | 0 | — |
| Section tags | 0 | 0 | 7 | 0% |
What each file covers
Sections
0 shared · 1 only in A · 5 only in B- − Introduction
- + Development Guidelines
- + Basic Rules
- + Security
- + Confidential Files
- + Workflow
Commands
neither file has anySection tags
0 shared · 0 only in A · 7 only in B- + test
- + lint-format
- + testing-strategy
- + security
- + ui
- + do-not
- + agent-behaviour
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/development-guidelines.md
@@ +1 @@
1# Development Guidelines
2
3## Basic Rules
4
5- Follow Instructions
6 - Execute tasks as per defined requirements
7 - Report progress or issues proactively
8
9- Autonomous Problem Solving
10 - Analyze and propose solutions when errors or problems occur
11 - Clearly state recommended options if multiple approaches exist
12 - Report issues that might be outside of the code
13
14- Respect Existing Code
15 - Follow existing code style and patterns
16 - Explain if major changes are necessary
17
18- Handling Repeated Failures
19 - If a test fails twice in a row, summarize the situation with reproduction steps, logs, and error messages, and report it
20 - Do not repeat the same action — always propose a solution
21
22## Security
23
24### Confidential Files
25
26Do not read or modify the following under any circumstances
27
28- .env file
29- Any file containing API keys, tokens, or credentials
30
31If changes to confidential files are necessary, contact the project owner.
32
33Also follow these security practices:
34
35- Never commit confidential files
36- Use environment variables for secrets
37- Avoid logging sensitive data (auth/user info)
38
39## Workflow
40
41Follow these four steps during development:
42
431. Requirements (PM Mode)
44 - Clarify and refine requirements
45 - Ask questions or make suggestions if needed
46
472. Design (Architect Mode)
48 - Choose appropriate architecture or design patterns
49 - Design components, data flows, and use case diagrams
50
513. Implementation (Code Mode)
52 - Write code based on the design
53 - Create unit tests
54 - Must be executable via Vitest
55 - 100% test coverage required for:
56 - statements
57 - branches
58 - functions
59 - lines
60 - Each function/component should be tested with mocked external dependencies
61
624. Quality Check (PMO Mode)
63 - Code Review
64 - Lint/format checks (ESLint / Prettier)
65 - Validate user input properly
66 - Consider performance and security
67 - Requirement Verification
68
69AI should make autonomous decisions to progress through these steps and deliver complete results in a single request whenever possible.
70
@@ −1 +1 @@
1−# Introduction
1+# Development Guidelines
22
3−This document outlines the development guidelines for Cline.
4−All development must follow these standards.
3+## Basic Rules
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+- Follow Instructions
6+ - Execute tasks as per defined requirements
7+ - Report progress or issues proactively
128
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.
9+- Autonomous Problem Solving
10+ - Analyze and propose solutions when errors or problems occur
11+ - Clearly state recommended options if multiple approaches exist
12+ - Report issues that might be outside of the code
13+
14+- Respect Existing Code
15+ - Follow existing code style and patterns
16+ - Explain if major changes are necessary
17+
18+- Handling Repeated Failures
19+ - If a test fails twice in a row, summarize the situation with reproduction steps, logs, and error messages, and report it
20+ - Do not repeat the same action — always propose a solution
21+
22+## Security
23+
24+### Confidential Files
25+
26+Do not read or modify the following under any circumstances
27+
28+- .env file
29+- Any file containing API keys, tokens, or credentials
30+
31+If changes to confidential files are necessary, contact the project owner.
32+
33+Also follow these security practices:
34+
35+- Never commit confidential files
36+- Use environment variables for secrets
37+- Avoid logging sensitive data (auth/user info)
38+
39+## Workflow
40+
41+Follow these four steps during development:
42+
43+1. Requirements (PM Mode)
44+ - Clarify and refine requirements
45+ - Ask questions or make suggestions if needed
46+
47+2. Design (Architect Mode)
48+ - Choose appropriate architecture or design patterns
49+ - Design components, data flows, and use case diagrams
50+
51+3. Implementation (Code Mode)
52+ - Write code based on the design
53+ - Create unit tests
54+ - Must be executable via Vitest
55+ - 100% test coverage required for:
56+ - statements
57+ - branches
58+ - functions
59+ - lines
60+ - Each function/component should be tested with mocked external dependencies
61+
62+4. Quality Check (PMO Mode)
63+ - Code Review
64+ - Lint/format checks (ESLint / Prettier)
65+ - Validate user input properly
66+ - Consider performance and security
67+ - Requirement Verification
68+
69+AI should make autonomous decisions to progress through these steps and deliver complete results in a single request whenever possible.
1470
