Cursor rule

1---
2description: 
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