Cline rules

1# Development Workflow
2 
3Rules for development process and workflow best practices.
4 
5## Workflow Best Practices
6 
7- **Long-Running Commands**: Use `nohup` for commands that cannot be executed quickly or need to run in the background, ensuring they continue after terminal disconnection.
8 
9- **Incremental Development**: Break large coding tasks into smaller components. Complete and test each component individually before proceeding to the next, ensuring each part is production-ready before moving forward.
10 
11- **File Organization**: Maintain a clean and organized file hierarchy. Place files in appropriate directories according to their purpose and function within the project.
12 
13- **Resource Management**: Consider system resource constraints when running multiple processes. Run resource-intensive operations sequentially rather than in parallel if system memory or CPU limitations are a concern.
14 
15- **Git Integration**: Follow git best practices from `.clinerules/version_control.md`. Commit frequently with clear messages, maintain clean working directory using `git_status_clear.md` workflow, and ensure logical commit grouping.
16 
17- **Interactive Program Testing**: When testing programs that require user input, create input files and redirect stdin using `echo "input" | ./program` or `./program < input.txt`. For multi-step interactions, use `expect` scripts or create comprehensive test files in `tests/input/` directory.
18