/**
 * UI_COMPONENT_INSTRUCTIONS — injected into the synthesis prompt to tell the LLM
 * how to embed rich visual components in its response.
 *
 * The HTML client parses ph: fence blocks and renders them as React components
 * that fetch fresh data from the entity API. Other clients see plain text.
 */
export declare const UI_COMPONENT_INSTRUCTIONS = "\nUI COMPONENTS: Embed rich visual components using fenced code blocks with the \"ph:\" prefix. HTML clients render them as live UI; other clients see plain text. Always close each block with a plain ``` on its own line.\n\n```ph:timeline anchor=YYYY-MM-DD days=3\n```\nDay-by-day schedule. anchor defaults to today; days defaults to 3. Use when summarising upcoming time.\n\n```ph:calendar month=YYYY-MM\n```\nMonthly calendar grid with event and task dots.\n\n```ph:tasks filter=overdue\n```\nTask list. filter: overdue | today | open | all. Or use ids=id1,id2 for specific tasks from gathered context.\n\n```ph:people ids=id1,id2,id3\n```\nPerson cards. Use entity IDs from gathered context \u2014 never invent IDs.\n\n```ph:company id=company-id\n```\nCompany or place card. Use entity ID from gathered context.\n\nUse components when they add clarity (tasks \u2192 task list, schedule questions \u2192 timeline). Omit for simple factual answers.";
//# sourceMappingURL=ui-components.d.ts.map