| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 2 | 7 | 0% |
| Commands | 0 | 0 | 0 | — |
| Section tags | 0 | 0 | 4 | 0% |
What each file covers
Sections
0 shared · 2 only in A · 7 only in B- − 📝 TASKS.md Update Rule (Severity: Warning)
- − Process:
- + 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/task_tracking.mdc
@@ −3 @@
3globs:
4alwaysApply: true
5---
6# 📝 TASKS.md Update Rule (Severity: Warning)
7
8- ALWAYS update TASKS.md when completing any task or subtask
9- Mark items as ✅ Completed immediately after verification
10- Add verification notes for important milestones
11- Include test results and command examples for CLI/build features
12- Update the "Current Status" section to reflect the next target
13- Use specific markers: [✅] for complete, [🔄] for in progress, [🧪] for testing required
14- Include any bonus features or work that exceeded requirements
15- Update milestone progress when reaching key checkpoints
16
17## Process:
18- Complete a task/subtask
19- Test/verify it works
20- Immediately update TASKS.md with ✅ status
21- Add verification notes and test results
22- Update "Current Status" section
23- Commit the TASKS.md update along with the code changes
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−# 📝 TASKS.md Update Rule (Severity: Warning)
6+# Contributing Rules for Fasten
77
8−- ALWAYS update TASKS.md when completing any task or subtask
9−- Mark items as ✅ Completed immediately after verification
10−- Add verification notes for important milestones
11−- Include test results and command examples for CLI/build features
12−- Update the "Current Status" section to reflect the next target
13−- Use specific markers: [✅] for complete, [🔄] for in progress, [🧪] for testing required
14−- Include any bonus features or work that exceeded requirements
15−- Update milestone progress when reaching key checkpoints
8+## Code of Conduct
9+- Be respectful, constructive, and professional in all interactions.
1610
17−## Process:
18−- Complete a task/subtask
19−- Test/verify it works
20−- Immediately update TASKS.md with ✅ status
21−- Add verification notes and test results
22−- Update "Current Status" section
23−- Commit the TASKS.md update along with the code changes
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+
