| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 1 | 7 | 0% |
| Commands | 0 | 0 | 0 | — |
| Section tags | 0 | 0 | 4 | 0% |
What each file covers
Sections
0 shared · 1 only in A · 7 only in B- − Teaching and Learning Approach (Severity: Warning)
- + Contributing Rules for Fasten
- + Code of Conduct
- + Code Standards
- + Testing
- + Performance
- + Submission Process
- + Architecture
Commands
neither file has anySection tags
0 shared · 0 only in A · 4 only in B- + test
- + git-pr
- + performance
- + do-not
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/contributing.mdc
@@ +3 @@
3globs:
4alwaysApply: true
5---
6# Contributing Rules for Fasten
7
8## Code of Conduct
9- Be respectful, constructive, and professional in all interactions.
10
11## Code Standards
12- Use Zig naming conventions: camelCase for functions, snake_case for variables, PascalCase for types.
13- Keep functions under 50 lines; cyclomatic complexity ≤ 10.
14- Document all public functions and complex algorithms.
15- Use explicit allocators and ensure all resources are freed.
16- Use Zig's error handling consistently.
17
18## Testing
19- Write unit, integration, performance, and error tests.
20- Use descriptive test names: `test "should [behavior] when [condition]"`.
21- Benchmark critical paths and set performance targets.
22
23## Performance
24- Bundle 100-200 JS files (~100KB) in <1s; 500+ files (~500KB) in <5s.
25- Peak memory ≤ 2x input size; zero tolerance for memory leaks.
26
27## Submission Process
28- Run all tests and benchmarks before submitting.
29- Use conventional commit messages: `type(scope): description`.
30- Complete PR checklist and template.
31- PRs require at least one maintainer review and passing CI.
32
33## Architecture
34- Each module has a single responsibility.
35- Explicit, minimal dependencies.
36- Consistent error propagation and documentation.
37- Optimize for speed, memory, and testability.
38
@@ −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+# Contributing Rules for Fasten
7+
8+## Code of Conduct
9+- Be respectful, constructive, and professional in all interactions.
10+
11+## Code Standards
12+- Use Zig naming conventions: camelCase for functions, snake_case for variables, PascalCase for types.
13+- Keep functions under 50 lines; cyclomatic complexity ≤ 10.
14+- Document all public functions and complex algorithms.
15+- Use explicit allocators and ensure all resources are freed.
16+- Use Zig's error handling consistently.
17+
18+## Testing
19+- Write unit, integration, performance, and error tests.
20+- Use descriptive test names: `test "should [behavior] when [condition]"`.
21+- Benchmark critical paths and set performance targets.
22+
23+## Performance
24+- Bundle 100-200 JS files (~100KB) in <1s; 500+ files (~500KB) in <5s.
25+- Peak memory ≤ 2x input size; zero tolerance for memory leaks.
26+
27+## Submission Process
28+- Run all tests and benchmarks before submitting.
29+- Use conventional commit messages: `type(scope): description`.
30+- Complete PR checklist and template.
31+- PRs require at least one maintainer review and passing CI.
32+
33+## Architecture
34+- Each module has a single responsibility.
35+- Explicit, minimal dependencies.
36+- Consistent error propagation and documentation.
37+- Optimize for speed, memory, and testability.
38+
