| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 6 | 2 | 0% |
| Commands | 0 | 0 | 0 | — |
| Section tags | 0 | 2 | 0 | 0% |
What each file covers
Sections
0 shared · 6 only in A · 2 only in B- − Performance Rules for Fasten
- − Targets
- − Benchmarking
- − Memory
- − Optimization
- − Monitoring
- + 📝 TASKS.md Update Rule (Severity: Warning)
- + Process:
Commands
neither file has anySection tags
0 shared · 2 only in A · 0 only in B- − performance
- − do-not
Line diff
v1truv1us/fasten · .cursor/rules/performance.mdc
@@ −3 @@
3globs:
4alwaysApply: true
5---
6# Performance Rules for Fasten
7
8## Targets
9- Small: <100ms, <10MB; Medium: <500ms, <50MB; Large: <2s, <200MB; XL: <10s, <500MB.
10- Lexer: >1MB/s; Parser: >500KB/s; Optimizer: >2MB/s; Codegen: >5MB/s.
11- Cold start <50ms; base memory <5MB.
12
13## Benchmarking
14- Use provided benchmark framework; warmup, multiple iterations, throughput checks.
15- Assert performance targets in tests; fail on regression >10%.
16
17## Memory
18- Use ArenaAllocator for temp data; Pool for frequent allocations.
19- Profile memory; zero tolerance for leaks; peak usage <2x input size.
20
21## Optimization
22- Minimize allocations in hot paths; use stack allocation when possible.
23- Profile before optimizing; document all optimizations.
24- Use efficient data structures (interning, compact AST).
25
26## Monitoring
27- Collect and log metrics (time, memory, compression ratio).
28- Alert on slow bundling, high memory, poor compression.
29- Run performance and memory tests in CI.
30
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
@@ −3 +3 @@
33 globs:
44 alwaysApply: true
55 ---
6−# Performance Rules for Fasten
6+# 📝 TASKS.md Update Rule (Severity: Warning)
77
8−## Targets
9−- Small: <100ms, <10MB; Medium: <500ms, <50MB; Large: <2s, <200MB; XL: <10s, <500MB.
10−- Lexer: >1MB/s; Parser: >500KB/s; Optimizer: >2MB/s; Codegen: >5MB/s.
11−- Cold start <50ms; base memory <5MB.
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
1216
13−## Benchmarking
14−- Use provided benchmark framework; warmup, multiple iterations, throughput checks.
15−- Assert performance targets in tests; fail on regression >10%.
16−
17−## Memory
18−- Use ArenaAllocator for temp data; Pool for frequent allocations.
19−- Profile memory; zero tolerance for leaks; peak usage <2x input size.
20−
21−## Optimization
22−- Minimize allocations in hot paths; use stack allocation when possible.
23−- Profile before optimizing; document all optimizations.
24−- Use efficient data structures (interning, compact AST).
25−
26−## Monitoring
27−- Collect and log metrics (time, memory, compression ratio).
28−- Alert on slow bundling, high memory, poor compression.
29−- Run performance and memory tests in CI.
30−
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
