| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 1 | 7 | 0% |
| Commands | 0 | 0 | 3 | 0% |
| Section tags | 0 | 0 | 6 | 0% |
What each file covers
Sections
0 shared · 1 only in A · 7 only in B- − Teaching and Learning Approach (Severity: Warning)
- + Development Rules for Fasten
- + Environment
- + Build
- + Testing
- + Debugging
- + CI/CD
- + Workflow
Commands
0 shared · 0 only in A · 3 only in B- + zig build
- + zig build clean
- + zig build test
Section tags
0 shared · 0 only in A · 6 only in B- + setup
- + build
- + test
- + deployment
- + do-not
- + agent-behaviour
Line diff
v1truv1us/fasten · .cursor/rules/teaching.mdc
@@ −3 @@
3globs:
4alwaysApply: true
5---
6## Teaching and Learning Approach (Severity: Warning)
7- Act as a guide and teacher, not a code writer
8- Explain concepts clearly with examples and reasoning
9- Break down complex topics into digestible steps
10- Show patterns and syntax to follow, but let user implement
11- Focus on "why" and "how" rather than just "what"
12- Ask guiding questions to help user think through design decisions
13- Help debug and troubleshoot when user gets stuck
14- Avoid writing complete implementations or large code blocks
15- Encourage incremental learning and experimentation
16- Provide conceptual examples, not production code to copy-paste
v1truv1us/fasten · .cursor/rules/development.mdc
@@ +3 @@
3globs:
4alwaysApply: true
5---
6# Development Rules for Fasten
7
8## Environment
9- Use Zig 0.11.0+; set up with Homebrew, direct download, or package manager.
10- Recommended: VS Code with ziglang extension, or Vim/Neovim with zig.vim.
11
12## Build
13- Use `zig build` for standard, debug, release, and safe builds.
14- Use build options for features and target platforms.
15- Clean with `zig build clean`.
16
17## Testing
18- Run all tests with `zig build test`.
19- Organize tests: unit, integration, performance, regression.
20- Use memory leak detection and verbose output as needed.
21
22## Debugging
23- Use debug builds and Zig's logging.
24- Use Valgrind, AddressSanitizer, or platform profilers for memory/perf issues.
25
26## CI/CD
27- Use GitHub Actions for build, test, benchmark, security, docs.
28- Simulate CI locally with provided scripts.
29
30## Workflow
31- Feature: branch, test, implement, benchmark, document, PR.
32- Bugfix: reproduce, fix, verify, regression test, PR.
33- Review: self-review, CI, peer review, address feedback, merge.
34
@@ −3 +3 @@
33 globs:
44 alwaysApply: true
55 ---
6−## Teaching and Learning Approach (Severity: Warning)
7−- Act as a guide and teacher, not a code writer
8−- Explain concepts clearly with examples and reasoning
9−- Break down complex topics into digestible steps
10−- Show patterns and syntax to follow, but let user implement
11−- Focus on "why" and "how" rather than just "what"
12−- Ask guiding questions to help user think through design decisions
13−- Help debug and troubleshoot when user gets stuck
14−- Avoid writing complete implementations or large code blocks
15−- Encourage incremental learning and experimentation
16−- Provide conceptual examples, not production code to copy-paste
6+# Development Rules for Fasten
7+
8+## Environment
9+- Use Zig 0.11.0+; set up with Homebrew, direct download, or package manager.
10+- Recommended: VS Code with ziglang extension, or Vim/Neovim with zig.vim.
11+
12+## Build
13+- Use `zig build` for standard, debug, release, and safe builds.
14+- Use build options for features and target platforms.
15+- Clean with `zig build clean`.
16+
17+## Testing
18+- Run all tests with `zig build test`.
19+- Organize tests: unit, integration, performance, regression.
20+- Use memory leak detection and verbose output as needed.
21+
22+## Debugging
23+- Use debug builds and Zig's logging.
24+- Use Valgrind, AddressSanitizer, or platform profilers for memory/perf issues.
25+
26+## CI/CD
27+- Use GitHub Actions for build, test, benchmark, security, docs.
28+- Simulate CI locally with provided scripts.
29+
30+## Workflow
31+- Feature: branch, test, implement, benchmark, document, PR.
32+- Bugfix: reproduce, fix, verify, regression test, PR.
33+- Review: self-review, CI, peer review, address feedback, merge.
34+
