Cline rules

1# Search Reliability
2 
3When working with the codebase, the current workspace files are the source of truth.
4 
5## Search
6- Never assume a function, variable, class, selector, component, or code pattern exists.
7- Prefer exact literal searches over regex.
8- Keep search patterns short and distinctive.
9- Never search for an entire code block.
10- Do not construct a search pattern from previously remembered code.
11 
12## If a Search Returns 0 Results
13- Do not immediately retry with another guessed pattern.
14- Read the relevant file and inspect its actual contents.
15- Find the target by reading the current implementation.
16- If another search is necessary, use exact text copied from the current file.
17- Do not repeatedly retry failed searches.
18 
19## Before Editing
20- Read the current file before modifying it.
21- Base edits only on code that actually exists in the workspace.
22- Never recreate an older version of the code from memory.
23- Make the smallest change necessary.
24- Do not modify unrelated working code.
25 
26## Verification
27- After making an edit, inspect the changed section.
28- Confirm the requested change actually exists before continuing.
29 
30## Failure Handling
31If two searches fail to locate the target:
321. Stop searching.
332. Inspect the relevant file directly.
343. Explain what was found.
354. Only then continue with the task.