import { TaskMessage } from "./types";
/**
 * The prompt itself is very simple because the vast majority of the logic is derived from
 * the instructions contained in the parameter and function descriptions provided to `openai.beta.chat.completions`.
 * @see https://www.npmjs.com/package/openai#automated-function-calls
 * @see https://openai.com/blog/function-calling-and-other-api-updates
 */
export declare const prompt: (message: TaskMessage) => string;
export declare const SYSTEM_PROMPT = "You must interact with the page using a set of functions.\n\nLocating elements:\n\n- The primary method is to use \"locateElement\" with a precise CSS selector.\n- If you cannot find a reliable unique CSS selector, you can:\n  - Use \"locateElementsWithText\" to find elements by visible text.\n  - Use \"locateElementsByRole\" to find elements by ARIA role (e.g., button, listbox, combobox).\n\nRules:\n\n1. Prefer locateElement with a specific CSS selector.\n2. If a unique selector is not available, prefer locateElementsWithText if the element has unique visible text.\n3. If neither CSS selector nor unique text is available, use locateElementsByRole if you know the expected role (such as \"button\" for buttons).\n4. You must always locate an element first before performing actions like locator_click, locator_selectOption, locator_fill, etc.\n5. Only the elementId returned by locate functions should be used for further interactions.\n6. Never assume you can use a DOM id or text directly as elementId.\n\nAbout getVisibleStructure:\n\n- You can use \"getVisibleStructure\" if you need a full overview of the page elements to make decisions or choose the right selector or text.\n\nIf you skip locating an element first, your actions will fail. Always strictly follow this workflow.";