fix(docs): update documentation to prefer component key in get_example calls

Author: Marina-L-Stoyanova

skills/igniteui-angular-components/references/data-display.md

@@ -251,7 +251,7 @@ Types for linear bar: `'default'`, `'info'`, `'success'`, `'warning'`, `'error'`
 
 ## Chat (AI Chat Component)
 
-> **Full doc in the MCP:** `get_doc({ framework: "angular", name: "chat" })` covers messages, attachments, quick replies, typing indicators, templates, and styling. Use `get_example({ framework: "angular", name: "chat" })` for working code samples. Prefer both over writing chat code from memory.
+> **Full doc in the MCP:** `get_doc({ framework: "angular", name: "chat" })` covers messages, attachments, quick replies, typing indicators, templates, and styling. Use `get_example({ framework: "angular", component: "chat" })` for working code samples. Prefer both over writing chat code from memory.
 
 ```typescript
 import { IgxChatComponent, IgxChatMessageContextDirective, type IgxChatOptions } from 'igniteui-angular/chat';

skills/igniteui-angular-components/references/directives.md

@@ -87,7 +87,7 @@ Inputs: `[igxRipple]` (ripple color), `[igxRippleCentered]` (always start from c
 
 ## Tooltip
 
-> **Full doc in the MCP:** `get_doc({ framework: "angular", name: "tooltip" })` covers triggers, overlay behavior, sticky/arrowed tooltips, styling, and accessibility. Use `get_example({ framework: "angular", name: "tooltip" })` for working code samples.
+> **Full doc in the MCP:** `get_doc({ framework: "angular", name: "tooltip" })` covers triggers, overlay behavior, sticky/arrowed tooltips, styling, and accessibility. Use `get_example({ framework: "angular", component: "tooltip" })` for working code samples.
 
 The at-a-glance pairing — `igxTooltipTarget` on the host references the `igxTooltip` element (both from `igniteui-angular/directives`):
 

skills/igniteui-angular-components/references/form-controls.md

@@ -40,7 +40,7 @@ Types: `line` (default), `border`, `box`, `search`.
 
 ## Combo (Multi-Select Dropdown)
 
-> **Full doc in the MCP:** `get_doc({ framework: "angular", name: "combo" })` covers data binding, selection APIs, forms support, keyboard behavior, and known issues. Use `get_example({ framework: "angular", name: "combo" })` for working code samples. Prefer both over this snippet when available.
+> **Full doc in the MCP:** `get_doc({ framework: "angular", name: "combo" })` covers data binding, selection APIs, forms support, keyboard behavior, and known issues. Use `get_example({ framework: "angular", component: "combo" })` for working code samples. Prefer both over this snippet when available.
 
 ```typescript
 import { IgxComboComponent } from 'igniteui-angular/combo';
@@ -52,7 +52,7 @@ import { IgxComboComponent } from 'igniteui-angular/combo';
 
 ## Simple Combo (Single-Select)
 
-> **Full doc in the MCP:** `get_doc({ framework: "angular", name: "simple-combo" })`. Use `get_example({ framework: "angular", name: "simple-combo" })` for working code samples.
+> **Full doc in the MCP:** `get_doc({ framework: "angular", name: "simple-combo" })`. Use `get_example({ framework: "angular", component: "simple-combo" })` for working code samples.
 
 `IgxSimpleComboComponent` from `igniteui-angular/simple-combo` (its own entry point, not `/combo`). Same API as `igx-combo` but restricted to single selection.
 

skills/igniteui-angular-figma-to-app/SKILL.md

@@ -382,7 +382,7 @@ Each row gives you:
 Call `list_components({ framework: "angular" })` **once** to discover which component
 families have full docs — **the catalog covers only a subset of components**. Then:
 
-- For families **with** a doc: call `get_example({ framework: "angular", name: "<doc-name>" })` (or `get_doc` when explanation context matters), all in a single parallel batch — never sequentially.
+- For families **with** a doc: call `get_example({ framework: "angular", component: "<doc-name>" })` (or `get_doc` when explanation context matters), all in a single parallel batch — never sequentially.
 - For families **without** a doc: read the matching reference files from the
   [`igniteui-angular-components`](../igniteui-angular-components/SKILL.md) and
   [`igniteui-angular-grids`](../igniteui-angular-grids/SKILL.md) skills, and use

skills/igniteui-angular-generate-from-image-design/SKILL.md

@@ -94,7 +94,7 @@ For component-to-Ignite-UI mapping, see [references/component-mapping.md](refere
 
 ## Step 4: Look Up Component API
 
-For every chosen component category that appears in the `list_components` results, call `get_example` with its doc `name` field (not the result title) — or `get_doc` when explanation context matters. **The doc catalog covers only a subset of components** — for categories without a doc, read the matching reference files from the [`igniteui-angular-components`](../igniteui-angular-components/SKILL.md) / [`igniteui-angular-grids`](../igniteui-angular-grids/SKILL.md) skills and use `search_api` for member-level API lookups. Read one or the other before coding — it gives exact usage patterns, inputs, and template structure.
+For every chosen component category that appears in the `list_components` results, call `get_example({ framework: "angular", component: "<name-field-value>" })` — pass the doc `name` field from `list_components` as the `component` parameter (not the result title) — or `get_doc` when explanation context matters. **The doc catalog covers only a subset of components** — for categories without a doc, read the matching reference files from the [`igniteui-angular-components`](../igniteui-angular-components/SKILL.md) / [`igniteui-angular-grids`](../igniteui-angular-grids/SKILL.md) skills and use `search_api` for member-level API lookups. Read one or the other before coding — it gives exact usage patterns, inputs, and template structure.
 
 Call `search_docs` for feature-based questions (e.g., "how to configure [component] for [specific behavior or styling need]") — it searches only the docs in the catalog.