Cline rules

1# Cline AI Assistant Guidelines
2 
3## Core Principles
4 
5* Make changes incrementally and verify each step
6* Always analyze existing code patterns before making changes
7* Prioritize built-in tools over shell commands
8* Follow existing project patterns and conventions
9* Maintain comprehensive test coverage
10 
11## Tool Usage
12 
13### File Operations
14* Use `read_file` for examining file contents instead of shell commands like `cat`
15* Use `replace_in_file` for targeted, specific changes to existing files
16* Use `write_to_file` only for new files or complete file rewrites
17* Use `list_files` to explore directory structures
18* Use `search_files` with precise regex patterns to find code patterns
19* Use `list_code_definition_names` to understand code structure before modifications
20 
21### Command Execution
22* Use `execute_command` sparingly, preferring built-in file operation tools when possible
23* Always provide clear explanations for any executed commands
24* Set `requires_approval` to true for potentially impactful operations
25 
26## Development Workflow
27 
28### Planning Phase (PLAN MODE)
29* Begin complex tasks in PLAN mode to discuss approach
30* Analyze existing codebase patterns using search tools
31* Review related test files to understand testing patterns
32* Present clear implementation steps for approval
33* Ask clarifying questions early to avoid rework
34 
35### Implementation Phase (ACT MODE)
36* Make changes incrementally, one file at a time
37* Verify each change before proceeding
38* Follow patterns discovered during planning phase
39* Focus on maintaining test coverage
40* Use error messages and linter feedback to guide fixes
41 
42## Code Modifications
43 
44### General Guidelines
45* Follow .editorconfig rules strictly
46* Preserve file headers and license information
47* Maintain consistent XML documentation
48* Respect existing error handling patterns
49* Keep line endings consistent with existing files
50 
51### Quality Checks
52* Verify changes match existing code style
53* Ensure test coverage for new code
54* Validate changes against project conventions
55* Check for proper error handling
56* Maintain nullable reference type annotations
57 
58## MCP Server Integration
59 
60* Use appropriate MCP tools when available for specialized tasks
61* Access MCP resources efficiently using proper URIs
62* Handle MCP operation results appropriately
63* Follow server-specific authentication and usage patterns
64 
65## Error Handling
66 
67* Provide clear error messages and suggestions
68* Handle tool operation failures gracefully
69* Suggest alternative approaches when primary approach fails
70* Roll back changes if necessary to maintain stability
71