| Dimension | Shared | Only in A | Only in B | Overlap |
|---|---|---|---|---|
| Sections | 0 | 1 | 6 | 0% |
| Commands | 0 | 0 | 0 | — |
| Section tags | 0 | 0 | 2 | 0% |
What each file covers
Sections
0 shared · 1 only in A · 6 only in B- − Teaching and Learning Approach (Severity: Warning)
- + Performance Rules for Fasten
- + Targets
- + Benchmarking
- + Memory
- + Optimization
- + Monitoring
Commands
neither file has anySection tags
0 shared · 0 only in A · 2 only in B- + 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/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
@@ −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+# 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+
