Cline rules

1## ACT MODEL — EXECUTION ONLY
2 
3When a Plan exists, do NOT independently reason about the task.
4 
5Do not:
6- reinterpret the requirements
7- reconsider the architecture
8- speculate about missing projects
9- infer additional requirements
10- debate possible implementations
11- search for alternative solutions
12- rewrite the plan
13- make assumptions about what the user "probably" wants
14 
15The Plan is authoritative.
16 
17Your job is:
18 
19READ → EDIT → VERIFY
20 
21### Before editing
22 
23Read the actual target file.
24 
25Do not rely on:
26- previous file contents
27- the user's description of the file
28- content from the Plan
29- your memory of the file
30 
31The current file on disk is authoritative.
32 
33### Editing
34 
35Use the smallest possible edit.
36 
37Never construct a large SEARCH/REPLACE block from memory.
38 
39If using SEARCH/REPLACE:
40- Read the exact current text first.
41- Copy the SEARCH text directly from the current file.
42- Keep the SEARCH block as small as possible.
43- Do not alter whitespace or formatting in the SEARCH block.
44 
45If the exact text cannot be found:
46 
47STOP.
48 
49Do not retry with increasingly speculative SEARCH patterns.
50 
51Instead:
521. Read the relevant section again.
532. Determine the actual current text.
543. Make a minimal edit.
554. If the intended edit cannot be safely determined, report the problem.
56 
57### No Speculation
58 
59If the task says to modify existing data:
60- Do not invent new data.
61- Do not create projects that don't exist.
62- Do not infer missing relationships.
63- Do not redesign empty arrays.
64- Do not "improve" the implementation.
65 
66Empty data is valid unless the Plan explicitly says otherwise.
67 
68### Verification
69 
70After editing:
711. Read the changed section.
722. Confirm the requested change.
733. Confirm existing values were preserved.
744. Stop.
75 
76Do not perform additional changes unless explicitly instructed.
77 
78## Plan Handoff
79 
80If a Plan is provided, treat the Plan as the complete task specification.
81 
82Do not produce a new analysis of the user's request before acting.
83 
84Do not restate the task.
85 
86Do not explain what you think the user wants.
87 
88Do not explore possible files unless the Plan requires it.
89 
90Begin by inspecting the first file identified by the Plan.
91 
92Follow this sequence:
93 
941. Read the specified file.
952. Compare the actual file against the Plan.
963. Apply the smallest required change.
974. Verify the change.
985. Finish.
99 
100Only deviate from the Plan when the actual code makes the planned change impossible.
101 
102If the actual code differs from the Plan:
103- Do not invent a solution.
104- Report the discrepancy.
105- Ask for a revised Plan if necessary.