Cursor rule

1---
2description: 
3globs: 
4alwaysApply: true
5---
6# Code Style Rules for Fasten
7 
8## Zig Code Style
9- Organize files: std imports, local imports, constants, types, public/private functions, tests.
10- Naming: camelCase for functions, snake_case for variables/fields, PascalCase for types/enums, SCREAMING_SNAKE_CASE for constants.
11- Indent with 4 spaces, no tabs. Max line length: 100 chars.
12- One space around binary ops, after commas/semicolons; no trailing whitespace.
13- Braces on same line; always use braces for control structures.
14 
15## Documentation
16- Document all public functions with triple-slash comments (///), including params, returns, errors.
17- Use inline comments for complex/non-obvious code.
18 
19## Error Handling
20- Use specific error enums per module; descriptive error names.
21- Use `try` for propagation; `catch` only for meaningful handling.
22- Include file, line, column in error messages.
23 
24## Memory Management
25- Pass allocators explicitly; use ArenaAllocator for temp data.
26- Use `defer` for cleanup; always free resources.
27 
28## Testing
29- Group related tests; descriptive names; test both success and error cases.
30- Use realistic and edge-case data.
31 
32## Performance
33- Minimize allocations in hot paths; reuse buffers; avoid unnecessary copying.
34- Tokenization: <1ms/KB; Parsing: <5ms/KB; Memory: <2x input size.
35