| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 5 | 2 | 0% |
| Commands | 0 | 0 | 0 | — |
| Section tags | 2 | 2 | 0 | 50% |
What each file covers
Sections
0 shared · 5 only in A · 2 only in B- − Go Development Rules
- − Directory Structure
- − Code Changes
- − Library use
- − Testing
- + Go Testing Rules
- + Core Testing Requirements
Commands
neither file has anySection tags
2 shared · 2 only in A · 0 only in B- − code-style
- − architecture
- test
- do-not
Line diff
superfly/flymcp · .cursor/rules/go.mdc
@@ −1 @@
1---
2description:
3globs: **/*.go
4alwaysApply: false
5---
6# Go Development Rules
7
8## Directory Structure
9- Use simple Go project layout
10 - ./cmd/ for individual subcommands
11 -
12- NEVER create a pkg or internal directory
13
14## Code Changes
15- Minimize file changes by keeping related functionality together
16- Prefer modifying existing files over creating new ones
17- Use interfaces to reduce coupling between components
18
19## Library use
20- ALWAYS use the go std library when writing new code
21- NEVER use a third party package without explicit user request
22
23## Testing
24- Tests MUST fail if the code they're testing isn't implemented
25- NEVER modify tests to make them pass without implementing the required functionality
26- Write tests before implementing features (TDD approach)
superfly/flymcp · .cursor/rules/go-test.mdc
@@ +1 @@
1---
2description:
3globs: "**/*_test.go"
4alwaysApply: false
5---
6# Go Testing Rules
7
8## Core Testing Requirements
9- Tests MUST fail if the code they're testing isn't implemented
10- NEVER modify tests to make them pass without implementing the required functionality
11- Write tests before implementing features (TDD approach)
@@ −1 +1 @@
11 ---
22 description:
3−globs: **/*.go
3+globs: "**/*_test.go"
44 alwaysApply: false
55 ---
6−# Go Development Rules
6+# Go Testing Rules
77
8−## Directory Structure
9−- Use simple Go project layout
10− - ./cmd/ for individual subcommands
11− -
12−- NEVER create a pkg or internal directory
13−
14−## Code Changes
15−- Minimize file changes by keeping related functionality together
16−- Prefer modifying existing files over creating new ones
17−- Use interfaces to reduce coupling between components
18−
19−## Library use
20−- ALWAYS use the go std library when writing new code
21−- NEVER use a third party package without explicit user request
22−
23−## Testing
8+## Core Testing Requirements
249 - Tests MUST fail if the code they're testing isn't implemented
2510 - NEVER modify tests to make them pass without implementing the required functionality
2611 - Write tests before implementing features (TDD approach)
