Cline rules

1# 💻 Core Coding Standards
2 
3## SPARC Coding Principles
4 
5- **Modularity**: Every file ≤ 500 lines, every function ≤ 50 lines with clear single responsibility
6- **Security**: No hard-coded secrets, credentials, or environment variables
7- **Validation**: All user inputs must be validated and sanitized
8- **Error Handling**: Proper error handling in all code paths
9- **Documentation**: Self-documenting code with strategic comments explaining "why" not "what"
10- **Testing**: Design for unit testing with dependency injection and mockable interfaces
11 
12## General Guidelines
13 
14- Follow established coding conventions for the language/framework being used
15- Use consistent indentation (2 spaces for JavaScript/TypeScript, 4 spaces for Python)
16- Keep functions small and focused on a single responsibility
17- Use meaningful variable and function names
18- Add comments for complex logic, but prefer self-documenting code
19- Avoid deep nesting of conditionals and loops
20- Handle errors appropriately
21- Write unit tests for critical functionality
22 
23## Code Organization
24 
25- Group related functionality together
26- Separate concerns appropriately
27- Use modules/components to encapsulate functionality
28- Follow the project's established architecture patterns
29- Apply SOLID principles (Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, Dependency Inversion)
30- Eliminate code duplication through abstraction (DRY principle)
31 
32## Performance Considerations
33 
34- Be mindful of performance implications, especially in loops or recursive functions
35- Avoid unnecessary computations or memory usage
36- Consider caching results of expensive operations when appropriate
37- Use appropriate data structures for the task at hand
38- Optimize critical paths while maintaining readability
39