Cline rules

1# Development Guidelines
2 
3## Code Style
4- Follow PEP 8 standards (automatically checked by Ruff)
5- Use meaningful variable and function names
6- Keep functions small and focused
7- Avoid deep nesting
8 
9## Type Hints
10- ALL functions must have type hints
11- Use proper type annotations for parameters and return values
12- Import types from typing module when needed
13- Pyright runs in strict mode - fix all type errors
14 
15## Testing
16- Write unit tests for all new features
17- Test files go in the tests/ directory
18- Mirror the source structure in tests
19- Run tests with `uv run pytest`
20- Aim for high test coverage
21 
22## Documentation
23- Use docstrings for all functions and classes
24- Follow Google or NumPy docstring style
25- Keep docstrings concise but informative
26- Update documentation when changing functionality
27 
28## Code Quality
29- No commented-out code in commits
30- Remove debug print statements
31- Handle exceptions appropriately
32- Use logging instead of print statements