Cline rules

1# 🏃 Current Sprint Guidelines
2 
3## SPARC Implementation Focus
4 
5- Apply SPARC methodology to all new development tasks
6- Break down complex features into SPARC workflow phases
7- Use subtasks for each SPARC phase when appropriate
8- Ensure all code follows SPARC modular architecture principles
9 
10## Focus Areas
11 
12- Prioritize bug fixes for the user authentication system
13- Implement new features for the reporting dashboard
14- Improve test coverage for core modules
15- Refactor the data processing pipeline for better performance
16- Ensure all files remain under 500 lines with clear modular boundaries
17 
18## Code Review Criteria
19 
20- All new code must have corresponding tests
21- Performance impact must be documented for any changes to critical paths
22- Security implications must be reviewed for authentication-related changes
23- UI changes must be tested on all supported browsers
24- Verify no environment variables or secrets are hardcoded
25- Confirm proper error handling in all code paths
26- Check that functions follow single responsibility principle
27 
28## Technical Debt
29 
30- Identify and document technical debt as you encounter it
31- Allocate time for addressing critical technical debt items
32- Refactor code that doesn't meet our current standards when modifying it
33- Split files exceeding 500 lines into logical modules
34 
35## Documentation
36 
37- Update API documentation for any changed endpoints
38- Document any new configuration options
39- Update the developer setup guide with new dependencies
40- Auto-document each feature with clear examples
41- Include SPARC phase documentation for complex features
42