Cline rules

1### Code Style
2 
3- Follow standard Go code style and conventions (gofmt).
4- Use meaningful variable and function names.
5- Add comments for exported functions and types.
6- Keep functions small and focused on a single responsibility.
7 
8### Error Handling
9 
10- Use the `fmt.Errorf("failed to X: %w", err)` pattern for error wrapping.
11- Always check errors and provide context.
12- Avoid panics in production code.
13 
14### Dependencies
15 
16- Prefer standard library solutions when possible, suggest libraries when appropriate.
17- Don't write solutions from scratch if a well-known and widely used library exists
18- Minimize external dependencies, unless an external dependency makes the code more cleaner or efficient.
19- Pin dependency versions in go.mod.
20- Run `go mod tidy` after adding new libraries
21 
22### Testing
23 
24- Write unit tests for core functionality.
25- Use table-driven tests where appropriate.
26- Mock external dependencies for testing.
27 
28### Development
29 
30- Run unit tests after a task is complete and confirm that they pass
31 
32### Libraries
33 
34- For CLI tools use spf13/cobra to generate commands and subcommands
35- Use spf13/viper to manage configuration
36- If Sqlite is used, use modernc.org/sqlite as the library, because it works even when cross-compiled
37- Use slog for logging and fmt.Printf for interactive output
38