Cline rules

1# Development Workflow
2 
3## Debugging and Testing
4 
5**When stuck or testing functionality in isolation:**
6- Create test scripts in `scripts/` folder
7- Use these to assess how things work by inspecting logs
8- Test individual components before integrating
9- Keep scripts for future reference
10 
11## Major Changes and Refactoring
12 
13**IMPORTANT: Before any rearchitecting or major structural changes:**
141. Consult with the user first
152. Present multiple options with pros/cons
163. Get explicit approval before proceeding
174. Major changes include: moving files, changing architecture, large refactors
18 
19## Adding New Features
20 
211. Identify which layer the feature belongs to (actions/config/utils/core)
222. Create or modify the appropriate module
233. Update type hints and docstrings
244. Update CLI if needed
25 
26## Modifying Existing Code
27 
281. Check which module owns the functionality
292. Make changes following single responsibility principle
303. Update dependent modules if interfaces change
314. Verify type hints still match
32 
33## Package Updates
34 
351. Always check PyPI for latest stable versions
362. Use `uv add package` for automatic latest version
373. Test after updates to ensure compatibility
384. Update version in pyproject.toml if making a release
39