@@ -44,14 +44,13 @@ RULES FOR USING LSFUSION TOOLS
4444
4545A. HOW-TO AND EXAMPLES
4646
47- 1 . HOW-TO REQUESTS
48- For HOW-TO requests, the assistant MUST decompose the task
49- into sub-tasks, where each sub-task is a primitive HOW-TO task .
47+ 1 . The assistant MUST always request how-tos or examples via the corresponding
48+ tools for ANY task related to code (including writing, modifying,
49+ analyzing, or understanding code) .
5050
51- 2 . EXAMPLES / SAMPLES
52- For SAMPLES or EXAMPLES requests, the assistant MUST decompose
53- the task into sub-tasks, where each sub-task produces
54- a small number of code lines.
51+ 2 . The assistant MUST decompose the task into sub-tasks, each producing a small
52+ number of code lines, and try to format them in how-to style. This applies
53+ to both primitive building blocks (HOW-TO) and complex applied scenarios (EXAMPLES).
5554
5655----------------------------------------------------------------
5756
@@ -86,11 +85,14 @@ C. ELEMENT SEARCH
8685 - correctly fill the corresponding filters
8786 - try to find required elements in a SINGLE search call
8887
89- 3 . If required elements cannot be found:
90- - the assistant MUST analyze which of the already found elements
91- may be related to the missing ones
92- - then search for the required elements among related elements
93- using appropriate additional filters
88+ 3 . If required elements cannot be found (e.g. by name):
89+ - the assistant MUST do at least ONE of the following:
90+ a) the assistant MUST search without filters or with minimal filters
91+ (e.g. only scope/module/widely used words)
92+ to get a "brief" of the project and discover relevant elements
93+ b) the assistant MUST analyze which of the already found elements may be related
94+ to the missing ones, then search for the required elements among related elements
95+ using appropriate additional filters
9496
95974 . The assistant MUST prefer keyword-based search
9698 over regex-based search.
0 commit comments