@progress/kendo-react-mcp 1.6.2-beta.cd97a7ec.0 → 1.7.1-beta.d2eee4d2.0

package/dist/index.js

@@ -1,804 +1,15 @@
 #!/usr/bin/env node
+import{McpServer as Lt}from"@modelcontextprotocol/sdk/server/mcp.js";import{StdioServerTransport as Ut}from"@modelcontextprotocol/sdk/server/stdio.js";import{dirname as yt,join as bt}from"path";import{fileURLToPath as vt}from"url";import{loadLicense as it,decodeLicenseKey as at,decodeLicenseEvidence as lt}from"@progress/kendo-licensing/utils";var q=class extends Error{constructor(t){super(t),this.name="LicenseError"}};function ae(e){return e.replace(/^\uFEFF/,"")}async function le(e){let t=null,n=null;try{let o=it();if(!o.success){let s=new q(o.message);throw e&&await e("license_load_failed",{error:o.message}).catch(()=>{}),s}try{t=(await at(o.value)).licenses.find(async i=>!!(await lt(i)).userId)}catch(s){console.log(s.message),e&&await e("license_load_failed",{error:s.message||"Unknown decoding error"}).catch(()=>{})}if(!t)return[ae(o.value),null]}catch(o){return n=o.message||"Unknown error loading license.",e&&await e("license_load_failed",{error:n}).catch(()=>{}),[null,n]}return[ae(t),null]}import P from"node:fs";import $ from"node:path";var F=!1,N=process.env.DEBUG_LOG_FILE,ce=!!(N&&typeof N=="string");if(ce){let e=$.resolve(N),t=$.dirname(e);if(t!=="."&&t!==process.cwd()&&!P.existsSync(t))try{P.mkdirSync(t,{recursive:!0})}catch(n){console.error("Error creating log directory:",n)}if(!P.existsSync(e))try{P.writeFileSync(e,"")}catch(n){console.error("Error creating log file:",n)}}else F=!1;F=ce&&!!N&&P.existsSync($.resolve(N));function h(...e){if(F&&N){let o=`${new Date().toISOString()}: ${e.join(" ")}
+`,s=$.resolve(N);P.appendFile(s,o,i=>{i&&console.error("Error writing to log file:",i)})}}import ct from"@grpc/proto-loader";import D from"@grpc/grpc-js";import ue from"path";import de from"fs";import{fileURLToPath as dt}from"url";var pt=dt(import.meta.url),ut=ue.dirname(pt),me={version:"unknown"},pe=ue.resolve(ut,"../package.json");de.existsSync(pe)&&(me=JSON.parse(de.readFileSync(pe,"utf-8")));function mt(e){return e.replace(/\u2014/g,"--").replace(/\u2013/g,"-").replace(/[^\x20-\x7E]/g,"")}var M=class{constructor(t,n,o){this.contextApiUrl=t;this.protoPath=n;this.options=o;this.toolNameHeader="assistant";let s=ct.loadSync(this.protoPath,{keepCase:!0,longs:String,enums:String,defaults:!0,oneofs:!0});this.isDev=this.contextApiUrl?.includes("localhost")||this.contextApiUrl?.includes("127.0.0.1"),h("Using ContextApi URl:",this.contextApiUrl);let i=D.loadPackageDefinition(s),r=100*1024*1024,a={"grpc.max_receive_message_length":r,"grpc.max_send_message_length":r};this.client=new i.ContextQueryService(this.contextApiUrl||"contextapi.telerik.com:443",this.isDev?D.credentials.createInsecure():D.credentials.createSsl(),a)}async getMetadata({meta:t}={meta:{}}){let[n,o]=this.isDev?["fake_license",null]:await le((p,b)=>this.logEvent(p,b)),s=process.env.CONTEXTAPI_API_KEY,i=s&&typeof s=="string",r=n&&typeof n=="string";if(!r&&!i&&o)throw new Error(`Failed to authenticate with API key or License key!
 
-// packages/react/src/index.ts
-import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
-import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
-
-// packages/react/src/lib/grpc-client.ts
-import { dirname, join } from "path";
-import { fileURLToPath as fileURLToPath2 } from "url";
-
-// packages/mcp-common/src/lib/read-license.ts
-import {
-  loadLicense,
-  decodeLicenseKey,
-  decodeLicenseEvidence
-} from "@progress/kendo-licensing/utils";
-var LicenseError = class extends Error {
-  constructor(message) {
-    super(message);
-    this.name = "LicenseError";
-  }
-};
-function fixBom(licenseKey) {
-  return licenseKey.replace(/^\uFEFF/, "");
-}
-async function readLicense(logCallback) {
-  let licenseEvidence = null;
-  let error = null;
-  try {
-    const license = loadLicense();
-    if (!license.success) {
-      const licenseError = new LicenseError(license.message);
-      if (logCallback) {
-        await logCallback("license_load_failed", {
-          error: license.message
-        }).catch(() => {
-        });
-      }
-      throw licenseError;
-    }
-    try {
-      const decodedLicense = await decodeLicenseKey(license.value);
-      licenseEvidence = decodedLicense.licenses.find(async (lic) => {
-        const evidence = await decodeLicenseEvidence(lic);
-        if (evidence.userId) {
-          return true;
-        }
-        return false;
-      });
-    } catch (err) {
-      console.log(err.message);
-      if (logCallback) {
-        await logCallback("license_load_failed", {
-          error: err.message || "Unknown decoding error"
-        }).catch(() => {
-        });
-      }
-    }
-    if (!licenseEvidence) {
-      return [fixBom(license.value), null];
-    }
-  } catch (err) {
-    error = err.message || "Unknown error loading license.";
-    if (logCallback) {
-      await logCallback("license_load_failed", {
-        error
-      }).catch(() => {
-      });
-    }
-    return [null, error];
-  }
-  return [fixBom(licenseEvidence), null];
-}
-
-// packages/mcp-common/src/lib/logger.ts
-import fs from "node:fs";
-import path from "node:path";
-var LOG_ENABLED = false;
-var LOG_FILE = process.env.DEBUG_LOG_FILE;
-var LOG_FILE_DEFINED = !!(LOG_FILE && typeof LOG_FILE === "string");
-if (LOG_FILE_DEFINED) {
-  const resolvedLogFile = path.resolve(LOG_FILE);
-  const logDir = path.dirname(resolvedLogFile);
-  if (logDir !== "." && logDir !== process.cwd() && !fs.existsSync(logDir)) {
-    try {
-      fs.mkdirSync(logDir, { recursive: true });
-    } catch (err) {
-      console.error("Error creating log directory:", err);
-    }
-  }
-  if (!fs.existsSync(resolvedLogFile)) {
-    try {
-      fs.writeFileSync(resolvedLogFile, "");
-    } catch (err) {
-      console.error("Error creating log file:", err);
-    }
-  }
-} else {
-  LOG_ENABLED = false;
-}
-LOG_ENABLED = LOG_FILE_DEFINED && !!LOG_FILE && fs.existsSync(path.resolve(LOG_FILE));
-function log(...args) {
-  if (LOG_ENABLED && LOG_FILE) {
-    const date = /* @__PURE__ */ new Date();
-    const dateString = date.toISOString();
-    const logString = `${dateString}: ${args.join(" ")}
-`;
-    const resolvedLogFile = path.resolve(LOG_FILE);
-    fs.appendFile(resolvedLogFile, logString, (err) => {
-      if (err) {
-        console.error("Error writing to log file:", err);
-      }
-    });
-  }
-}
-
-// packages/mcp-common/src/lib/context-api.ts
-import protoLoader from "@grpc/proto-loader";
-import grpc from "@grpc/grpc-js";
-import path2 from "path";
-import fs2 from "fs";
-import { fileURLToPath } from "url";
-var __filename = fileURLToPath(import.meta.url);
-var __dirname = path2.dirname(__filename);
-var packageJson = { version: "unknown" };
-var packageJsonPath = path2.resolve(__dirname, "../package.json");
-if (fs2.existsSync(packageJsonPath)) {
-  packageJson = JSON.parse(fs2.readFileSync(packageJsonPath, "utf-8"));
-}
-function sanitizeMetadata(value) {
-  return value.replace(/\u2014/g, "--").replace(/\u2013/g, "-").replace(/[^\x20-\x7E]/g, "");
-}
-var D2CError = class extends Error {
-  constructor(code, message, details) {
-    super(message);
-    this.code = code;
-    this.details = details;
-    this.name = "D2CError";
-  }
-};
-var ContextAPI = class {
-  constructor(contextApiUrl, protoPath2, options) {
-    this.contextApiUrl = contextApiUrl;
-    this.protoPath = protoPath2;
-    this.options = options;
-    this.toolNameHeader = "assistant";
-    const proto = protoLoader.loadSync(this.protoPath, {
-      keepCase: true,
-      longs: String,
-      enums: String,
-      defaults: true,
-      oneofs: true
-    });
-    this.isDev = this.contextApiUrl?.includes("localhost") || this.contextApiUrl?.includes("127.0.0.1");
-    log("Using ContextApi URl:", this.contextApiUrl);
-    const protoDescriptor = grpc.loadPackageDefinition(proto);
-    const maxMsgSize = 100 * 1024 * 1024;
-    const channelOptions = {
-      "grpc.max_receive_message_length": maxMsgSize,
-      "grpc.max_send_message_length": maxMsgSize
-    };
-    this.client = new protoDescriptor.ContextQueryService(
-      this.contextApiUrl || "contextapi.telerik.com:443",
-      this.isDev ? grpc.credentials.createInsecure() : grpc.credentials.createSsl(),
-      channelOptions
-    );
-  }
-  async getMetadata({ meta } = { meta: {} }) {
-    const [license, error] = this.isDev ? ["fake_license", null] : await readLicense((eventName, fields) => this.logEvent(eventName, fields));
-    const apiKey = process.env.CONTEXTAPI_API_KEY;
-    const hasApiKey = apiKey && typeof apiKey === "string";
-    const hasLicense = license && typeof license === "string";
-    if (!hasLicense && !hasApiKey && error) {
-      throw new Error(
-        `Failed to authenticate with API key or License key!
-
-License Error: ${error}`
-      );
-    }
-    const metadata = new grpc.Metadata();
-    if (hasLicense) {
-      try {
-        metadata.add("x-license-key", license);
-      } catch (error2) {
-        log("Error adding license key to metadata:", error2);
-        throw new Error(`Failed to use license key: ${error2.message}`);
-      }
-    }
-    if (hasApiKey) {
-      metadata.add("x-api-key", apiKey);
-    }
-    if (this.options?.libName) {
-      metadata.add("x-library-name", this.options.libName);
-    }
-    metadata.add("x-tool-name", this.toolNameHeader);
-    const requestMetadata = JSON.stringify({
-      ...meta,
-      source: "npm",
-      version: packageJson.version,
-      os: process.platform,
-      node_version: process.version
-    });
-    metadata.add("x-request-metadata", sanitizeMetadata(requestMetadata));
-    return metadata;
-  }
-  async query(params, meta) {
-    const metadata = await this.getMetadata({ meta });
-    return new Promise((resolve, reject) => {
-      this.client.query(
-        params,
-        metadata,
-        (err, response) => {
-          if (err) {
-            reject(new Error(err));
-          } else {
-            resolve(response);
-          }
-        }
-      );
-    });
-  }
-  async getApiRefMatches(params, meta) {
-    const metadata = await this.getMetadata({ meta });
-    return new Promise((resolve, reject) => {
-      this.client.getApiRefMatches(
-        params,
-        metadata,
-        (err, response) => {
-          if (err) {
-            reject(new Error(err));
-          } else {
-            resolve(response);
-          }
-        }
-      );
-    });
-  }
-  async queryCssUtils(params, meta) {
-    const metadata = await this.getMetadata({ meta });
-    return new Promise((resolve, reject) => {
-      this.client.cssUtilsSearch(
-        params,
-        metadata,
-        (err, response) => {
-          if (err) {
-            log("Error querying CSS Utils:", err);
-            reject(new Error(err));
-          } else {
-            resolve(response);
-          }
-        }
-      );
-    });
-  }
-  async queryIconsSearch(params, meta) {
-    const metadata = await this.getMetadata({ meta });
-    return new Promise((resolve, reject) => {
-      this.client.iconsSearch(params, metadata, (err, response) => {
-        if (err) {
-          log("Error querying Icons Search:", err);
-          reject(new Error(err));
-        } else {
-          resolve(response);
-        }
-      });
-    });
-  }
-  async queryBuildingBlocks(params, meta) {
-    const metadata = await this.getMetadata({ meta });
-    return new Promise((resolve, reject) => {
-      this.client.buildingBlocksSearch(
-        params,
-        metadata,
-        (err, response) => {
-          if (err) {
-            log("Error querying Building Blocks:", err);
-            reject(new Error(err));
-          } else {
-            resolve(response);
-          }
-        }
-      );
-    });
-  }
-  async validateUserLicense() {
-    const metadata = await this.getMetadata();
-    return new Promise((resolve, reject) => {
-      this.client.validateUserLicense(
-        null,
-        metadata,
-        (err, response) => {
-          if (err) {
-            log("Error validating user license:", err);
-            reject(new Error(err));
-          } else {
-            resolve(response);
-          }
-        }
-      );
-    });
-  }
-  async queryThemeGenerate(params, meta) {
-    const metadata = await this.getMetadata({ meta });
-    return new Promise((resolve, reject) => {
-      this.client.generateTheme(params, metadata, (err, response) => {
-        if (err) {
-          log("Error querying context API/GenerateTheme:", err);
-          reject(new Error(err));
-        } else {
-          resolve(response);
-        }
-      });
-    });
-  }
-  async recordOrchestratorUserRequest({ meta }) {
-    const metadata = await this.getMetadata({ meta });
-    return new Promise((resolve, reject) => {
-      this.client.recordOrchestratorUserRequest(
-        null,
-        metadata,
-        (err, response) => {
-          if (err) {
-            log("Error recording orchestrator user request:", err);
-            reject(new Error(err));
-          } else {
-            resolve(response);
-          }
-        }
-      );
-    });
-  }
-  async recordToolUserRequest({ toolName, meta }) {
-    const metadata = await this.getMetadata({ meta });
-    return new Promise((resolve, reject) => {
-      this.client.recordToolUserRequest(
-        { tool_name: toolName },
-        metadata,
-        (err, response) => {
-          if (err) {
-            log("Error recording tool user request:", err);
-            reject(new Error(err));
-          } else {
-            resolve(response);
-          }
-        }
-      );
-    });
-  }
-  async logEvent(eventName, fields) {
-    const apiKey = "h8utJ6rk4PpIWX4JMn9beQDsjVUri6KV0XYfiVwq";
-    if (!apiKey || typeof apiKey !== "string") {
-      log("LOGGING_API_KEY not configured, skipping log event");
-      return;
-    }
-    const metadata = new grpc.Metadata();
-    metadata.add("x-api-key", apiKey);
-    return new Promise((resolve, reject) => {
-      this.client.logEvent(
-        { event_name: eventName, fields: fields || {} },
-        metadata,
-        (err, response) => {
-          if (err) {
-            log("Error logging event:", err);
-            reject(new Error(err));
-          } else {
-            resolve();
-          }
-        }
-      );
-    });
-  }
-  /**
-   * Process a Figma design through the D2C pipeline
-   * 
-   * @param params - Figma design data and processing options
-   * @returns Processed design with layout, styles, and component matches
-   * @throws D2CError if processing fails
-   */
-  async processFigmaDesign(params) {
-    const metadata = await this.getMetadata();
-    const request = {};
-    if (params.node_jsons && params.node_jsons.length > 0) {
-      request.node_jsons = params.node_jsons;
-    } else if (params.root_node_json) {
-      request.node_jsons = [params.root_node_json];
-    } else {
-      throw new Error("Either node_jsons or root_node_json must be provided");
-    }
-    return new Promise((resolve, reject) => {
-      this.client.processFigmaDesign(
-        request,
-        metadata,
-        (err, response) => {
-          if (err) {
-            log("Error processing Figma design:", err);
-            reject(new Error(`gRPC error: ${err.message}`));
-            return;
-          }
-          if (response.error) {
-            const error = new D2CError(
-              response.error.code,
-              response.error.message,
-              response.error.details
-            );
-            log("D2C processing error:", error);
-            reject(error);
-            return;
-          }
-          if (response.success) {
-            const layoutPseudoCodes = response.success.layout_pseudo_codes || [];
-            const result = {
-              // Backward compatibility: first layout or empty string
-              layout_pseudo_code: layoutPseudoCodes[0] || response.success.layout_pseudo_code || "",
-              layout_pseudo_codes: layoutPseudoCodes.length > 0 ? layoutPseudoCodes : [response.success.layout_pseudo_code || ""],
-              design_tokens: response.success.design_tokens || "",
-              stats: {
-                total_nodes: response.success.stats?.total_nodes || 0,
-                processing_time_ms: response.success.stats?.processing_time_ms || 0
-              }
-            };
-            resolve(result);
-            return;
-          }
-          reject(new Error("Invalid response format from server"));
-        }
-      );
-    });
-  }
-};
-
-// packages/mcp-common/src/models/user.ts
-import { z } from "zod";
-var userInfoSchema = z.object({
-  user_id: z.string(),
-  user_email: z.string().email()
-});
-
-// packages/mcp-common/src/models/entitlements.ts
-import { z as z2 } from "zod";
-var itemSchema = z2.object({
-  Product: z2.object({
-    Id: z2.number().int(),
-    Code: z2.string(),
-    Name: z2.string()
-  }),
-  License: z2.nullable(
-    z2.object({
-      Id: z2.number().int(),
-      Name: z2.string(),
-      Type: z2.string(),
-      Active: z2.boolean()
-    })
-  ),
-  Availability: z2.array(
-    z2.object({
-      LicenseStart: z2.nullable(z2.string().datetime()),
-      LicenseEnd: z2.nullable(z2.string().datetime())
-    })
-  ),
-  IsLicenseAvailable: z2.optional(z2.boolean())
-});
-var entitlementsSchema = z2.array(itemSchema);
-
-// packages/mcp-common/src/lib/utils.ts
-async function checkAccess(cb) {
-  const access = process.env.KENDO_MCP_ACCESS;
-  if (access === "true" || access === "1" || access === "full") {
-    return "full";
-  } else if (typeof access === "string" && (access.toLowerCase() === "agent" || access.toLowerCase() === "assistant")) {
-    return access.toLowerCase();
-  }
-  const productCode = await cb();
-  if (productCode.toLocaleLowerCase() === "agentic_ui_generator") {
-    return "agent";
-  }
-  if (productCode.toLocaleLowerCase() === "ai_coding_assistants") {
-    return "assistant";
-  }
-  return "none";
-}
-
-// packages/mcp-common/src/lib/instructions/accessibility.ts
-function getAccessibilityGuidelines() {
-  return `**Accessibility Guidelines: WCAG 2.2 Level AA Compliance**
-
-**Core Principles:**
-1. Use semantic HTML and ARIA correctly
-2. Ensure WCAG 2.2 AA compliance
-3. Follow W3C ARIA Authoring Practices
-4. Provide standards-based accessibility fixes
-
-**1. Form Control Labels** (WCAG 1.3.1, 3.3.2, 4.1.2)
-Every input must have an associated label.
-CORRECT: \`<input type="search" aria-label="Search products" placeholder="Search...">\`
-CORRECT: \`<label for="qty">Quantity</label><input type="number" id="qty">\`
-WRONG: \`<span>Email</span><input type="email">\` (no association)
-WRONG: \`<input type="email" placeholder="Email">\` (placeholder as label)
-
-**2. Button Accessibility** (WCAG 4.1.2, 2.4.6, 2.5.3)
-All buttons need accessible names describing their purpose.
-CORRECT: \`<button type="button">Save Changes</button>\`
-CORRECT: \`<button aria-label="Close dialog"><svg aria-hidden="true" focusable="false">...</svg></button>\`
-WRONG: \`<button><svg>...</svg></button>\` (no accessible name)
-WRONG: \`<button>Click here</button>\` (generic text)
-
-**3. Popup/Menu Triggers** (WCAG 4.1.2, 1.3.1)
-Indicate popup purpose and state using aria-haspopup, aria-expanded, aria-controls.
-CORRECT: \`<button aria-expanded="false" aria-haspopup="menu" aria-controls="menu-id">Settings</button>\`
-
-**4. Image Accessibility** (WCAG 1.1.1)
-Informative: \`<img src="chart.png" alt="Sales increased 25% in Q4 2024">\`
-Functional: \`<a href="/home"><img src="logo.png" alt="Company Name Home"></a>\`
-Decorative: \`<img src="border.png" alt="" role="presentation">\`
-Complex: \`<img src="chart.png" alt="Sales data" aria-describedby="desc-id">\`
-WRONG: Missing alt, filename as alt, generic alt for decorative images
-
-**5. Link Accessibility** (WCAG 2.4.4, 2.4.6)
-Links must be descriptive and understandable out of context.
-CORRECT: \`<a href="/products">View All Products</a>\`
-CORRECT: \`<a href="/article" aria-label="Read more about New Product Launch">Read more</a>\`
-WRONG: "Click here", "Read more", "Learn more" without context
-
-**6. Form Validation** (WCAG 3.3.1, 3.3.2, 3.3.3)
-Errors must be identified, associated with inputs, and provide suggestions. Use aria-describedby, aria-invalid="true", and role="alert".
-
-**7. Heading Structure** (WCAG 1.3.1, 2.4.6)
-Each page must have an \`<h1>\` that describes its content. Use hierarchical, descriptive headings with no skipped levels (h1\u2192h2\u2192h3).
-CORRECT: \`<h1>Dashboard</h1> <h2>Sales</h2> <h3>By Region</h3>\`
-WRONG: No \`<h1>\` on the page, or skipping levels (h1\u2192h3)
-If a heading should look smaller than its semantic level, use CSS: \`<h2 class="text-sm">Subtitle</h2>\`
-
-**8. Page Component Landmark Rules** (WCAG 1.3.1, 4.1.2)
-Page components (route components) may be rendered inside a layout that already provides \`<main>\`, \`<header>\`, or \`<footer>\`. Since the layout configuration is unknown, avoid using these landmarks in page components to prevent potential duplication and nesting violations. Use \`<div>\`, \`<section>\`, or \`<article>\` as the top-level wrapper instead.
-- Avoid adding \`<main>\`, \`role="main"\`, \`<header>\`, or \`<footer>\` in page components \u2014 the layout typically provides them. Duplicating them can cause \`landmark-no-duplicate-main\` and \`landmark-main-is-top-level\` violations.
-- Avoid adding \`role="banner"\` or using a semantic \`<header>\` element in page components \u2014 the layout's \`<header>\` already claims the banner landmark. Adding another causes \`landmark-banner-is-top-level\` violations.
-- Avoid adding \`role="contentinfo"\` to elements inside page components \u2014 the contentinfo landmark should be a top-level landmark, not nested inside \`<main>\` or other landmarks. Nesting it can cause \`landmark-contentinfo-is-top-level\` violations.
-- When multiple \`<section>\` or \`<nav>\` elements exist on a page, give each a unique \`aria-label\` to avoid \`landmark-unique\` violations.
-
-**9. ARIA Role and Attribute Restrictions** (WCAG 4.1.2)
-Only use ARIA roles that are valid for the given HTML element. Avoid adding \`aria-label\` or \`aria-labelledby\` to elements that do not permit naming.
-- \`<article>\` has an implicit \`article\` role. Do NOT override it with \`role="listitem"\`, \`role="button"\`, \`role="link"\`, or any other role \u2014 none are allowed on \`<article>\`. Use \`<li>\` for list items, \`<button>\` for interactive cards, or \`<a>\` for clickable cards instead.
-- \`<button>\` already has an implicit \`button\` role. Do NOT add \`role="listitem"\` or other incompatible roles.
-- \`<span>\` and \`<div>\` without roles are generic elements. Do NOT add \`aria-label\` to them \u2014 it is a prohibited attribute on elements with no accessible role and can cause \`aria-prohibited-attr\` violations. Instead, use \`role="img"\` + \`aria-label\` for visual indicators, or use visually hidden text.
-- Do NOT add \`aria-label\` to non-interactive \`<div>\` wrappers \u2014 it has no effect and triggers violations.
-- \`aria-pressed\` is only valid on elements with \`role="button"\`, \`role="checkbox"\`, \`role="menuitemcheckbox"\`, \`role="option"\`, \`role="radio"\`, or \`role="switch"\`. Do NOT use \`aria-pressed\` on elements with \`role="listitem"\` or other roles.
-CORRECT: \`<ul role="list"><li class="product-card">...</li></ul>\` (listitem inside list)
-CORRECT: \`<span role="img" aria-label="Status: pending" class="status-dot"></span>\` (role added before aria-label)
-CORRECT: \`<span class="status-dot" aria-hidden="true"></span><span class="visually-hidden">Pending</span>\` (hidden text alternative)
-WRONG: \`<article role="listitem">\` (listitem not allowed on article)
-WRONG: \`<article role="button">\` (button not allowed on article \u2014 use \`<button>\` or \`<div role="button">\`)
-WRONG: \`<span aria-label="pending" class="status-dot"></span>\` (aria-label prohibited on generic span)
-WRONG: \`<div aria-label="Product badges" class="badges"></div>\` (aria-label prohibited on generic div)
-
-**Quick Checklist:**
-- **Forms:** Associated labels, aria-required on required fields, autocomplete attributes, aria-describedby for errors, aria-invalid for invalid fields, fieldsets with legends
-- **Buttons/Links:** Accessible names, aria-label for icon buttons, aria-hidden on decorative icons, descriptive link text
-- **Popups/Dialogs:** aria-haspopup, aria-expanded, aria-controls, role="dialog", aria-modal="true", aria-labelledby, focus trap, Escape to close
-- **Images:** alt on all images, descriptive alt for informative, empty alt for decorative, aria-describedby for complex
-- **Structure:** One h1, logical heading hierarchy, avoid \`<main>\`, \`<header>\`, \`<footer>\`, \`role="main"\`, \`role="contentinfo"\`, \`role="banner"\` in page/route components (the layout may already provide them), use \`<section>\` or \`<div>\` as page-level wrappers, unique aria-labels on duplicate landmark types
-- **ARIA Rules:** Avoid adding \`aria-label\` to generic \`<span>\`/\`<div>\` without a role, avoid using \`role="listitem"\` or \`role="button"\` on \`<article>\` \u2014 use \`<li>\` for list items, add \`role="img"\` before \`aria-label\` on visual indicators, \`aria-pressed\` only on button-like roles
-- **Scrollable Regions:** Any scrollable container must have \`tabindex="0"\` or contain keyboard-interactive children
-- **Nested Interactive:** Do not add interactive role/tabindex to a container that already has focusable children
-- **List Roles:** \`role="list"\` containers must have \`role="listitem"\` children \u2014 prefer \`<ul>/<li>\` natively
-- **Dynamic Content:** role="status"/aria-live="polite" for updates, role="alert"/aria-live="assertive" for critical alerts
-- **Keyboard/Focus:** All interactive elements keyboard accessible, logical focus order, visible focus indicators, no keyboard traps (except modals)
-- **Color/Contrast:** 4.5:1 text contrast (3:1 large text), 3:1 UI component contrast, no color-only information, 3:1 focus indicator contrast`;
-}
-
-// packages/mcp-common/src/lib/heartbeat.ts
-var ONE_DAY_MS = 24 * 60 * 60 * 1e3;
-function startHeartbeat(options) {
-  const {
-    serverName,
-    contextApi: contextApi2,
-    additionalFields = {},
-    intervalMs = ONE_DAY_MS
-  } = options;
-  const eventName = `mcp_server_heartbeat`;
-  const sendHeartbeat = async () => {
-    try {
-      const fields = {
-        server_name: serverName,
-        timestamp: (/* @__PURE__ */ new Date()).toISOString(),
-        ...additionalFields
-      };
-      await contextApi2.logEvent(eventName, fields);
-    } catch (error) {
-      log(`Failed to send heartbeat for ${serverName}:`, error);
-    }
-  };
-  sendHeartbeat();
-  const intervalId = setInterval(sendHeartbeat, intervalMs);
-  return () => {
-    clearInterval(intervalId);
-    log(`Heartbeat stopped for ${serverName}`);
-  };
-}
-
-// packages/mcp-common/src/lib/getting-started-params.ts
-import { z as z3 } from "zod";
-var KendoThemes = ["default", "bootstrap", "material", "fluent"];
-function createGettingStartedInputSchema(suiteName, defaultProjectName) {
-  return {
-    projectName: z3.string().default(defaultProjectName).describe(
-      "The name of the project. Used as the project folder name when creating a new project."
-    ),
-    createNewProject: z3.boolean().default(true).describe(
-      `Whether to create a new project before configuring ${suiteName}. Set to true to scaffold a brand-new project, or false if the project already exists and you only want to add ${suiteName} to it.`
-    ),
-    theme: z3.enum(KendoThemes).default("default").describe(
-      "The Kendo UI theme to use. Determines which theme package is installed and imported."
-    )
-  };
-}
-
-// packages/react/src/lib/constants.ts
-var REACT_SUITE_NAME = "Kendo UI for React";
-var Suite = "react";
-var PRODUCT_LINE = "kendo";
-var ReactComponents = [
-  "ActionSheet",
-  "AIPrompt",
-  "Animation",
-  "AppBar",
-  "ArcGauge",
-  "AutoComplete",
-  "Avatar",
-  "Badge",
-  "Barcode",
-  "BottomNavigation",
-  "Breadcrumb",
-  "Button",
-  "ButtonGroup",
-  "BreadCrumb",
-  "Calendar",
-  "Card",
-  "Chart",
-  "ChartWizard",
-  "Chat",
-  "Checkbox",
-  "Chip",
-  "ChipList",
-  "ChunkProgressBar",
-  "CircularGauge",
-  "ColorGradient",
-  "ColorPalette",
-  "ColorPicker",
-  "ComboBox",
-  "ContextMenu",
-  "ConversationalUI",
-  "DataGrid",
-  "Grid",
-  // Alias for DataGrid only used in the mcp-server
-  "DataQuery",
-  "DateMath",
-  "DateInput",
-  "DatePicker",
-  "DateRangePicker",
-  "DateTimePicker",
-  "Dialog",
-  "Drag&Drop",
-  "Drawer",
-  "Drawing",
-  "DropDownButton",
-  "DropDownList",
-  "DropDownTree",
-  "Editor",
-  "Error",
-  "ExcelExport",
-  "ExpansionPanel",
-  "ExternalDropZone",
-  "FileSaver",
-  "FileManager",
-  "Filter",
-  "FlatColorPicker",
-  "FloatingActionButton",
-  "FloatingLabel",
-  "Form",
-  "Gantt",
-  "Gauge",
-  "General",
-  "GridLayout",
-  "Hint",
-  "Icon",
-  "InlineAIPrompt",
-  "Input",
-  "Label",
-  "LinearGauge",
-  "ListBox",
-  "ListView",
-  "Loader",
-  "Map",
-  "MaskedTextBox",
-  "Menu",
-  "MultiColumnComboBox",
-  "MultiSelect",
-  "MultiSelectTree",
-  "MultiViewCalendar",
-  "Notification",
-  "NumericTextBox",
-  "OrgChart",
-  "PageTemplates/BuildingBlocks",
-  "Pager",
-  "PanelBar",
-  "PDFProcessing",
-  "PDFViewer",
-  "PivotGrid",
-  "Popover",
-  "Popup",
-  "ProgressBar",
-  "PromptBox",
-  "QRCode",
-  "RadialGauge",
-  "RadioButton",
-  "RadioGroup",
-  "RangeSlider",
-  "Rating",
-  "Ripple",
-  "Sankey",
-  "Scheduler",
-  "ScrollView",
-  "Signature",
-  "Skeleton",
-  "Slider",
-  "Sortable",
-  "Sparkline",
-  "SpeechToTextButton",
-  "SmartPasteButton",
-  "SplitButton",
-  "Splitter",
-  "Spreadsheet",
-  "StackLayout",
-  "Stepper",
-  "StockChart",
-  "SVGIcon",
-  "Switch",
-  "TabStrip",
-  "TaskBoard",
-  "TextArea",
-  "TextBox",
-  "TileLayout",
-  "Timeline",
-  "TimePicker",
-  "Toolbar",
-  "Tooltip",
-  "TreeList",
-  "TreeView",
-  "Typography",
-  "Upload",
-  "VSCodeExtension",
-  "Window"
-];
-
-// packages/react/src/lib/grpc-client.ts
-var protoPath = join(
-  dirname(fileURLToPath2(import.meta.url)),
-  "../proto/service.proto"
-);
-var contextApi = new ContextAPI("contextapi.telerik.com:443", protoPath, {
-  libName: Suite
-});
-var validateUserLicense = async () => {
-  return contextApi.validateUserLicense();
-};
-
-// packages/react/src/index.ts
-import fs3 from "fs";
-import path3 from "path";
-import { fileURLToPath as fileURLToPath3 } from "url";
-
-// packages/kendo-ui-agent/src/lib/tools-factory.ts
-import { z as z4 } from "zod";
-
-// packages/kendo-ui-agent/src/lib/ui-agent-tool.ts
-var UIAgentTool = class {
-  constructor(name, config, cb) {
-    this.name = name;
-    this.config = config;
-    this.cb = cb;
-  }
-  register(mcpServer) {
-    this.server = mcpServer;
-    this.server.registerTool(this.name, this.config, this.cb);
-  }
-  hasAccess(accessType) {
-    if (!this.config.requiredAccess || this.config.requiredAccess.length === 0) {
-      return true;
-    }
-    return accessType === "full" || this.config.requiredAccess.includes(accessType);
-  }
-};
-
-// packages/kendo-ui-agent/src/lib/templates/validator.ts
-var renderValidatorResponse = (ctx, frameworkValidationSteps) => `# ${ctx.suiteName} - Code Validation & Quality Assurance
+License Error: ${o}`);let a=new D.Metadata;if(r)try{a.add("x-license-key",n)}catch(p){throw h("Error adding license key to metadata:",p),new Error(`Failed to use license key: ${p.message}`)}i&&a.add("x-api-key",s),this.options?.libName&&a.add("x-library-name",this.options.libName),a.add("x-tool-name",this.toolNameHeader);let d=JSON.stringify({...t,source:"npm",version:me.version,os:process.platform,node_version:process.version});return a.add("x-request-metadata",mt(d)),a}async query(t,n){let o=await this.getMetadata({meta:n});return new Promise((s,i)=>{this.client.query(t,o,(r,a)=>{r?i(new Error(r)):s(a)})})}async getApiRefMatches(t,n){let o=await this.getMetadata({meta:n});return new Promise((s,i)=>{this.client.getApiRefMatches(t,o,(r,a)=>{r?i(new Error(r)):s(a)})})}async queryCssUtils(t,n){let o=await this.getMetadata({meta:n});return new Promise((s,i)=>{this.client.cssUtilsSearch(t,o,(r,a)=>{r?(h("Error querying CSS Utils:",r),i(new Error(r))):s(a)})})}async queryIconsSearch(t,n){let o=await this.getMetadata({meta:n});return new Promise((s,i)=>{this.client.iconsSearch(t,o,(r,a)=>{r?(h("Error querying Icons Search:",r),i(new Error(r))):s(a)})})}async queryBuildingBlocks(t,n){let o=await this.getMetadata({meta:n});return new Promise((s,i)=>{this.client.buildingBlocksSearch(t,o,(r,a)=>{r?(h("Error querying Building Blocks:",r),i(new Error(r))):s(a)})})}async validateUserLicense(){let t=await this.getMetadata();return new Promise((n,o)=>{this.client.validateUserLicense(null,t,(s,i)=>{s?(h("Error validating user license:",s),o(new Error(s))):n(i)})})}async queryThemeGenerate(t,n){let o=await this.getMetadata({meta:n});return new Promise((s,i)=>{this.client.generateTheme(t,o,(r,a)=>{r?(h("Error querying context API/GenerateTheme:",r),i(new Error(r))):s(a)})})}async recordOrchestratorUserRequest({meta:t}){let n=await this.getMetadata({meta:t});return new Promise((o,s)=>{this.client.recordOrchestratorUserRequest(null,n,(i,r)=>{i?(h("Error recording orchestrator user request:",i),s(new Error(i))):o(r)})})}async recordToolUserRequest({toolName:t,meta:n}){let o=await this.getMetadata({meta:n});return new Promise((s,i)=>{this.client.recordToolUserRequest({tool_name:t},o,(r,a)=>{r?(h("Error recording tool user request:",r),i(new Error(r))):s(a)})})}async logEvent(t,n){let o=process.env.LOGGING_API_KEY;if(!o||typeof o!="string"){h("LOGGING_API_KEY not configured, skipping log event");return}let s=new D.Metadata;return s.add("x-api-key",o),new Promise((i,r)=>{this.client.logEvent({event_name:t,fields:n||{}},s,(a,d)=>{a?(h("Error logging event:",a),r(new Error(a))):i()})})}};import{z as K}from"zod";var io=K.object({user_id:K.string(),user_email:K.string().email()});import{z as k}from"zod";var ht=k.object({Product:k.object({Id:k.number().int(),Code:k.string(),Name:k.string()}),License:k.nullable(k.object({Id:k.number().int(),Name:k.string(),Type:k.string(),Active:k.boolean()})),Availability:k.array(k.object({LicenseStart:k.nullable(k.string().datetime()),LicenseEnd:k.nullable(k.string().datetime())})),IsLicenseAvailable:k.optional(k.boolean())}),co=k.array(ht);async function he(e){let t=process.env.KENDO_MCP_ACCESS;if(t==="true"||t==="1"||t==="full")return"full";if(typeof t=="string"&&(t.toLowerCase()==="agent"||t.toLowerCase()==="assistant"))return t.toLowerCase();let n=await e();return n.toLocaleLowerCase()==="agentic_ui_generator"?"agent":n.toLocaleLowerCase()==="ai_coding_assistants"?"assistant":"none"}function ge(){return'**Accessibility Guidelines: WCAG 2.2 Level AA Compliance**\n\n**Core Principles:**\n1. Use semantic HTML and ARIA correctly\n2. Ensure WCAG 2.2 AA compliance\n3. Follow W3C ARIA Authoring Practices\n4. Provide standards-based accessibility fixes\n\n**1. Form Control Labels** (WCAG 1.3.1, 3.3.2, 4.1.2)\nEvery input must have an associated label.\nCORRECT: `<input type="search" aria-label="Search products" placeholder="Search...">`\nCORRECT: `<label for="qty">Quantity</label><input type="number" id="qty">`\nWRONG: `<span>Email</span><input type="email">` (no association)\nWRONG: `<input type="email" placeholder="Email">` (placeholder as label)\n\n**2. Button Accessibility** (WCAG 4.1.2, 2.4.6, 2.5.3)\nAll buttons need accessible names describing their purpose.\nCORRECT: `<button type="button">Save Changes</button>`\nCORRECT: `<button aria-label="Close dialog"><svg aria-hidden="true" focusable="false">...</svg></button>`\nWRONG: `<button><svg>...</svg></button>` (no accessible name)\nWRONG: `<button>Click here</button>` (generic text)\n\n**3. Popup/Menu Triggers** (WCAG 4.1.2, 1.3.1)\nIndicate popup purpose and state using aria-haspopup, aria-expanded, aria-controls.\nCORRECT: `<button aria-expanded="false" aria-haspopup="menu" aria-controls="menu-id">Settings</button>`\n\n**4. Image Accessibility** (WCAG 1.1.1)\nInformative: `<img src="chart.png" alt="Sales increased 25% in Q4 2024">`\nFunctional: `<a href="/home"><img src="logo.png" alt="Company Name Home"></a>`\nDecorative: `<img src="border.png" alt="" role="presentation">`\nComplex: `<img src="chart.png" alt="Sales data" aria-describedby="desc-id">`\nWRONG: Missing alt, filename as alt, generic alt for decorative images\n\n**5. Link Accessibility** (WCAG 2.4.4, 2.4.6)\nLinks must be descriptive and understandable out of context.\nCORRECT: `<a href="/products">View All Products</a>`\nCORRECT: `<a href="/article" aria-label="Read more about New Product Launch">Read more</a>`\nWRONG: "Click here", "Read more", "Learn more" without context\n\n**6. Form Validation** (WCAG 3.3.1, 3.3.2, 3.3.3)\nErrors must be identified, associated with inputs, and provide suggestions. Use aria-describedby, aria-invalid="true", and role="alert".\n\n**7. Heading Structure** (WCAG 1.3.1, 2.4.6)\nEach page must have an `<h1>` that describes its content. Use hierarchical, descriptive headings with no skipped levels (h1\u2192h2\u2192h3).\nCORRECT: `<h1>Dashboard</h1> <h2>Sales</h2> <h3>By Region</h3>`\nWRONG: No `<h1>` on the page, or skipping levels (h1\u2192h3)\nIf a heading should look smaller than its semantic level, use CSS: `<h2 class="text-sm">Subtitle</h2>`\n\n**8. Page Component Landmark Rules** (WCAG 1.3.1, 4.1.2)\nPage components (route components) may be rendered inside a layout that already provides `<main>`, `<header>`, or `<footer>`. Since the layout configuration is unknown, avoid using these landmarks in page components to prevent potential duplication and nesting violations. Use `<div>`, `<section>`, or `<article>` as the top-level wrapper instead.\n- Avoid adding `<main>`, `role="main"`, `<header>`, or `<footer>` in page components \u2014 the layout typically provides them. Duplicating them can cause `landmark-no-duplicate-main` and `landmark-main-is-top-level` violations.\n- Avoid adding `role="banner"` or using a semantic `<header>` element in page components \u2014 the layout\'s `<header>` already claims the banner landmark. Adding another causes `landmark-banner-is-top-level` violations.\n- Avoid adding `role="contentinfo"` to elements inside page components \u2014 the contentinfo landmark should be a top-level landmark, not nested inside `<main>` or other landmarks. Nesting it can cause `landmark-contentinfo-is-top-level` violations.\n- When multiple `<section>` or `<nav>` elements exist on a page, give each a unique `aria-label` to avoid `landmark-unique` violations.\n\n**9. ARIA Role and Attribute Restrictions** (WCAG 4.1.2)\nOnly use ARIA roles that are valid for the given HTML element. Avoid adding `aria-label` or `aria-labelledby` to elements that do not permit naming.\n- `<article>` has an implicit `article` role. Do NOT override it with `role="listitem"`, `role="button"`, `role="link"`, or any other role \u2014 none are allowed on `<article>`. Use `<li>` for list items, `<button>` for interactive cards, or `<a>` for clickable cards instead.\n- `<button>` already has an implicit `button` role. Do NOT add `role="listitem"` or other incompatible roles.\n- `<span>` and `<div>` without roles are generic elements. Do NOT add `aria-label` to them \u2014 it is a prohibited attribute on elements with no accessible role and can cause `aria-prohibited-attr` violations. Instead, use `role="img"` + `aria-label` for visual indicators, or use visually hidden text.\n- Do NOT add `aria-label` to non-interactive `<div>` wrappers \u2014 it has no effect and triggers violations.\n- `aria-pressed` is only valid on elements with `role="button"`, `role="checkbox"`, `role="menuitemcheckbox"`, `role="option"`, `role="radio"`, or `role="switch"`. Do NOT use `aria-pressed` on elements with `role="listitem"` or other roles.\nCORRECT: `<ul role="list"><li class="product-card">...</li></ul>` (listitem inside list)\nCORRECT: `<span role="img" aria-label="Status: pending" class="status-dot"></span>` (role added before aria-label)\nCORRECT: `<span class="status-dot" aria-hidden="true"></span><span class="visually-hidden">Pending</span>` (hidden text alternative)\nWRONG: `<article role="listitem">` (listitem not allowed on article)\nWRONG: `<article role="button">` (button not allowed on article \u2014 use `<button>` or `<div role="button">`)\nWRONG: `<span aria-label="pending" class="status-dot"></span>` (aria-label prohibited on generic span)\nWRONG: `<div aria-label="Product badges" class="badges"></div>` (aria-label prohibited on generic div)\n\n**Quick Checklist:**\n- **Forms:** Associated labels, aria-required on required fields, autocomplete attributes, aria-describedby for errors, aria-invalid for invalid fields, fieldsets with legends\n- **Buttons/Links:** Accessible names, aria-label for icon buttons, aria-hidden on decorative icons, descriptive link text\n- **Popups/Dialogs:** aria-haspopup, aria-expanded, aria-controls, role="dialog", aria-modal="true", aria-labelledby, focus trap, Escape to close\n- **Images:** alt on all images, descriptive alt for informative, empty alt for decorative, aria-describedby for complex\n- **Structure:** One h1, logical heading hierarchy, avoid `<main>`, `<header>`, `<footer>`, `role="main"`, `role="contentinfo"`, `role="banner"` in page/route components (the layout may already provide them), use `<section>` or `<div>` as page-level wrappers, unique aria-labels on duplicate landmark types\n- **ARIA Rules:** Avoid adding `aria-label` to generic `<span>`/`<div>` without a role, avoid using `role="listitem"` or `role="button"` on `<article>` \u2014 use `<li>` for list items, add `role="img"` before `aria-label` on visual indicators, `aria-pressed` only on button-like roles\n- **Scrollable Regions:** Any scrollable container must have `tabindex="0"` or contain keyboard-interactive children\n- **Nested Interactive:** Do not add interactive role/tabindex to a container that already has focusable children\n- **List Roles:** `role="list"` containers must have `role="listitem"` children \u2014 prefer `<ul>/<li>` natively\n- **Dynamic Content:** role="status"/aria-live="polite" for updates, role="alert"/aria-live="assertive" for critical alerts\n- **Keyboard/Focus:** All interactive elements keyboard accessible, logical focus order, visible focus indicators, no keyboard traps (except modals)\n- **Color/Contrast:** 4.5:1 text contrast (3:1 large text), 3:1 UI component contrast, no color-only information, 3:1 focus indicator contrast'}var gt=1440*60*1e3;function fe(e){let{serverName:t,contextApi:n,additionalFields:o={},intervalMs:s=gt}=e,i="mcp_server_heartbeat",r=async()=>{try{let d={server_name:t,timestamp:new Date().toISOString(),...o};await n.logEvent(i,d)}catch(d){h(`Failed to send heartbeat for ${t}:`,d)}};r();let a=setInterval(r,s);return()=>{clearInterval(a),h(`Heartbeat stopped for ${t}`)}}import{z as j}from"zod";var ft=["default","bootstrap","material","fluent"];function ye(e,t){return{projectName:j.string().default(t).describe("The name of the project. Used as the project folder name when creating a new project."),createNewProject:j.boolean().default(!0).describe(`Whether to create a new project before configuring ${e}. Set to true to scaffold a brand-new project, or false if the project already exists and you only want to add ${e} to it.`),theme:j.enum(ft).default("default").describe("The Kendo UI theme to use. Determines which theme package is installed and imported.")}}var c="Kendo UI for React",T="react",x="kendo";var O=["ActionSheet","AIPrompt","Animation","AppBar","ArcGauge","AutoComplete","Avatar","Badge","Barcode","BottomNavigation","Breadcrumb","Button","ButtonGroup","BreadCrumb","Calendar","Card","Chart","ChartWizard","Chat","Checkbox","Chip","ChipList","ChunkProgressBar","CircularGauge","ColorGradient","ColorPalette","ColorPicker","ComboBox","ContextMenu","ConversationalUI","DataGrid","Grid","DataQuery","DateMath","DateInput","DatePicker","DateRangePicker","DateTimePicker","Dialog","Drag&Drop","Drawer","Drawing","DropDownButton","DropDownList","DropDownTree","Editor","Error","ExcelExport","ExpansionPanel","ExternalDropZone","FileSaver","FileManager","Filter","FlatColorPicker","FloatingActionButton","FloatingLabel","Form","Gantt","Gauge","General","GridLayout","Hint","Icon","InlineAIPrompt","Input","Label","LinearGauge","ListBox","ListView","Loader","Map","MaskedTextBox","Menu","MultiColumnComboBox","MultiSelect","MultiSelectTree","MultiViewCalendar","Notification","NumericTextBox","OrgChart","PageTemplates/BuildingBlocks","Pager","PanelBar","PDFProcessing","PDFViewer","PivotGrid","Popover","Popup","ProgressBar","PromptBox","QRCode","RadialGauge","RadioButton","RadioGroup","RangeSlider","Rating","Ripple","Sankey","Scheduler","ScrollView","Signature","Skeleton","Slider","Sortable","Sparkline","SpeechToTextButton","SmartPasteButton","SplitButton","Splitter","Spreadsheet","StackLayout","Stepper","StockChart","SVGIcon","Switch","TabStrip","TaskBoard","TextArea","TextBox","TileLayout","Timeline","TimePicker","Toolbar","Tooltip","TreeList","TreeView","Typography","Upload","VSCodeExtension","Window"];var kt=bt(yt(vt(import.meta.url)),"../proto/service.proto"),G=new M("test.contextapi.telerik.com:443",kt,{libName:T});var be=async()=>G.validateUserLicense();import _t from"fs";import ot from"path";import{fileURLToPath as $t}from"url";import{z as v}from"zod";var S=class{constructor(t,n,o){this.name=t;this.config=n;this.cb=o}register(t){this.server=t,this.server.registerTool(this.name,this.config,this.cb)}hasAccess(t){return!this.config.requiredAccess||this.config.requiredAccess.length===0?!0:t==="full"||this.config.requiredAccess.includes(t)}};var L=(e,t)=>`# ${e.suiteName} - Code Validation & Quality Assurance
 
 ## Comprehensive Code Validation Checklist
 Execute these validation steps systematically to ensure high-quality, maintainable code:
 
 ### Validation Phase: Framework-Specific Validation
 
-${frameworkValidationSteps}
+${t}
 
 ### Validation Phase: General Code Quality & Best Practices
 
@@ -835,97 +46,179 @@ Responsive Design:
 - Graceful error handling for all user interactions
 - Meaningful error messages for users
 - Network error handling for API calls
-`;
-
-// packages/kendo-ui-agent/src/lib/templates/orchestrator.ts
-var responsiveKendoDesignSystemGuidance = (ctx) => `**Tool call example:**
+`;var V=()=>`## UX/UI Design Best Practices
+
+> **These are default guidelines \u2014 follow them when the user has not stated otherwise.** If the user explicitly requests different behavior (e.g., a specific component size, a custom row limit, alternate breakpoints, a different layout pattern), defer to the user's stated preference and disregard the conflicting default below. Only accessibility and WCAG requirements (contrast ratios, focus indicators, semantic HTML, ARIA) apply regardless of user preference.
+
+Follow these principles when building or reviewing any UI. They apply regardless of the visual style requested.
+
+### Visual Hierarchy & Typography
+- Use a strict 3-level heading hierarchy: page title (h1) \u2192 section heading (h2) \u2192 component label (h3). Never skip levels.
+- Body text line length: 60\u201380 characters maximum. Wider lines reduce readability.
+- Numeric and currency columns must use \`font-variant-numeric: tabular-nums\` to keep digits column-aligned.
+- Never use more than 2 typefaces in a single interface.
+
+### Color & Contrast
+- Body text contrast ratio: \u2265 4.5:1 against its background.
+- Large text (\u2265 18pt / 14pt bold) and UI component boundaries: \u2265 3:1.
+- Use only the 5 semantic color slots \u2014 primary, success, warning, error, info \u2014 for meaning. Do not invent new semantic colors.
+- Never use color alone to convey status or meaning (8% of men have color vision deficiency). Always pair color with an icon or text label.
+- Never use red and green as the sole distinguishing colors.
+
+### Component Sizing & Density
+- Never mix size variants within the same form or toolbar. Pick one: \`"small"\`, \`"medium"\`, or \`"large"\` and apply it consistently.
+- \`"small"\` (24px) = data-dense tools. \`"medium"\` (32px) = default. \`"large"\` (40px) = comfortable/consumer-facing.
+
+### Motion & Animation
+- Always support \`prefers-reduced-motion: reduce\` \u2014 set transition durations to \u2264 0.01ms in that media query.
+- Micro-interactions (button press, tooltip): 150\u2013250ms. Panel transitions (drawer, sidebar): 300\u2013400ms.
+- Never animate layout properties that cause reflow (width, height, margin, padding). Animate transform and opacity instead.
+
+### Interaction Patterns
+- Never set \`outline: none\` globally. Keyboard focus indicators are required (WCAG 2.4.7).
+- Loading states: prefer Skeleton loader for content areas, overlay + ProgressBar for blocking operations, disabled button + inline spinner for async submission.
+- Error recovery: inline validation near the field for form errors; notification/toast for API/system errors.
+- Every icon-only button must have a visible tooltip and an \`aria-label\`.
+- Never show tooltips on disabled elements \u2014 disabled elements cannot receive focus.
+
+### Responsive Design
+- Breakpoints (defaults \u2014 use the project's breakpoint system if one is already established): Mobile < 640px | Tablet 640\u20131024px | Desktop 1024\u20131440px | Wide > 1440px.
+- Constrain max content width to 1440px with \`margin: 0 auto\` on wide viewports, unless a different maximum is already defined by the project.
+- On mobile (< 480px), data grids must switch to stacked/card layout \u2014 tabular layout is unusable at that width.
+- Schedulers/complex data views are not viable on mobile; provide a simplified alternative or a clear message.
+
+### UX Writing
+- Input labels describe *what* the field is. Placeholder text hints at *format or example* \u2014 never use placeholder as a substitute for a label.
+- Button labels must be specific action verbs: "Save Changes", "Delete Record", "Export CSV" \u2014 not "Submit", "OK", or "Yes".
+- Error messages must be specific and actionable: "Email address is already registered" not "Error 409".
+- Table/grid column headers: Title Case. Never ALL CAPS.
+- Empty states must explain why it's empty and offer a next action (e.g., "No records found. Add your first item.").
+
+### Data Presentation
+- Numeric and currency values must be right-aligned in table/grid columns.
+- Never display raw ISO 8601 date strings (e.g., \`2024-01-15T09:30:00Z\`) \u2014 always format for the locale (e.g., "15 Jan 2024").
+- Never render more than 200 rows in a fully-loaded table. Use pagination or virtual scrolling for larger datasets.
+- Never leave grid columns without explicit widths \u2014 causes layout jank on load and sort operations.
+
+### Chart Type Selection
+- **Line / Area**: continuous quantitative data over time (trends, rates).
+- **Bar (vertical)**: discrete time periods or ordered categories.
+- **Horizontal Bar**: comparing named categories (rankings, survey results).
+- **Donut (not Pie)**: part-to-whole proportions with \u2264 6 segments. Avoid Pie charts \u2014 the center hole of a Donut makes area estimation easier.
+- **Avoid**: 3D charts, dual-axis charts (misleading), charts with > 7 series in the same view.
+- Chart legend placement: below the chart.
+
+### Dialog vs Window Decisions
+- **Dialog (modal)**: use when the user must respond before continuing. Title should be action-oriented: "Delete this record?" not "Confirmation".
+- **Window (non-modal)**: use when content can exist alongside the background (resizable/draggable panels, editors).
+- Destructive dialog actions (delete, overwrite) must use the error theme color.
+- Every dialog must be closable via Escape key and have a clearly labeled close control.
+
+### Form Validation Display Rules
+- Show field-level validation errors **after the first blur** (not on initial render, not on every keystroke).
+- Display error text inline, directly below the field \u2014 never in a toast or far from the field.
+- On form-level submit failure, focus the first invalid field automatically.
+- Required fields: mark with an asterisk (*) and include a legend. Do not mark optional fields \u2014 label them "(optional)" only if most fields are required.
+
+### Grid Data Volume & Scrolling Strategy
+- Never render more than 200 rows without pagination or virtual scrolling.
+- Use **pagination** when users need to navigate by page number, see total row count, or perform export/select-all operations.
+- Use **virtual scrolling** when the dataset is very large (thousands of rows) and users scroll continuously rather than jumping to pages.
+- Default page size: 25 rows. Offer page size options (10, 25, 50) as defaults unless the project specifies otherwise.
+
+### Grid Feature Selection
+Enable only the Grid features genuinely required for the workflow. Each enabled feature adds UI chrome, event listeners, and DOM nodes. Start with the minimum set and add only when user stories require it:
+- \`sortable\` \u2014 when users need to find specific rows in non-obvious order
+- \`filterable\` \u2014 for datasets > 50 rows with varied values; skip for small fixed lists
+- \`groupable\` \u2014 only when hierarchical analysis is a core workflow
+- \`reorderable\` / \`resizable\` \u2014 when user customization of the view is a stated requirement
+- \`selectable\` \u2014 only when batch actions exist
+- \`editable\` \u2014 only when inline data entry is the primary workflow, not for read-only display
+
+### Form Layout Defaults
+These are defaults \u2014 respect the project's existing form conventions if established:
+- Prefer single-column form layout \u2014 easier to read and complete than multi-column.
+- Use two-column layout only for tightly related field pairs (First Name / Last Name, Start Date / End Date).
+- Align labels above their fields for complex forms; inline labels work only for very short forms (2\u20133 fields).
+- Place the primary action (Save / Submit) at the bottom left; Cancel or secondary actions to its right.
+
+### Whitespace Defaults
+When no design token system is defined by the project, apply these minimum spacing values:
+- Section separators: \u2265 24px vertical gap between distinct content areas.
+- Card internal padding: 16\u201324px.
+- Form field vertical gap: \u2265 16px between fields (24px for multi-column groups).
+- Page left/right margin: 24\u201332px minimum, even at desktop widths.`;var At=e=>`**Tool call example:**
 \`\`\`
-${ctx.layoutAssistantName}({
+${e.layoutAssistantName}({
     prompt="Provide Kendo Design System utility classes to make the following layout structure responsive across mobile, tablet, and desktop views: [LAYOUT DESCRIPTION HERE]",
     includeBuildingBlockExamples=false // Optional, include examples of Kendo building blocks (Grid, Flex, Stack, etc.)
 })
 \`\`\`
-`;
-var vanillaCSSResponsiveGuidance = `**General Responsive Design Guidance:**
+`,Ct=`**General Responsive Design Guidance:**
 - Use CSS media queries to apply different styles at various breakpoints (e.g., mobile, tablet, desktop).
 - Consider a mobile-first approach, starting with styles for smaller screens and adding complexity for larger screens.
 - Ensure flexible grid layouts that can adapt to different screen sizes.
 - Use relative units (%, em, rem) instead of fixed units (px) for widths and spacing to allow for better scalability.
-- Test the design across multiple devices and screen sizes to ensure a consistent user experience.`;
-var tailwindResponsiveGuidance = `**Tailwind CSS Responsive Design Guidance:**
+- Test the design across multiple devices and screen sizes to ensure a consistent user experience.`,St=`**Tailwind CSS Responsive Design Guidance:**
 - Use Tailwind's responsive utility variants (e.g., sm:, md:, lg:, xl:) to apply styles at specific breakpoints.
 - Start with mobile styles (no prefix) and layer on additional styles for larger screens using the appropriate prefixes.
 - Leverage Tailwind's grid and flex utilities to create flexible layouts that adapt to different screen sizes.
 - Use Tailwind's spacing utilities to maintain consistent spacing across breakpoints.
-- Test the design across multiple devices and screen sizes to ensure a consistent user experience.`;
-var renderOrchestratorResponse = (ctx, options) => {
-  const validationInstructions = renderValidatorResponse(
-    { suiteName: ctx.suiteName, libKey: ctx.libKey },
-    options.validationSteps
-  );
-  const includeLayout = ctx.includeLayout && ctx.layoutMode === "utils";
-  const dragDropGuidance = ctx.libKey === "angular" ? `- **Drag and Drop**: Consider using the DragandDrop and Sortable components when drag-and-drop functionality is needed.` : "";
-  const componentsList = ctx.components ? ctx.components.join(", ") : "components";
-  const responsiveLayoutHint = includeLayout ? `- And use the ${ctx.layoutAssistantName} tool to get Kendo CSS utility classes needed for responsive design.` : "";
-  const responsiveKDSGuidance = includeLayout ? responsiveKendoDesignSystemGuidance(ctx) : "";
-  const responsiveVanillaCSSGuidance = ctx.layoutMode === "vanilla" ? vanillaCSSResponsiveGuidance : "";
-  const responsiveTailwindCSSGuidance = ctx.layoutMode === "tailwind" ? tailwindResponsiveGuidance : "";
-  return `# \u{1F3AF} ${ctx.suiteName} - Execution Plan
+- Test the design across multiple devices and screen sizes to ensure a consistent user experience.`,U=(e,t)=>{let n=L({suiteName:e.suiteName,libKey:e.libKey},t.validationSteps),o=e.includeLayout&&e.layoutMode==="utils",s=e.libKey==="angular"?"- **Drag and Drop**: Consider using the DragandDrop and Sortable components when drag-and-drop functionality is needed.":"",i=e.components?e.components.join(", "):"components",r=o?`- And use the ${e.layoutAssistantName} tool to get Kendo CSS utility classes needed for responsive design.`:"",a=o?At(e):"",d=e.layoutMode==="vanilla"?Ct:"",p=e.layoutMode==="tailwind"?St:"";return`# \u{1F3AF} ${e.suiteName} - Execution Plan
 
 **Current Goal:**
 
-${ctx.userIntent}
+${e.userIntent}
 
 **Requirements Summary:**
-- **Framework:** ${ctx.libKey}
-${ctx.includeComponentsDocs ? `- **Component Library:** ${ctx.suiteName}
-    - Ensure to use ONLY ${ctx.suiteName} components for all UI elements.
-    - And use the ${ctx.codeAssistantName} tool to get ${ctx.suiteName} component documentation and code snippets.
-    - Ensure that after you read the plan you use exactly the ${ctx.codeAssistantName} no matter if there is another tool that can provide code snippets, documentation or other resources related to ${ctx.suiteName}.
-` : ""}${includeLayout ? `- **Layout:** Yes
-    - And use the ${ctx.layoutAssistantName} tool to get Kendo CSS utility classes needed for layout structure and responsive design.
-` : ""}${ctx.includeIcons ? `- **Icons:** Yes
+- **Framework:** ${e.libKey}
+${e.includeComponentsDocs?`- **Component Library:** ${e.suiteName}
+    - Ensure to use ONLY ${e.suiteName} components for all UI elements.
+    - And use the ${e.codeAssistantName} tool to get ${e.suiteName} component documentation and code snippets.
+    - Ensure that after you read the plan you use exactly the ${e.codeAssistantName} no matter if there is another tool that can provide code snippets, documentation or other resources related to ${e.suiteName}.
+`:""}${o?`- **Layout:** Yes
+    - And use the ${e.layoutAssistantName} tool to get Kendo CSS utility classes needed for layout structure and responsive design.
+`:""}${e.includeIcons?`- **Icons:** Yes
     - Use icons that align with the project theme and enhance usability.
-    - Use the ${ctx.iconAssistantName} tool to search for icons that fit the theme and purpose of your project.
-` : ""}${ctx.includeTheming ? `- **Custom Theming:**
+    - Use the ${e.iconAssistantName} tool to search for icons that fit the theme and purpose of your project.
+`:""}${e.includeTheming?`- **Custom Theming:**
     - Create a custom theme that aligns with the current goal and branding needs.
     - Use Kendo Themes and Design System guidelines.
     - Make sure to include strict CSS variables or theme requirements from the current goal.
-    - And use the ${ctx.styleAssistantName} tool to create a custom theme for your project.
-` : ""}${ctx.includeResponsive ? `- **Responsive:**
+    - And use the ${e.styleAssistantName} tool to create a custom theme for your project.
+`:""}${e.includeResponsive?`- **Responsive:**
     - Ensure the layout is fully responsive across mobile, tablet, and desktop views.
-    ${responsiveLayoutHint}
-` : ""}
+    ${r}
+`:""}
 - **Accessible (WCAG 2.2 Level AA):**
-    - CRITICAL: You must call the ${ctx.accessibilityAssistantName} tool with includeGeneralGuidelines=true on your first call to get WCAG 2.2 Level AA guidelines.
+    - CRITICAL: You must call the ${e.accessibilityAssistantName} tool with includeGeneralGuidelines=true on your first call to get WCAG 2.2 Level AA guidelines.
     - For subsequent calls, use includeGeneralGuidelines=false to get only component-specific accessibility information.
     - Ensure all components meet WCAG 2.2 Level AA standards.
 
-${includeLayout ? `**STYLING AND LAYOUT REQUIREMENTS:**
+${o?`**STYLING AND LAYOUT REQUIREMENTS:**
 **LAYOUT MODE: KENDO DESIGN SYSTEM CSS UTILITIES**
 ## CRITICAL DESIGN SYSTEM CONSTRAINTS
 - **USE ONLY KENDO DESIGN SYSTEM UTILITIES** for ALL styling, layout, spacing, positioning, and responsive behavior
 - Avoid custom CSS, inline styles, or other CSS framework classes
-- The ${ctx.layoutAssistantName} tool will provide the specific Kendo CSS utility classes needed
+- The ${e.layoutAssistantName} tool will provide the specific Kendo CSS utility classes needed
 - All layout requirements must use Kendo utilities exclusively
-` : ""}
-${ctx.layoutMode === "vanilla" ? `**STYLING AND LAYOUT REQUIREMENTS:**
+`:""}
+${e.layoutMode==="vanilla"?`**STYLING AND LAYOUT REQUIREMENTS:**
 **LAYOUT MODE: VANILLA**
 - In this mode, you should use Kendo UI components and vanilla CSS for layout and styling.
 - Do NOT use any utility-first CSS classes (e.g., from Tailwind) for layout or styling.
 - Focus on leveraging the built-in capabilities of Kendo UI components and writing custom CSS as needed to achieve the desired design and layout.
-` : ""}
-${ctx.layoutMode === "tailwind" ? `**STYLING AND LAYOUT REQUIREMENTS:**
+`:""}
+${e.layoutMode==="tailwind"?`**STYLING AND LAYOUT REQUIREMENTS:**
 **LAYOUT MODE: TAILWIND**
 - In this mode, you should use Tailwind CSS utility classes for layout and styling.
 - Do NOT write custom CSS or use vanilla CSS for layout or styling.
 - Focus on leveraging Tailwind's utility-first approach to achieve the desired design and layout, while still using Kendo UI components for functionality.
-` : ""}
-${ctx.includeFigmaD2C ? `**DESIGN EXTRACTION FROM FIGMA FILE**
-- You are given a Figma file URL that contains the design for the current goal. You MUST use the ${ctx.figmaD2CToolName} tool to extract design information from the Figma file.
-- Extracted design information should be used to get information about the layout, styles, design tokens and assets that can be used within the project.
-- The ${ctx.figmaD2CToolName} tool will output you Layout structure of the design, design tokens for CSS and any decoration and a snapshot of the design.
-` : ""}
+`:""}
+
+---
+
+${V()}
 
 ---
 
@@ -939,13 +232,13 @@ Follow these steps strictly in order to achieve a complete and polished implemen
 **MANDATORY REQUIREMENT:**
 
 - Before implementing any UI components or features, you must call the accessibility assistant with general guidelines
-- On your first call to "${ctx.accessibilityAssistantName}", set "includeGeneralGuidelines=true" to get foundational WCAG 2.2 Level AA best practices
+- On your first call to "${e.accessibilityAssistantName}", set "includeGeneralGuidelines=true" to get foundational WCAG 2.2 Level AA best practices
 - These general guidelines apply to all components and must be considered throughout implementation
 - For all subsequent calls, set "includeGeneralGuidelines=false" to get only component-specific information
 
 **First tool call (includes general WCAG guidelines):**
 \`\`\`
-${ctx.accessibilityAssistantName}({
+${e.accessibilityAssistantName}({
     query="What are the accessibility requirements for [COMPONENT_NAME]?",
     component="[COMPONENT_NAME]",
     includeGeneralGuidelines=true  // ONLY true on first call
@@ -954,11 +247,11 @@ ${ctx.accessibilityAssistantName}({
 
 **Step 2: Get Component-Specific Accessibility Information**
 
-For each additional ${ctx.suiteName} component you plan to use, call the tool with "includeGeneralGuidelines=false":
+For each additional ${e.suiteName} component you plan to use, call the tool with "includeGeneralGuidelines=false":
 
 **Tool call example:**
 \`\`\`
-${ctx.accessibilityAssistantName}({
+${e.accessibilityAssistantName}({
     query="What are the accessibility features and requirements for [COMPONENT_NAME]? Include ARIA attributes, keyboard navigation, and screen reader support.",
     component="[COMPONENT_NAME]",
     includeGeneralGuidelines=false  // false for all calls after the first
@@ -967,112 +260,14 @@ ${ctx.accessibilityAssistantName}({
 
 **Example:**
 \`\`\`
-${ctx.accessibilityAssistantName}({
+${e.accessibilityAssistantName}({
     query="How to associate the label with another component or HTML input?",
     component="Label",
     includeGeneralGuidelines=false
 })
 \`\`\`
 
-${ctx.includeFigmaD2C ? `### Phase: Design Extraction and Analysis
-
-**IMPORTANT DESIGN EXTRACTION REQUIRMENTS**
-- Use the ${ctx.figmaD2CToolName} tool to extract design information from the provided Figma file URL.
-- Analyze the extracted design information to identify key layout structures, components, styles, and design tokens.
-- Use the insights from the design analysis to inform your implementation in the next phases, ensuring alignment with the original design intent.
-- Follow ALL three extraction steps sequentially \u2014 each step is MANDATORY.
-- Complete the verification checklist after each step before proceeding to the next.
-
-
-**Step 1: Extract Base Design Information from Figma**
-- Extract only base the first layer of the design to get the overall structure and layout without going too deep into details. This will help you to understand the design hierarchy and identify key components and layout patterns.
-- Use the downloaded design snapshot to visually analyze the design and correlate it with the extracted structure. This will help you to identify which nodes correspond to which design elements and to plan your implementation accordingly.
-- **REQUIRED OUTPUT:** After extraction, you MUST output a structured list of ALL discovered node IDs with their labels/names before proceeding to Step 2. Format this as a clear inventory that will be referenced in subsequent steps. For each node, extract the node ID from the node-id attribute of the node XML tag.
-- **Depth escalation:** If a node at this depth shows it contains more children than can be captured (e.g., children are truncated), re-fetch that specific node with depth + 5 to ensure complete extraction.
-
-**Tool call example:**
-\`\`\`
-${ctx.figmaD2CToolName}({
-    url: [Figma URL from prompt]
-    depth: 10 // Consider more depth only if the user prompt explicitly states to extract deeply.
-})
-\`\`\`
-
-**Step 1 Completion Checklist (MUST satisfy before proceeding):**
-- [ ] Have I captured all top-level layout containers (headers, footers, main sections)?
-- [ ] Have I identified all major structural components?
-- [ ] Have I created and outputted a structured list of node IDs and their labels?
-- [ ] Have I visually analyzed the design snapshot to correlate nodes with design elements?
-
-**Step 2: Extract Main Nodes Design**
-- Based on the initial extraction and analysis, identify the main nodes that are critical for the design implementation. These could be reusable headers, body, navigation, sidebar or footer elements that illustrate the main structure.
-- Use the node IDs from the node-id attribute of the node XML tag to fetch these specific nodes with more depth to capture necessary details for implementation. This targeted extraction will help you to get the relevant design information without overwhelming the process with too much data.
-- **Depth escalation:** If any main node shows truncated children or contains more elements than expected at the given depth, immediately re-fetch with depth + 5.
-
-**Tool call example:**
-\`\`\`
-${ctx.figmaD2CToolName}({
-    fileKey: [The fileKey extracted from Step 1]
-    nodeIds: [Array of main node IDs identified from Step 1]
-    depth: 10 // Deeper extraction for main nodes to capture necessary details.
-})
-\`\`\`
-
-**Step 2 Completion Checklist (MUST satisfy before proceeding):**
-- [ ] Have I captured all interactive components (buttons, inputs, navigation elements)?
-- [ ] Have I identified all typography styles and text elements?
-- [ ] Have I extracted all color tokens and design system values?
-- [ ] Have I documented child node IDs that need deeper extraction in Step 3?
-
-**Step 3: Extract Child Node Details (MANDATORY)**
-**CRITICAL:** After Step 2, you MUST proceed to Step 3. Extract ALL child nodes identified in Step 2. Do not skip this step.
-
-- Extract all child nodes that were identified in Step 2 as requiring deeper analysis. These include specific components, styles, or interactions that are essential for accurate implementation.
-- Use the node IDs from the node-id attribute to fetch these specific child nodes with sufficient depth to capture all critical design details.
-- **Depth escalation:** If child nodes still show incomplete extraction (truncated elements, nested components not fully visible), re-fetch with depth + 5 until all leaf-level components are captured.
-
-**Tool call example:**
-\`\`\`
-${ctx.figmaD2CToolName}({
-    fileKey: [The fileKey extracted from Step 1]
-    nodeIds: [Array of ALL child node IDs identified from Step 2]
-    depth: 15 // Targeted deeper extraction for specific nodes. Increase if needed.
-})
-\`\`\`
-
-**Step 3 Completion Checklist (MUST satisfy before proceeding):**
-- [ ] Have I captured ALL leaf-level components (buttons, icons, form inputs)?
-- [ ] Have I extracted all spacing, padding, and margin values?
-- [ ] Have I identified all border styles, shadows, and visual effects?
-- [ ] Are there any remaining truncated nodes? (If yes, apply depth escalation)
-
-**Iterative Extraction and Stopping Condition**
-Continue iterating over the extraction process following these rules:
-- **Continue until:** (a) All leaf-level components have been captured with complete details, OR (b) You have completed 3 extraction passes \u2014 whichever comes first.
-- After each iteration, verify that no new child nodes require deeper extraction.
-- If depth escalation is needed after 3 passes, document the limitation and proceed with available data.
-
-**MANDATORY: Design Extraction Verification (Complete BEFORE Code Generation Phase)**
-Before proceeding to any code generation or implementation phase, you MUST produce and output a verification summary containing:
-
-1. **Component Inventory:** List all UI components discovered (buttons, inputs, cards, navigation elements, etc.)
-2. **Hierarchy Map:** Show the parent-child relationships of major layout sections
-3. **Design Tokens Identified:**
-   - Colors (with hex/rgba values)
-   - Typography (font families, sizes, weights)
-   - Spacing values (margins, paddings, gaps)
-   - Border styles and effects
-4. **Gaps and Limitations:** Explicitly state any design elements that could not be fully extracted
-
-**This verification summary serves as the design specification for implementation. Do not proceed to Code Generation until this summary is complete.**
-
-**Additional Extraction During Implementation:**
-- During the implementation phase (Code Generation), you can and should use the ${ctx.figmaD2CToolName} tool with the relevant node IDs from the node-id attributes again if you discover you need more specific design details for certain components or sections that were not captured in earlier phases.
-- If additional extraction is needed, apply the same depth escalation logic and verification steps.
-` : ""}
-
-
-${includeLayout ? `
+${o?`
 ### Phase: Layout Foundation
 
 **Step 1: Create Base Layout Structure**
@@ -1083,16 +278,16 @@ ${includeLayout ? `
 
 **Tool call example:**
 \`\`\`
-${ctx.layoutAssistantName}({
+${e.layoutAssistantName}({
     prompt="Provide Kendo Design System utility classes for the following layout structure: [LAYOUT DESCRIPTION HERE]",
     includeBuildingBlockExamples=true // Optional, include examples of Kendo building blocks (Grid, Flex, Stack, etc.)
 })
 \`\`\`
-` : ""}
-${ctx.includeComponentsDocs ? `
+`:""}
+${e.includeComponentsDocs?`
 ### Phase: Component Integration
 **Step 1: Identify and Implement Core Components**
-Based on your current goal, analyze what other ${ctx.suiteName} components are needed and implement them one by one. Here you are some appropriate components based on the different project type:
+Based on your current goal, analyze what other ${e.suiteName} components are needed and implement them one by one. Here you are some appropriate components based on the different project type:
 
 **Component Selection Guidelines:**
 - **Landing Pages**: Consider Button, Card, Form components, Layout containers, Navigation elements
@@ -1100,17 +295,17 @@ Based on your current goal, analyze what other ${ctx.suiteName} components are n
 - **Data Entry**: Consider Form, TextBox, DatePicker, DropDownList, Upload, Validation components
 - **Content Management**: Consider Grid, Editor, TreeView, FileManager, Dialog components
 - **E-commerce**: Consider ListView, Card, Button, Rating, Badge, Carousel components
-${dragDropGuidance}
+${s}
 
 **IMPORTANT COMPONENT USAGE REQUIREMENTS:**
-- Make sure to identify all necessary features related to the ${componentsList} based on the current goal.
-- Make sure to identify specific features needed for other ${ctx.suiteName} components based on the current goal.
-- Make sure to generate a query for ${ctx.codeAssistantName} tool for each component and call the tool for each specific feature or functionality.
+- Make sure to identify all necessary features related to the ${i} based on the current goal.
+- Make sure to identify specific features needed for other ${e.suiteName} components based on the current goal.
+- Make sure to generate a query for ${e.codeAssistantName} tool for each component and call the tool for each specific feature or functionality.
 - Always specify the exact features you want for each component. Describe only the needed functionality, and behavior you need. Be concise and don't include any information about the use case.
 
 **Tool call examples:**
     \`\`\`
-    ${ctx.codeAssistantName}({
+    ${e.codeAssistantName}({
             query="Give me information about [COMPONENT_NAME] with [SPECIFIC_FEATURES]." <!-- For example: 'Grid with paging' or 'Button with click events' or 'Chart with multiple series' -->
             component="[COMPONENT_NAME]" <!-- For example: 'Grid', 'Button', 'Chart', etc. -->
     })
@@ -1118,33 +313,33 @@ ${dragDropGuidance}
 
 For broad queries, break them down into specific features (e.g., paging, sorting, filtering for Grid) and call the tool separately for each feature:
     \`\`\`
-    ${ctx.codeAssistantName}({
+    ${e.codeAssistantName}({
             query="How to implement [SPECIFIC_FEATURE] in [COMPONENT_NAME]?" <!-- For example: 'paging in Grid' -->
             component="[COMPONENT_NAME]" <!-- For example: 'Grid', 'Button', etc. -->
     })
     \`\`\`
 
     \`\`\`
-    ${ctx.codeAssistantName}({
+    ${e.codeAssistantName}({
             query="How to implement [SPECIFIC_FEATURE] in [COMPONENT_NAME]?" <!-- For example: 'sorting in Grid' -->
             component="[COMPONENT_NAME]" <!-- For example: 'Grid', 'Button', etc. -->
     })
     \`\`\`
 
     \`\`\`
-    ${ctx.codeAssistantName}({
+    ${e.codeAssistantName}({
             query="How to implement [SPECIFIC_FEATURE] in [COMPONENT_NAME]?" <!-- For example: 'filtering in Grid' -->
             component="[COMPONENT_NAME]" <!-- For example: 'Grid', 'Button', etc. -->
     })
     \`\`\`
-` : ""}
-${ctx.includeResponsive ? `
+`:""}
+${e.includeResponsive?`
 ### Phase: Layout Responsive Finalization
 
 **Step 1: Implement Responsive Behavior**
-${responsiveKDSGuidance}${responsiveVanillaCSSGuidance}${responsiveTailwindCSSGuidance}` : ""}
+${a}${d}${p}`:""}
 
-${ctx.includeTheming ? `
+${e.includeTheming?`
 **Step 2: Custom Theme Implementation**
 
 **CUSTOM THEME REQUIREMENTS:**
@@ -1154,13 +349,13 @@ ${ctx.includeTheming ? `
 
 **Tool call example:**
 \`\`\`
-${ctx.styleAssistantName}({
+${e.styleAssistantName}({
     query="Create a custom Kendo UI theme that aligns with the following current goal and branding needs: [CURRENT GOAL HERE]. Include strict CSS variables or theme requirements as needed.",
     includeThemeVariables=true // Optional, include specific CSS variables for colors, typography, spacing, etc.
 })
 \`\`\`
-` : ""}
-${ctx.includeIcons ? `
+`:""}
+${e.includeIcons?`
 **Step 3: Iconography and Visual Enhancements**
 
 **ICONOGRAPHY GUIDELINES:**
@@ -1170,64 +365,61 @@ ${ctx.includeIcons ? `
 
 **Tool call example:**
 \`\`\`
-${ctx.iconAssistantName}({
+${e.iconAssistantName}({
     query="Suggest icons that fit the theme and purpose of the following current goal: [CURRENT GOAL HERE]. Provide icon names and usage context.",
 })
 \`\`\`
-` : ""}
+`:""}
 ### Phase: Code Generation
 **IMPORTANT:** Do NOT generate ANY code or create files until ALL information gathering phases (1-3) are complete.
 **Step 1: Generate Complete Implementation**
-After completing all information gathering phases above, generate the complete ${ctx.libKey} component/page implementation:
+After completing all information gathering phases above, generate the complete ${e.libKey} component/page implementation:
 **Code Generation Requirements:**
-- Create complete, functional ${ctx.libKey} components/pages
-- Include all identified ${ctx.suiteName} components with their configurations
+- Create complete, functional ${e.libKey} components/pages
+- Include all identified ${e.suiteName} components with their configurations
 - Apply ALL Kendo Design System utility classes gathered from layout assistant
 - Implement proper component event handling and data binding
 - Ensure responsive behavior using Kendo utility classes
 - Include necessary import statements and dependencies
 
-${options.injectedPlan ?? ""}
+${t.injectedPlan??""}
 
 ### Phase: Validation and Finalization
 
 **Step 1: Code Validation**
 ** CRITICAL REQUIREMENT: You MUST validate the generated UI code using this comprehensive checklist to ensure code quality and compliance:**
 
-${validationInstructions}
+${n}
 
 **Step 2: Final Review and Testing**
 ** Implementation Validation:**
-${ctx.includeComponentsDocs ? ` - Components render correctly without errors
-- All ${ctx.suiteName} component features function as expected
-- Event handling and data binding operate correctly` : ""}
-${ctx.includeResponsive ? `- Responsive layout works across breakpoints` : ""}
+${e.includeComponentsDocs?` - Components render correctly without errors
+- Running \`npm run build\` compiles the application successfully without any build errors or crashes.
+- All ${e.suiteName} component features function as expected
+- Event handling and data binding operate correctly`:""}
+${e.includeResponsive?"- Responsive layout works across breakpoints":""}
 
 **Quick Fixes (if needed):**
 
 After code implementation and validation you can make quick fixes as needed:
-- Use ${ctx.codeAssistantName} for component-specific issues
-- Use ${ctx.layoutAssistantName} for styling adjustments
+- If any build errors are found, fix them and re-run the application.
+- Use ${e.codeAssistantName} for component-specific issues
+- Use ${e.layoutAssistantName} for styling adjustments
 
 +### Before You Begin
-- When following/executing the plan call tools are defined from the same function_ecosystem/MCP_server which ${ctx.name} was called.
+- When following/executing the plan call tools are defined from the same function_ecosystem/MCP_server which ${e.name} was called.
 - Do NOT generate or suggest any code until all tools have been used and validated responses are incorporated.
 - Focus on planning and sequencing.
 - Summarize the components, layouts, and utilities gathered.
-- Confirm all required inputs from tools have been provided.`;
-};
-
-// packages/kendo-ui-agent/src/lib/templates/assistant-orchestrator.ts
-var renderAssistantOrchestratorResponse = (ctx) => {
-  return `# ${ctx.suiteName} Assistant
+- Confirm all required inputs from tools have been provided.`};var H=e=>`# ${e.suiteName} Assistant
 
 **What you're looking for:**
 
-${ctx.userIntent}
+${e.userIntent}
 
 **Available Tools:**
-- **${ctx.codeAssistantName}** - Get component documentation, features, and usage examples
-- **${ctx.iconAssistantName}** - Search for icons from the Kendo icon library
+- **${e.codeAssistantName}** - Get component documentation, features, and usage examples
+- **${e.iconAssistantName}** - Search for icons from the Kendo icon library
 
 ---
 
@@ -1237,7 +429,7 @@ Follow these steps to find the right components and resources:
 
 ### Step 1: Identify Components
 
-Based on your needs, consider these ${ctx.suiteName} component categories:
+Based on your needs, consider these ${e.suiteName} component categories:
 
 **Common Use Cases:**
 - **Data Display**: Grid, ListView, TreeView, Card, TileLayout
@@ -1250,10 +442,10 @@ Based on your needs, consider these ${ctx.suiteName} component categories:
 
 **How to explore components:**
 
-Use the ${ctx.codeAssistantName} tool to learn about specific components:
+Use the ${e.codeAssistantName} tool to learn about specific components:
 
 \`\`\`
-${ctx.codeAssistantName}({
+${e.codeAssistantName}({
     query: "What are the main features of [COMPONENT_NAME]?",
     component: "[COMPONENT_NAME]"
 })
@@ -1261,14 +453,14 @@ ${ctx.codeAssistantName}({
 
 **Examples:**
 \`\`\`
-${ctx.codeAssistantName}({
+${e.codeAssistantName}({
     query: "How to use Grid with paging and sorting?",
     component: "Grid"
 })
 \`\`\`
 
 \`\`\`
-${ctx.codeAssistantName}({
+${e.codeAssistantName}({
     query: "What features does DatePicker have?",
     component: "DatePicker"
 })
@@ -1279,37 +471,37 @@ ${ctx.codeAssistantName}({
 - Break complex queries into multiple calls focusing on one feature at a time
 - Specify the exact component name in the component parameter
 
-${ctx.includeIcons ? `
+${e.includeIcons?`
 ### Step 2: Find Icons
 
-Use the ${ctx.iconAssistantName} tool to search for icons:
+Use the ${e.iconAssistantName} tool to search for icons:
 
 \`\`\`
-${ctx.iconAssistantName}({
+${e.iconAssistantName}({
     query: "Search for icons related to [YOUR THEME/PURPOSE]"
 })
 \`\`\`
 
 **Examples:**
 \`\`\`
-${ctx.iconAssistantName}({
+${e.iconAssistantName}({
     query: "icons for navigation menu"
 })
 \`\`\`
 
 \`\`\`
-${ctx.iconAssistantName}({
+${e.iconAssistantName}({
     query: "icons for user actions like edit, delete, save"
 })
 \`\`\`
-` : ""}
+`:""}
 
 ### Step 3: Review and Implement
 
 After gathering information:
-1. Review the component documentation provided by ${ctx.codeAssistantName}
-2. Check which icons are available from ${ctx.iconAssistantName}
-3. Use the official ${ctx.suiteName} documentation for detailed implementation guides
+1. Review the component documentation provided by ${e.codeAssistantName}
+2. Check which icons are available from ${e.iconAssistantName}
+3. Use the official ${e.suiteName} documentation for detailed implementation guides
 4. Refer to the component examples and code snippets provided
 
 ---
@@ -1317,44 +509,33 @@ After gathering information:
 ## Getting Started
 
 **Next Actions:**
-1. Start by calling ${ctx.codeAssistantName} for the components you need
-2. ${ctx.includeIcons ? `Search for icons using ${ctx.iconAssistantName}` : "Review the component documentation"}
-3. Follow the ${ctx.suiteName} official documentation for implementation details
+1. Start by calling ${e.codeAssistantName} for the components you need
+2. ${e.includeIcons?`Search for icons using ${e.iconAssistantName}`:"Review the component documentation"}
+3. Follow the ${e.suiteName} official documentation for implementation details
 
 **Important Notes:**
 - These tools provide documentation and guidance, not code generation
-- Always refer to official ${ctx.suiteName} documentation for the most up-to-date information
-- Tool responses include usage examples and best practices`;
-};
-
-// packages/kendo-ui-agent/src/lib/templates/shared-validation.ts
-var getSharedValidationSteps = (uiLibrary, designSystem) => ({
-  SETUP_VALIDATION: `
+- Always refer to official ${e.suiteName} documentation for the most up-to-date information
+- Tool responses include usage examples and best practices`;var E=(e,t)=>({SETUP_VALIDATION:`
  UI Library Setup:
-- ${uiLibrary} modules properly imported and configured
-- ${uiLibrary} theme properly loaded and applied
-- ${uiLibrary} license properly configured
-- Globalization and localization properly configured for ${uiLibrary} components
-- Required ${uiLibrary} dependencies installed and up-to-date`,
-  PERFORMANCE_OPTIMIZATION: `
+- ${e} modules properly imported and configured
+- ${e} theme properly loaded and applied
+- ${e} license properly configured
+- Globalization and localization properly configured for ${e} components
+- Required ${e} dependencies installed and up-to-date`,PERFORMANCE_OPTIMIZATION:`
  Performance Optimization:
 - Efficient rendering patterns to prevent unnecessary re-renders
-- Lazy loading of ${uiLibrary} components when appropriate
-- Virtualization enabled for large datasets in ${uiLibrary} components
-- Only required ${uiLibrary} modules imported and tree-shaken`,
-  THEME_AND_STYLING: `
- ${uiLibrary} Theme & Styling:
-- Prioritize the ${designSystem} Design System utilities
+- Lazy loading of ${e} components when appropriate
+- Virtualization enabled for large datasets in ${e} components
+- Only required ${e} modules imported and tree-shaken`,THEME_AND_STYLING:`
+ ${e} Theme & Styling:
+- Prioritize the ${t} Design System utilities
 - Avoid custom CSS or other framework classes
 - Do not use inline styles
-- Consistent ${uiLibrary} theme application across all components
+- Consistent ${e} theme application across all components
 - Custom theme variables properly defined and scoped
-- ${uiLibrary} icon fonts properly loaded and optimized
-- Brand colors integrated with ${uiLibrary} component themes`
-});
-
-// packages/kendo-ui-agent/src/lib/templates/tailwind-bridge.ts
-var kendoTokenList = `--kendo-color-app-surface
+- ${e} icon fonts properly loaded and optimized
+- Brand colors integrated with ${e} component themes`});var wt=`--kendo-color-app-surface
 --kendo-color-on-app-surface
 --kendo-color-subtle
 --kendo-color-surface
@@ -1540,8 +721,7 @@ var kendoTokenList = `--kendo-color-app-surface
 --kendo-border-radius-xxl
 --kendo-border-radius-xxxl
 --radius-4xl: 1.5rem
---kendo-border-radius-full`;
-var tailwindV3SetupPrompt = `I need you to set up a system where Tailwind CSS is the single source of truth for all design tokens, and those tokens are automatically reflected as CSS custom properties so I can use them in regular CSS too.
+--kendo-border-radius-full`,ve=`I need you to set up a system where Tailwind CSS is the single source of truth for all design tokens, and those tokens are automatically reflected as CSS custom properties so I can use them in regular CSS too.
 Requirements:
 
 All design tokens (colors, spacing, font families, border radius, shadows) are defined once in tailwind.config.js
@@ -1556,8 +736,7 @@ Output I need:
 
 The full tailwind.config.js with the plugin included
 The base CSS file importing Tailwind
-A short example showing a component using both bg-primary and var(--color-primary) side by side`;
-var tailwindV4SetupPrompt = `I need you to set up a system where Tailwind CSS v4 is the single source of truth for all design tokens, and those tokens are automatically available as CSS custom properties so I can use them in regular CSS too.
+A short example showing a component using both bg-primary and var(--color-primary) side by side`,ke=`I need you to set up a system where Tailwind CSS v4 is the single source of truth for all design tokens, and those tokens are automatically available as CSS custom properties so I can use them in regular CSS too.
 Requirements:
 
 All design tokens (colors, spacing, font families, border radius, shadows) are defined once in the @theme block \u2014 no tailwind.config.js
@@ -1571,1271 +750,144 @@ Use the Kendo theme tokens listed above as the design tokens.
 Output I need:
 
 The single CSS file with @import "tailwindcss", the @theme block, and the .dark overrides
-A short example showing a component using both bg-primary and var(--color-primary) side by side`;
-var tailwindBridgeExample = `## Tailwind CSS Setup Instructions
+A short example showing a component using both bg-primary and var(--color-primary) side by side`,z=`## Tailwind CSS Setup Instructions
 
 Detect which version of Tailwind CSS the project uses, then follow the appropriate setup guide below.
 
 ### Kendo Theme Tokens
 These are the design tokens to map into Tailwind:
-${kendoTokenList}
+${wt}
 
 ### For Tailwind CSS v3 (uses tailwind.config.js)
 
 <tailwind_v3_setup>
-${tailwindV3SetupPrompt}
+${ve}
 </tailwind_v3_setup>
 
 ### For Tailwind CSS v4 (uses @theme block, no config file)
 
 <tailwind_v4_setup>
-${tailwindV4SetupPrompt}
+${ke}
 </tailwind_v4_setup>
 
-IMPORTANT: Detect which version of Tailwind CSS the project uses, then follow the matching setup guide.`;
-
-// packages/kendo-ui-agent/src/lib/tools-factory.ts
-function formatApiRefItemFromJson(rawValue, component) {
-  let data;
-  try {
-    data = JSON.parse(rawValue);
-  } catch {
-    return rawValue;
-  }
-  const item = data?.Item;
-  if (!item) {
-    return rawValue;
-  }
-  const sectionParts = [];
-  const name = item.FullName ?? item.Name ?? "";
-  const type = item.Type ?? "";
-  const summary = item.Summary ?? "";
-  const syntax = item.SyntaxContent ?? "";
-  sectionParts.push(
-    `## API Reference Item
-- Name: ${name}
-- Type: ${type}
-- Summary: ${summary}
-- Syntax: ${syntax}`
-  );
-  const returnTypeItems = data.RelatedItemsByType?.["return_type"];
-  if (returnTypeItems?.length) {
-    const returnType = returnTypeItems[0].Text;
-    if (returnType) {
-      sectionParts.push(`- Return Type: ${returnType}`);
-    }
-  }
-  const examples = item.Examples ?? [];
-  if (examples.length > 0) {
-    let exampleSection = "## Examples\n";
-    let exampleIndex = 0;
-    for (const example of examples) {
-      const exComponent = (example.Component ?? "").toLowerCase();
-      const compLower = component.toLowerCase();
-      if (exComponent && exComponent !== compLower && exComponent !== "general") {
-        continue;
-      }
-      exampleIndex += 1;
-      const code = example.Code ?? "";
-      exampleSection += `### Example ${exampleIndex}
+IMPORTANT: Detect which version of Tailwind CSS the project uses, then follow the matching setup guide.`;function Tt(e,t){let n;try{n=JSON.parse(e)}catch{return e}let o=n?.Item;if(!o)return e;let s=[],i=o.FullName??o.Name??"",r=o.Type??"",a=o.Summary??"",d=o.SyntaxContent??"";s.push(`## API Reference Item
+- Name: ${i}
+- Type: ${r}
+- Summary: ${a}
+- Syntax: ${d}`);let p=n.RelatedItemsByType?.return_type;if(p?.length){let u=p[0].Text;u&&s.push(`- Return Type: ${u}`)}let b=o.Examples??[];if(b.length>0){let u=`## Examples
+`,l=0;for(let y of b){let A=(y.Component??"").toLowerCase(),C=t.toLowerCase();if(A&&A!==C&&A!=="general")continue;l+=1;let w=y.Code??"";u+=`### Example ${l}
 \`\`\`
-${code}
+${w}
 \`\`\`
-`;
-    }
-    if (exampleIndex > 0) {
-      sectionParts.push(exampleSection);
-    }
-  }
-  const related = data.RelatedItemsByType ?? {};
-  const additionalContextItems = [];
-  for (const [relationType, relatedItems] of Object.entries(related)) {
-    if (relationType === "return_type" || relationType === "render_fragment") {
-      continue;
-    }
-    for (const relatedItem of relatedItems ?? []) {
-      const fullName = relatedItem.FullName ?? "";
-      const shortText = relatedItem.ShortText ?? "";
-      additionalContextItems.push(`### ${fullName} (${relationType})
-${shortText}`);
-    }
-  }
-  if (additionalContextItems.length > 0) {
-    sectionParts.push("## Additional Context\n" + additionalContextItems.join("\n---\n"));
-  }
-  return sectionParts.join("\n\n");
-}
-var LAYOUT_MODE = process.env.KENDO_UIA_LAYOUT_MODE || "utils";
-function createOrchestratorTool(config, templateOptions, contextApi2) {
-  const {
-    name,
-    title,
-    description,
-    layoutAssistantName: layoutAssistantName2,
-    codeAssistantName: codeAssistantName2,
-    styleAssistantName: styleAssistantName2,
-    iconAssistantName: iconAssistantName2,
-    accessibilityAssistantName: accessibilityAssistantName2,
-    figmaD2CToolName: figmaD2CToolName2,
-    suiteName,
-    libKey,
-    components
-  } = config;
-  const tool = new UIAgentTool(
-    name,
-    {
-      title,
-      description,
-      requiredAccess: config.requiredAccess,
-      inputSchema: {
-        userIntent: z4.string().describe(
-          `Detailed description and intent of what the user wants to build. Include the type of page/component, main functionality, visual requirements, and any specific ${suiteName} components you want to use.`
-        ),
-        needsComponentsDocsConfidence: z4.number().min(0).max(1).default(1).describe(
-          "Confidence (0-1) to include Component Documentation assistance. Default is 1."
-        ),
-        needsLayoutConfidence: z4.number().min(0).max(1).default(0).describe(
-          "Confidence (0-1) to include Layout assistance. Default is 0."
-        ),
-        needsStylingConfidence: z4.number().min(0).max(1).default(0).describe(
-          "Confidence (0-1) to include Theming/Styling assistance. Default is 0."
-        ),
-        needsResponsiveBehaviorConfidence: z4.number().min(0).max(1).default(0).describe(
-          "Confidence (0-1) to include Responsive Behavior assistance. Default is 0."
-        ),
-        needsIconsConfidence: z4.number().min(0).max(1).default(0).describe(
-          "Confidence (0-1) to include Icons assistance. Default is 0."
-        ),
-        needsFigmaD2CConfidence: z4.boolean().describe("Whether to include Figma D2C assistance. If the prompt includes a Figma URL always make sure to set to true.").default(false),
-        componentsNeeded: z4.array(z4.enum(components)).optional().describe(
-          `Optional list of specific ${suiteName} components needed for the project.`
-        )
-      }
-    },
-    async ({
-      userIntent,
-      needsComponentsDocsConfidence,
-      needsLayoutConfidence,
-      needsStylingConfidence,
-      needsResponsiveBehaviorConfidence,
-      needsIconsConfidence,
-      needsFigmaD2CConfidence,
-      componentsNeeded
-    }, { _meta }) => {
-      log("UI Orchestrator called with:", {
-        userIntent,
-        needsComponentsDocsConfidence,
-        needsLayoutConfidence,
-        needsStylingConfidence,
-        needsResponsiveBehaviorConfidence,
-        needsIconsConfidence
-      });
-      try {
-        await contextApi2.recordOrchestratorUserRequest({
-          meta: {
-            userIntent,
-            componentsNeeded,
-            _meta
-          }
-        });
-      } catch (error) {
-        throw getGrpcError(error);
-      }
-      const clientCapabilities = tool.server?.server.getClientCapabilities?.();
-      const supportsElicitation = clientCapabilities?.elicitation;
-      let forceIncludeCustomTheming;
-      if (supportsElicitation && needsStylingConfidence > 0.3 && needsStylingConfidence <= 0.6) {
-        const result = await tool.server?.server.elicitInput({
-          message: "I was unable to determine if you need custom Kendo Theme assistant. Can you please confirm?",
-          requestedSchema: {
-            type: "object",
-            properties: {
-              includeCustomTheming: {
-                type: "boolean",
-                description: "Whether to include Custom Theming assistance in the workflow."
-              }
-            },
-            required: ["includeCustomTheming"]
-          }
-        });
-        if (result?.action === "accept" && result.content?.includeCustomTheming) {
-          forceIncludeCustomTheming = true;
-        }
-      }
-      const response = renderOrchestratorResponse(
-        {
-          name,
-          userIntent,
-          includeComponentsDocs: needsComponentsDocsConfidence > 0.3,
-          includeTheming: needsStylingConfidence > 0.6 || !!forceIncludeCustomTheming,
-          includeLayout: needsLayoutConfidence > 0.5,
-          includeIcons: needsIconsConfidence > 0.6,
-          includeResponsive: needsLayoutConfidence > 0.5 && needsResponsiveBehaviorConfidence > 0.4,
-          includeFigmaD2C: needsFigmaD2CConfidence,
-          layoutAssistantName: layoutAssistantName2,
-          codeAssistantName: codeAssistantName2,
-          styleAssistantName: styleAssistantName2,
-          iconAssistantName: iconAssistantName2,
-          accessibilityAssistantName: accessibilityAssistantName2,
-          figmaD2CToolName: figmaD2CToolName2,
-          suiteName,
-          libKey,
-          layoutMode: LAYOUT_MODE,
-          components: componentsNeeded
-        },
-        templateOptions
-      );
-      return {
-        content: [
-          {
-            type: "text",
-            text: response
-          }
-        ]
-      };
-    }
-  );
-  return tool;
-}
-function createAssistantOrchestratorTool(config, contextApi2) {
-  const {
-    name,
-    title,
-    description,
-    iconAssistantName: iconAssistantName2,
-    codeAssistantName: codeAssistantName2,
-    suiteName,
-    libKey,
-    components
-  } = config;
-  const tool = new UIAgentTool(
-    name,
-    {
-      title,
-      description,
-      inputSchema: {
-        userIntent: z4.string().describe(
-          `Describe what you want to build or what components you're looking for. Include the type of functionality, features, or UI elements you need from ${suiteName}.`
-        ),
-        needsIconsConfidence: z4.number().min(0).max(1).default(0.7).describe(
-          "Confidence (0-1) to include Icons assistance. Default is 0.7."
-        ),
-        componentsNeeded: z4.array(z4.enum(components)).optional().describe(
-          `Optional list of specific ${suiteName} components you want to learn about.`
-        )
-      },
-      requiredAccess: config.requiredAccess
-    },
-    async ({
-      userIntent,
-      needsIconsConfidence,
-      componentsNeeded
-    }, { _meta }) => {
-      log("Assistant Orchestrator called with:", {
-        userIntent,
-        needsIconsConfidence,
-        componentsNeeded
-      });
-      try {
-        await contextApi2.recordOrchestratorUserRequest({
-          meta: {
-            userIntent,
-            componentsNeeded,
-            _meta
-          }
-        });
-      } catch (error) {
-        throw getGrpcError(error);
-      }
-      const response = renderAssistantOrchestratorResponse({
-        name,
-        userIntent,
-        includeComponentsDocs: true,
-        // Always true for assistant mode
-        includeIcons: needsIconsConfidence > 0.5,
-        codeAssistantName: codeAssistantName2,
-        iconAssistantName: iconAssistantName2,
-        suiteName,
-        libKey,
-        components: componentsNeeded
-      });
-      return {
-        content: [
-          {
-            type: "text",
-            text: response
-          }
-        ]
-      };
-    }
-  );
-  return tool;
-}
-function createLayoutAssistantTool(config, contextApi2) {
-  const {
-    name,
-    title,
-    description,
-    suiteName: _suiteName,
-    libKey,
-    getPreContent
-  } = config;
-  return new UIAgentTool(
-    name,
-    {
-      title,
-      description,
-      requiredAccess: LAYOUT_MODE === "utils" ? config.requiredAccess : ["none"],
-      inputSchema: {
-        prompt: z4.string().describe(
-          `An enhanced prompt describing the HTML layout structure, design requirements or specific visual effects you want to achieve.`
-        ),
-        includeBuildingBlockExamples: z4.boolean().describe(
-          "Whether to include building block examples. Defaults to false."
-        ).default(false)
-      }
-    },
-    async ({ prompt, includeBuildingBlockExamples }, { _meta }) => {
-      log("Layout Assistant called with:", {
-        prompt,
-        includeBuildingBlockExamples
-      });
-      try {
-        const cssResponse = await contextApi2.queryCssUtils({ query: prompt }, { _meta });
-        let finalMarkdown = cssResponse.values.join("\n") || "No CSS utilities found for the given prompt.";
-        const preContent = getPreContent?.() ?? "";
-        const buildLayout = (buildingBlockMd) => {
-          return `${preContent}
+`}l>0&&s.push(u)}let g=n.RelatedItemsByType??{},f=[];for(let[u,l]of Object.entries(g))if(!(u==="return_type"||u==="render_fragment"))for(let y of l??[]){let A=y.FullName??"",C=y.ShortText??"";f.push(`### ${A} (${u})
+${C}`)}return f.length>0&&s.push(`## Additional Context
+`+f.join(`
+---
+`)),s.join(`
+
+`)}var W=process.env.KENDO_UIA_LAYOUT_MODE||"utils";function Ae(e,t,n){let{name:o,title:s,description:i,layoutAssistantName:r,codeAssistantName:a,styleAssistantName:d,iconAssistantName:p,accessibilityAssistantName:b,suiteName:g,libKey:f,components:u}=e,l=new S(o,{title:s,description:i,requiredAccess:e.requiredAccess,inputSchema:{userIntent:v.string().describe(`Detailed description and intent of what the user wants to build. Include the type of page/component, main functionality, visual requirements, and any specific ${g} components you want to use.`),needsComponentsDocsConfidence:v.number().min(0).max(1).default(1).describe("Confidence (0-1) to include Component Documentation assistance. Default is 1."),needsLayoutConfidence:v.number().min(0).max(1).default(0).describe("Confidence (0-1) to include Layout assistance. Default is 0."),needsStylingConfidence:v.number().min(0).max(1).default(0).describe("Confidence (0-1) to include Theming/Styling assistance. Default is 0."),needsResponsiveBehaviorConfidence:v.number().min(0).max(1).default(0).describe("Confidence (0-1) to include Responsive Behavior assistance. Default is 0."),needsIconsConfidence:v.number().min(0).max(1).default(0).describe("Confidence (0-1) to include Icons assistance. Default is 0."),componentsNeeded:v.array(v.enum(u)).optional().describe(`Optional list of specific ${g} components needed for the project.`)}},async({userIntent:y,needsComponentsDocsConfidence:A,needsLayoutConfidence:C,needsStylingConfidence:w,needsResponsiveBehaviorConfidence:I,needsIconsConfidence:se,componentsNeeded:re},{_meta:st})=>{h("UI Orchestrator called with:",{userIntent:y,needsComponentsDocsConfidence:A,needsLayoutConfidence:C,needsStylingConfidence:w,needsResponsiveBehaviorConfidence:I,needsIconsConfidence:se});try{await n.recordOrchestratorUserRequest({meta:{userIntent:y,componentsNeeded:re,_meta:st}})}catch(_){throw R(_)}let rt=l.server?.server.getClientCapabilities?.()?.elicitation,ie;if(rt&&w>.3&&w<=.6){let _=await l.server?.server.elicitInput({message:"I was unable to determine if you need custom Kendo Theme assistant. Can you please confirm?",requestedSchema:{type:"object",properties:{includeCustomTheming:{type:"boolean",description:"Whether to include Custom Theming assistance in the workflow."}},required:["includeCustomTheming"]}});_?.action==="accept"&&_.content?.includeCustomTheming&&(ie=!0)}return{content:[{type:"text",text:U({name:o,userIntent:y,includeComponentsDocs:A>.3,includeTheming:w>.6||!!ie,includeLayout:C>.5,includeIcons:se>.6,includeResponsive:C>.5&&I>.4,layoutAssistantName:r,codeAssistantName:a,styleAssistantName:d,iconAssistantName:p,accessibilityAssistantName:b,suiteName:g,libKey:f,layoutMode:W,components:re},t)}]}});return l}function Ce(e,t){let{name:n,title:o,description:s,iconAssistantName:i,codeAssistantName:r,suiteName:a,libKey:d,components:p}=e;return new S(n,{title:o,description:s,inputSchema:{userIntent:v.string().describe(`Describe what you want to build or what components you're looking for. Include the type of functionality, features, or UI elements you need from ${a}.`),needsIconsConfidence:v.number().min(0).max(1).default(.7).describe("Confidence (0-1) to include Icons assistance. Default is 0.7."),componentsNeeded:v.array(v.enum(p)).optional().describe(`Optional list of specific ${a} components you want to learn about.`)},requiredAccess:e.requiredAccess},async({userIntent:g,needsIconsConfidence:f,componentsNeeded:u},{_meta:l})=>{h("Assistant Orchestrator called with:",{userIntent:g,needsIconsConfidence:f,componentsNeeded:u});try{await t.recordOrchestratorUserRequest({meta:{userIntent:g,componentsNeeded:u,_meta:l}})}catch(A){throw R(A)}return{content:[{type:"text",text:H({name:n,userIntent:g,includeComponentsDocs:!0,includeIcons:f>.5,codeAssistantName:r,iconAssistantName:i,suiteName:a,libKey:d,components:u})}]}})}function Se(e,t){let{name:n,title:o,description:s,suiteName:i,libKey:r,getPreContent:a}=e;return new S(n,{title:o,description:s,requiredAccess:W==="utils"?e.requiredAccess:["none"],inputSchema:{prompt:v.string().describe("An enhanced prompt describing the HTML layout structure, design requirements or specific visual effects you want to achieve."),includeBuildingBlockExamples:v.boolean().describe("Whether to include building block examples. Defaults to false.").default(!1)}},async({prompt:d,includeBuildingBlockExamples:p},{_meta:b})=>{h("Layout Assistant called with:",{prompt:d,includeBuildingBlockExamples:p});try{let f=(await t.queryCssUtils({query:d},{_meta:b})).values.join(`
+`)||"No CSS utilities found for the given prompt.",u=a?.()??"",l=y=>`${u}
 
 # Kendo Design System CSS Utilities
 
-${finalMarkdown}
-${buildingBlockMd ?? ""}
-`;
-        };
-        if (includeBuildingBlockExamples) {
-          try {
-            const buildingBlocksResponse = await contextApi2.queryBuildingBlocks({
-              query: prompt,
-              lib_name: libKey
-            }, { _meta });
-            let buildingBlockMd = "";
-            if (buildingBlocksResponse.items?.length > 0) {
-              buildingBlockMd = `
+${f}
+${y??""}
+`;if(p)try{let y=await t.queryBuildingBlocks({query:d,lib_name:r},{_meta:b}),A="";y.items?.length>0&&(A=`
 ## Building Blocks Examples
 
 The examples here are for demonstration purpose how CSS utils can be implemented in various building blocks.
 However, consider your own design requirements and specifics in order to implement your templates/building blocks correctly.
 
-${buildingBlocksResponse.items.map(
-                (item) => `
-### ${item.name}
+${y.items.map(C=>`
+### ${C.name}
 
-${item.description}
+${C.description}
 
 \`\`\`code
-${item.code}
+${C.code}
 \`\`\`
-`
-              ).join("\n")}`;
-            }
-            finalMarkdown = buildLayout(buildingBlockMd);
-          } catch (buildingBlockError) {
-            log("Error calling building-blocks service:", buildingBlockError);
-            finalMarkdown = buildLayout();
-          }
-        } else {
-          finalMarkdown = buildLayout();
-        }
-        return {
-          content: [
-            {
-              type: "text",
-              text: finalMarkdown
-            }
-          ]
-        };
-      } catch (error) {
-        throw getGrpcError(error);
-      }
-    }
-  );
-}
-function createStyleAssistantTool(config, contextApi2) {
-  const { name, title, description, libKey: _libKey, getPreContent } = config;
-  return new UIAgentTool(
-    name,
-    {
-      title,
-      description,
-      requiredAccess: config.requiredAccess,
-      inputSchema: {
-        prompt: z4.string().describe(
-          `A natural language description of the desired visual style or theme. For example: 'Create a modern dark theme with high contrast'.`
-        )
-      }
-    },
-    async ({ prompt }, { _meta }) => {
-      log("Style Assistant called with:", { prompt });
-      if (LAYOUT_MODE === "tailwind") {
-        return {
-          content: [
-            {
-              type: "text",
-              text: `Note: For layout and spacing, use Tailwind CSS utility classes to structure your layout and apply spacing between elements.
+`).join(`
+`)}`),f=l(A)}catch(y){h("Error calling building-blocks service:",y),f=l()}else f=l();return{content:[{type:"text",text:f}]}}catch(g){throw R(g)}})}function we(e,t){let{name:n,title:o,description:s,libKey:i,getPreContent:r}=e;return new S(n,{title:o,description:s,requiredAccess:e.requiredAccess,inputSchema:{prompt:v.string().describe("A natural language description of the desired visual style or theme. For example: 'Create a modern dark theme with high contrast'.")}},async({prompt:a},{_meta:d})=>{if(h("Style Assistant called with:",{prompt:a}),W==="tailwind")return{content:[{type:"text",text:`Note: For layout and spacing, use Tailwind CSS utility classes to structure your layout and apply spacing between elements.
 IMPORTANT: You need to set up Tailwind CSS so it becomes the single source of truth for all design tokens. Detect which Tailwind version the project uses and follow the appropriate setup instructions below.
 
 <tailwind_setup_instructions>
-${tailwindBridgeExample}
+${z}
 </tailwind_setup_instructions>
-    `
-            }
-          ]
-        };
-      }
-      let formattedCSS = "";
-      try {
-        const result = await contextApi2.queryThemeGenerate({ prompt }, { _meta });
-        if (result.variables_json) {
-          const theme = JSON.parse(result.variables_json);
-          let cssBlocks = [];
-          if (theme) {
-            for (const key of Object.keys(theme)) {
-              if (typeof theme[key] === "string") {
-                cssBlocks.push(`${key}: ${theme[key]}`);
-              }
-            }
-          }
-          formattedCSS = cssBlocks.join("\n\n");
-        }
-      } catch (error) {
-        throw getGrpcError(error);
-      }
-      const preContent = getPreContent?.() ?? "";
-      const response = formattedCSS ? `Use the following CSS variables to style the web application, including colors, typography, spacing, and component appearance.
+    `}]};let p="";try{let f=await t.queryThemeGenerate({prompt:a},{_meta:d});if(f.variables_json){let u=JSON.parse(f.variables_json),l=[];if(u)for(let y of Object.keys(u))typeof u[y]=="string"&&l.push(`${y}: ${u[y]}`);p=l.join(`
+
+`)}}catch(f){throw R(f)}let b=r?.()??"";return{content:[{type:"text",text:p?`Use the following CSS variables to style the web application, including colors, typography, spacing, and component appearance.
 Ensure the variables are applied consistently across all relevant elements.
 Do NOT set any inline styles. CSS variables should be defined in global or component-level CSS files, or via supported theming mechanisms.
 
-${preContent}
+${b}
 
 ## Generated CSS Variables
 
 \`\`\`css
-${formattedCSS}
+${p}
 \`\`\`
-` : "No CSS variables were generated for the given prompt.";
-      return {
-        content: [
-          {
-            type: "text",
-            text: response
-          },
-          {
-            type: "text",
-            text: "Note: For layout and spacing, use the Layout Assistant tool to get the appropriate Kendo CSS utility classes."
-          }
-        ]
-      };
-    }
-  );
-}
-function createIconSearchTool(config, contextApi2) {
-  const { name, title, description, libKey: _libKey, getPostContent } = config;
-  return new UIAgentTool(
-    name,
-    {
-      title,
-      description,
-      requiredAccess: config.requiredAccess,
-      inputSchema: {
-        query: z4.string().describe(
-          "A search query for finding icons. Be specific about the icon purpose, style, or action."
-        ),
-        limit: z4.number().min(0.1).max(1).default(0.1).describe(
-          `The proportion of matching icons to return (0.1 = 1 icon, 0.5 = 5 icons, 1.0 = many icons). Default is 0.1.`
-        )
-      }
-    },
-    async ({ query, limit }, { _meta }) => {
-      log("Icon Search called with:", { query, limit });
-      try {
-        const result = await contextApi2.queryIconsSearch({
-          query,
-          limit: limit * 100
-        }, { _meta });
-        const postContent = getPostContent?.() ?? "";
-        const response = `${result.values.join("\n\n")}
-
-${postContent}`;
-        return {
-          content: [
-            {
-              type: "text",
-              text: response
-            }
-          ]
-        };
-      } catch (error) {
-        throw getGrpcError(error);
-      }
-    }
-  );
-}
-function createCodeAssistantTool(config, contextApi2) {
-  const {
-    name,
-    title,
-    description,
-    libKey,
-    suiteName: _suiteName,
-    components,
-    componentAliases,
-    getPostContent
-  } = config;
-  return new UIAgentTool(
-    name,
-    {
-      title,
-      description,
-      requiredAccess: config.requiredAccess,
-      inputSchema: {
-        query: z4.string().describe("The query to search for."),
-        component: z4.enum(components).describe(
-          "The component to search for. If not specified, use General."
-        )
-      }
-    },
-    async ({ query, component }, { _meta }) => {
-      log("Code Assistant called with:", { query, component });
-      let resolvedComponent = component;
-      if (componentAliases) {
-        const alias = componentAliases[component];
-        if (alias) {
-          resolvedComponent = alias;
-        }
-      }
-      try {
-        const response = await contextApi2.query({
-          query,
-          component: resolvedComponent?.toLowerCase() ?? "general",
-          lib_name: libKey,
-          text_matches_count: 3,
-          code_matches_count: 0,
-          allowed_types: ["documentation"]
-        }, { _meta });
-        const cleanedValues = response.values.map(
-          (val) => val.replace(/\0/g, "")
-        );
-        const postContent = getPostContent?.({ component }) ?? "";
-        const combinedResponse = `${cleanedValues.join("\n\n")}
-
-${postContent}`;
-        return {
-          content: [
-            {
-              type: "text",
-              text: combinedResponse
-            }
-          ]
-        };
-      } catch (error) {
-        throw getGrpcError(error);
-      }
-    }
-  );
-}
-function createAccessibilityAssistantTool(config, contextApi2) {
-  const {
-    name,
-    title,
-    description,
-    libKey,
-    suiteName: _suiteName,
-    components,
-    componentAliases
-  } = config;
-  return new UIAgentTool(
-    name,
-    {
-      title,
-      description,
-      requiredAccess: config.requiredAccess,
-      inputSchema: {
-        query: z4.string().describe("The query to search for."),
-        component: z4.enum(components).describe(
-          "The component to search for. If not specified, use General."
-        ),
-        includeGeneralGuidelines: z4.boolean().default(false).describe(
-          "Set to true only on the first call to include comprehensive WCAG 2.2 Level AA general guidelines. After the first call, set to false to get only component-specific accessibility information. Default is false."
-        )
-      }
-    },
-    async ({ query, component, includeGeneralGuidelines }, { _meta }) => {
-      log("Accessibility Assistant called with:", {
-        query,
-        component,
-        includeGeneralGuidelines
-      });
-      let resolvedComponent = component;
-      if (componentAliases) {
-        const alias = componentAliases[component];
-        if (alias) {
-          resolvedComponent = alias;
-        }
-      }
-      try {
-        let finalResponse = "";
-        if (includeGeneralGuidelines) {
-          const generalGuidelines = getAccessibilityGuidelines();
-          finalResponse += "# WCAG 2.2 Level AA General Accessibility Guidelines\n\n";
-          finalResponse += generalGuidelines;
-          finalResponse += "\n\n---\n\n";
-        }
-        const response = await contextApi2.getApiRefMatches({
-          query,
-          component: resolvedComponent?.toLowerCase() ?? "general",
-          lib_name: libKey,
-          filters_json: '{"type":{"$in":["accessibility"]}}'
-        }, { _meta });
-        const cleanedValues = response.values.map(
-          (val) => val.replace(/\0/g, "")
-        );
-        const formattedValues = cleanedValues.map(
-          (val) => formatApiRefItemFromJson(val, resolvedComponent?.toLowerCase() ?? "general")
-        );
-        const componentResult = formattedValues.join("\n\n");
-        if (componentResult) {
-          if (includeGeneralGuidelines) {
-            finalResponse += "# Component-Specific Accessibility Information\n\n";
-          }
-          finalResponse += componentResult;
-        } else if (!includeGeneralGuidelines) {
-          finalResponse = "No component-specific accessibility guidelines found.";
-        }
-        return {
-          content: [
-            {
-              type: "text",
-              text: finalResponse
-            }
-          ]
-        };
-      } catch (error) {
-        throw getGrpcError(error);
-      }
-    }
-  );
-}
-function getGrpcError(error) {
-  const errorObj = error;
-  if (errorObj.code === 16 /* UNAUTHENTICATED */) {
-    return new Error(
-      "Error: You are not authenticated. Please verify the Telerik License Key provided is valid."
-    );
-  } else if (errorObj.code === 8 /* RESOURCE_EXHAUSTED */) {
-    return new Error(
-      `Error: You have exceeded the extension quota. Upgrade to subscription licensing to unlock full access. Message: ${errorObj.message}.`
-    );
-  } else if (errorObj.code === 7 /* PERMISSION_DENIED */) {
-    return new Error(
-      "Error: You do not have permission to access this resource. Please verify that you have a valid license."
-    );
-  } else {
-    return new Error(
-      `Error: An error occurred while calling the service. Please try again later.
-
-Error Code: ${errorObj.code} Error Message: ${errorObj.message}`
-    );
-  }
-}
+`:"No CSS variables were generated for the given prompt."},{type:"text",text:"Note: For layout and spacing, use the Layout Assistant tool to get the appropriate Kendo CSS utility classes."}]}})}function Te(e,t){let{name:n,title:o,description:s,libKey:i,getPostContent:r}=e;return new S(n,{title:o,description:s,requiredAccess:e.requiredAccess,inputSchema:{query:v.string().describe("A search query for finding icons. Be specific about the icon purpose, style, or action."),limit:v.number().min(.1).max(1).default(.1).describe("The proportion of matching icons to return (0.1 = 1 icon, 0.5 = 5 icons, 1.0 = many icons). Default is 0.1.")}},async({query:a,limit:d},{_meta:p})=>{h("Icon Search called with:",{query:a,limit:d});try{let b=await t.queryIconsSearch({query:a,limit:d*100},{_meta:p}),g=r?.()??"";return{content:[{type:"text",text:`${b.values.join(`
 
-// packages/kendo-ui-agent/src/lib/figma-d2c/types.ts
-var FigmaAPIError = class extends Error {
-  constructor(status, body) {
-    super(`Figma API error ${status}: ${body}`);
-    this.status = status;
-    this.body = body;
-    this.name = "FigmaAPIError";
-  }
-};
-
-// packages/kendo-ui-agent/src/lib/figma-d2c/figma-client.ts
-var FigmaClient = class {
-  constructor(apiKey) {
-    this.retryConfig = {
-      maxRetries: 3,
-      baseDelayMs: 1e3,
-      maxDelayMs: 3e4
-    };
-    this.apiKey = apiKey;
-  }
-  /**
-   * Fetch file metadata including node and component counts
-   */
-  async getFileMeta(fileKey) {
-    const fileResponse = await this.getFile(fileKey, { depth: 1 });
-    const counts = this.countNodesAndComponents(fileResponse.document);
-    return {
-      nodeCount: counts.nodes,
-      componentCount: counts.components
-    };
-  }
-  /**
-   * Fetch a specific file with optional depth parameter
-   */
-  async getFile(fileKey, options) {
-    const url = this.buildFileUrl(fileKey, options);
-    return this.fetchWithRetry(url);
-  }
-  /**
-   * Fetch specific nodes by ID
-   */
-  async getNodes(fileKey, nodeIds, options) {
-    const url = this.buildNodesUrl(fileKey, nodeIds, options);
-    return this.fetchWithRetry(url);
-  }
-  /**
-   * Get export URLs for node images
-   */
-  async getImages(fileKey, nodeIds, options) {
-    const url = this.buildImagesUrl(fileKey, nodeIds, options);
-    return this.fetchWithRetry(url);
-  }
-  /**
-   * Get download URLs for embedded image fills
-   * Returns a map of imageRef hashes to temporary S3 download URLs
-   */
-  async getImageFills(fileKey) {
-    const url = `https://api.figma.com/v1/files/${fileKey}/images`;
-    return this.fetchWithRetry(url);
-  }
-  /**
-   * Core fetch method with retry logic
-   */
-  async fetchWithRetry(url) {
-    let lastError = null;
-    for (let attempt = 0; attempt < this.retryConfig.maxRetries; attempt++) {
-      try {
-        const response = await fetch(url, {
-          headers: {
-            "X-Figma-Token": this.apiKey,
-            "Content-Type": "application/json"
-          }
-        });
-        if (response.status === 429) {
-          const retryAfter = response.headers.get("Retry-After");
-          const delayMs = retryAfter ? parseInt(retryAfter) * 1e3 : this.calculateBackoff(attempt);
-          await this.sleep(delayMs);
-          continue;
-        }
-        if (!response.ok) {
-          const body = await response.text();
-          throw new FigmaAPIError(response.status, body);
-        }
-        return await response.json();
-      } catch (err) {
-        lastError = err;
-        if (err instanceof FigmaAPIError && err.status >= 400 && err.status < 500) {
-          throw err;
-        }
-        if (attempt < this.retryConfig.maxRetries - 1) {
-          await this.sleep(this.calculateBackoff(attempt));
-        }
-      }
-    }
-    throw lastError ?? new Error("Max retries exceeded");
-  }
-  /**
-   * Calculate exponential backoff with jitter
-   */
-  calculateBackoff(attempt) {
-    const delay = this.retryConfig.baseDelayMs * Math.pow(2, attempt);
-    const jitter = Math.random() * 0.3 * delay;
-    return Math.min(delay + jitter, this.retryConfig.maxDelayMs);
-  }
-  sleep(ms) {
-    return new Promise((resolve) => setTimeout(resolve, ms));
-  }
-  buildFileUrl(fileKey, options) {
-    const base = `https://api.figma.com/v1/files/${fileKey}`;
-    const params = new URLSearchParams();
-    if (options?.depth) {
-      params.set("depth", options.depth.toString());
-    }
-    return params.toString() ? `${base}?${params}` : base;
-  }
-  buildNodesUrl(fileKey, nodeIds, options) {
-    const base = `https://api.figma.com/v1/files/${fileKey}/nodes`;
-    const params = new URLSearchParams();
-    params.set("ids", nodeIds.join(","));
-    if (options?.depth) {
-      params.set("depth", options.depth.toString());
-    }
-    return `${base}?${params}`;
-  }
-  buildImagesUrl(fileKey, nodeIds, options) {
-    const base = `https://api.figma.com/v1/images/${fileKey}`;
-    const params = new URLSearchParams();
-    params.set("ids", nodeIds.join(","));
-    if (options?.format) params.set("format", options.format);
-    if (options?.scale) params.set("scale", options.scale.toString());
-    return `${base}?${params}`;
-  }
-  /**
-   * Recursively count nodes and components in the document tree
-   */
-  countNodesAndComponents(node) {
-    let nodes = 1;
-    let components = node.type === "COMPONENT" || node.type === "COMPONENT_SET" ? 1 : 0;
-    if (node.children) {
-      for (const child of node.children) {
-        const childCounts = this.countNodesAndComponents(child);
-        nodes += childCounts.nodes;
-        components += childCounts.components;
-      }
-    }
-    return { nodes, components };
-  }
-};
-
-// packages/kendo-ui-agent/src/lib/figma-d2c/utils.ts
-function parseFigmaUrl(url) {
-  const invalidResult = {
-    fileKey: "",
-    type: "unknown",
-    isDevMode: false,
-    isValid: false
-  };
-  if (!url || typeof url !== "string") {
-    return invalidResult;
-  }
-  let parsed;
-  try {
-    parsed = new URL(url.trim());
-  } catch {
-    return invalidResult;
-  }
-  const validDomains = ["figma.com", "www.figma.com"];
-  if (!validDomains.includes(parsed.hostname)) {
-    return invalidResult;
-  }
-  const pathParts = parsed.pathname.split("/").filter(Boolean);
-  if (pathParts.length < 2) {
-    return invalidResult;
-  }
-  const typeMap = {
-    file: "file",
-    design: "design",
-    proto: "proto",
-    board: "board"
-  };
-  const type = typeMap[pathParts[0]] || "unknown";
-  const fileKey = pathParts[1];
-  if (!/^[a-zA-Z0-9]+$/.test(fileKey)) {
-    return invalidResult;
-  }
-  const fileName = pathParts[2] ? decodeURIComponent(pathParts[2]).replace(/-/g, " ") : void 0;
-  const nodeIdParam = parsed.searchParams.get("node-id");
-  let nodeId;
-  let nodeIds;
-  if (nodeIdParam) {
-    const rawIds = nodeIdParam.split(",").map((id) => id.trim()).filter(Boolean);
-    nodeIds = rawIds.map((id) => id.replace(/-/g, ":"));
-    nodeId = nodeIds[0];
-  }
-  const branchKey = parsed.searchParams.get("t") ?? void 0;
-  const isDevMode = parsed.searchParams.get("m") === "dev";
-  return {
-    fileKey,
-    fileName,
-    nodeId,
-    nodeIds,
-    type,
-    branchKey,
-    isDevMode,
-    isValid: true
-  };
-}
+`)}
 
-// packages/kendo-ui-agent/src/lib/figma-d2c/fetcher.ts
-var NodeFetcher = class {
-  constructor(client) {
-    this.client = client;
-  }
-  /**
-   * Fetch a design starting from a file or specific node(s)
-   * 
-   * @param fileKey - The Figma file key
-   * @param nodeIds - Optional node ID(s) - can be string or string[]
-   * @param options - Fetch options including depth
-   * @returns Fetch result with root node and stats
-   */
-  async fetch(fileKey, nodeIds, options = {}) {
-    const initialDepth = options.initialDepth ?? 10;
-    const fetchImages = options.fetchImages ?? true;
-    const imageFormat = options.imageFormat ?? "png";
-    const imageScale = options.imageScale ?? 2;
-    const stats = {
-      totalNodesFetched: 0,
-      apiCallsMade: 0,
-      imagesFetched: 0
-    };
-    let nodeIdArray;
-    if (!nodeIds) {
-      nodeIdArray = [];
-    } else if (typeof nodeIds === "string") {
-      nodeIdArray = [nodeIds];
-    } else {
-      nodeIdArray = nodeIds;
-    }
-    let rootNode;
-    let fetchedNodes = [];
-    if (nodeIdArray.length > 0) {
-      const response = await this.client.getNodes(fileKey, nodeIdArray, { depth: initialDepth });
-      stats.apiCallsMade++;
-      for (const nodeId of nodeIdArray) {
-        const nodeData = response.nodes[nodeId]?.document;
-        if (!nodeData) {
-          throw new Error(`Node ${nodeId} not found`);
-        }
-        fetchedNodes.push(nodeData);
-      }
-      if (fetchedNodes.length === 1) {
-        rootNode = fetchedNodes[0];
-      } else {
-        rootNode = this.createContainerNode(fetchedNodes);
-      }
-    } else {
-      const response = await this.client.getFile(fileKey, { depth: initialDepth });
-      stats.apiCallsMade++;
-      rootNode = response.document;
-      fetchedNodes = [rootNode];
-    }
-    stats.totalNodesFetched += this.countNodes(rootNode);
-    const images = [];
-    if (fetchImages && nodeIdArray.length > 0) {
-      try {
-        const imageResult = await this.fetchNodeImages(
-          fileKey,
-          nodeIdArray,
-          fetchedNodes,
-          { format: imageFormat, scale: imageScale }
-        );
-        images.push(...imageResult.images);
-        stats.apiCallsMade += imageResult.apiCalls;
-        stats.imagesFetched = images.length;
-      } catch (error) {
-        console.warn("Failed to fetch images:", error);
-      }
-    }
-    return {
-      rootNode,
-      fetchedNodes,
-      images,
-      stats
-    };
-  }
-  /**
-   * Fetch and download images for specified nodes
-   */
-  async fetchNodeImages(fileKey, nodeIds, nodes, options) {
-    const imageResponse = await this.client.getImages(fileKey, nodeIds, options);
-    let apiCalls = 1;
-    const images = [];
-    for (let i = 0; i < nodeIds.length; i++) {
-      const nodeId = nodeIds[i];
-      const imageUrl = imageResponse.images[nodeId];
-      if (imageUrl) {
-        try {
-          const imageData = await this.downloadImage(imageUrl, options.format);
-          const node = nodes[i];
-          images.push({
-            nodeId,
-            nodeName: node?.name || "Unknown",
-            data: imageData,
-            mimeType: this.getMimeType(options.format),
-            url: imageUrl
-          });
-        } catch (error) {
-          console.warn(`Failed to download image for node ${nodeId}:`, error);
-        }
-      }
-    }
-    return { images, apiCalls };
-  }
-  /**
-   * Download an image from a URL and convert to base64
-   */
-  async downloadImage(url, format) {
-    const response = await fetch(url);
-    if (!response.ok) {
-      throw new Error(`Failed to download image: ${response.statusText}`);
-    }
-    if (format === "svg") {
-      const svgText = await response.text();
-      return Buffer.from(svgText, "utf-8").toString("base64");
-    } else {
-      const arrayBuffer = await response.arrayBuffer();
-      return Buffer.from(arrayBuffer).toString("base64");
-    }
-  }
-  /**
-   * Get MIME type for image format
-   */
-  getMimeType(format) {
-    switch (format) {
-      case "png":
-        return "image/png";
-      case "jpg":
-        return "image/jpeg";
-      case "svg":
-        return "image/svg+xml";
-      default:
-        return "image/png";
-    }
-  }
-  /**
-   * Create a synthetic container node that wraps multiple nodes
-   */
-  createContainerNode(nodes) {
-    return {
-      id: "container-" + Date.now(),
-      name: "Multi-Node Container",
-      type: "GROUP",
-      visible: true,
-      children: nodes
-    };
-  }
-  /**
-   * Count total nodes in a tree
-   */
-  countNodes(node) {
-    let count = 1;
-    if (node.children) {
-      for (const child of node.children) {
-        count += this.countNodes(child);
-      }
-    }
-    return count;
-  }
-};
-
-// packages/kendo-ui-agent/src/lib/figma-d2c/figma-d2c-tool.ts
-import { z as z5 } from "zod";
-function createFigmaD2CTool({
-  name,
-  figmaApiKey,
-  requiredAccess
-}, contextApi2) {
-  return new UIAgentTool(
-    name,
-    {
-      title: "Figma Design to Code",
-      description: "Converts Figma designs to code by analyzing the design structure and matching Kendo UI components. Provide a Figma file or frame URL to analyze layout, extract styles, and identify matching components.",
-      inputSchema: {
-        url: z5.string().describe(
-          "Figma file or node URL (e.g., https://www.figma.com/file/...)"
-        ).optional(),
-        fileKey: z5.string().describe("Figma file key (alternative to URL)").optional(),
-        nodeIds: z5.array(z5.string()).describe("Array of specific node IDs to fetch (alternative to URL)").optional(),
-        depth: z5.number().min(1).max(20).default(10).describe("Initial fetch depth (1-20, default: 10)")
-      },
-      requiredAccess
-    },
-    async ({ url, fileKey, nodeIds, depth }) => {
-      const client = new FigmaClient(figmaApiKey);
-      const fetcher = new NodeFetcher(client);
-      let fileKeyToUse = fileKey;
-      let nodeIdsToUse;
-      if (fileKeyToUse) {
-        if (nodeIds && nodeIds.length > 0) {
-          nodeIdsToUse = nodeIds.length === 1 ? nodeIds[0] : nodeIds;
-        }
-      } else if (url) {
-        const parsed = parseFigmaUrl(url);
-        if (!parsed.isValid || !parsed.fileKey) {
-          throw new Error(
-            "Invalid Figma URL. Please provide a valid Figma file or frame URL."
-          );
-        }
-        fileKeyToUse = parsed.fileKey;
-        if (parsed.nodeId) {
-          nodeIdsToUse = parsed.nodeId;
-        }
-      } else {
-        throw new Error("Please provide either a Figma URL, fileKey, or both.");
-      }
-      const fetchResult = await fetcher.fetch(fileKeyToUse, nodeIdsToUse, {
-        initialDepth: depth,
-        fetchImages: true,
-        imageFormat: "png",
-        imageScale: 2
-      });
-      const resultJson = {
-        name: fetchResult.rootNode.name,
-        type: fetchResult.rootNode.type,
-        rootNode: fetchResult.rootNode,
-        fetchedNodes: fetchResult.fetchedNodes,
-        meta: {
-          fileKey,
-          nodeIds
-        }
-      };
-      let backendResponse;
-      try {
-        const nodeJsons = fetchResult.fetchedNodes.map(
-          (node) => JSON.stringify(node)
-        );
-        backendResponse = await contextApi2.processFigmaDesign({
-          node_jsons: nodeJsons
-        });
-      } catch (error) {
-        console.error("Backend processing failed:", error);
-        return {
-          content: [
-            {
-              type: "text",
-              text: JSON.stringify(
-                {
-                  error: {
-                    message: `Backend processing failed: ${error.message}`,
-                    code: error.code || "UNKNOWN"
-                  },
-                  figma_data: resultJson
-                },
-                null,
-                2
-              )
-            }
-          ]
-        };
-      }
-      const content = [];
-      content.push({
-        type: "text",
-        text: `# Figma Design Extraction Results
-Successfully fetched design data for file key ${fileKeyToUse} with for nodes [${nodeIds?.join(", ")}]. 
-The following is the processed design data including layout pseudo-code and design tokens extracted from the Figma design, plus images for visual references of the desired nodes:`
-      });
-      backendResponse.layout_pseudo_codes.forEach((layoutCode, index) => {
-        const [nodeName, nodeId] = ((index2) => {
-          const node = fetchResult.fetchedNodes[index2];
-          return node ? [node.name, node.id] : ["Unknown Node", "unknown_id"];
-        })(index);
-        content.push({
-          type: "text",
-          text: `## Psuedo-code Layout - Node: ${nodeName} (${nodeId})
-
-` + layoutCode,
-          _meta: {
-            description: `Psuedo-code Layout - Node: ${nodeName} (${nodeId})`
-          },
-          annotations: {
-            audience: ["assistant"]
-          }
-        });
-      });
-      content.push({
-        type: "text",
-        text: `## Design Tokens - File: ${fileKey} for Nodes: [${nodeIds?.join(", ")}]
-
-` + backendResponse.design_tokens,
-        _meta: {
-          description: `Design Tokens - File: ${fileKey} for Nodes: [${nodeIds?.join(", ")}]`
-        },
-        annotations: {
-          audience: ["assistant"]
-        }
-      });
-      if (fetchResult.images && fetchResult.images.length > 0) {
-        for (const image of fetchResult.images) {
-          content.push({
-            type: "image",
-            data: image.data,
-            mimeType: image.mimeType,
-            _meta: {
-              description: `Design snapshot of ${image.nodeName} (${image.nodeId})`
-            },
-            annotations: {
-              audience: ["assistant"]
-            }
-          });
-        }
-      }
-      content.push({
-        type: "text",
-        text: `# Analysis Instructions and Next Steps
-
-Use the above design data, layout pseudo-code, and design tokens to analyze the Figma design and identify components. Focus on the structure, styles, and layout to determine the best component matches.
-If more design details are needed, consider asking for additional nodes or deeper fetches to gather more information about specific areas of the design.`
-      });
-      return {
-        content
-      };
-    }
-  );
-}
+${g}`}]}}catch(b){throw R(b)}})}function Ie(e,t){let{name:n,title:o,description:s,libKey:i,suiteName:r,components:a,componentAliases:d,getPostContent:p}=e;return new S(n,{title:o,description:s,requiredAccess:e.requiredAccess,inputSchema:{query:v.string().describe("The query to search for."),component:v.enum(a).describe("The component to search for. If not specified, use General.")}},async({query:b,component:g},{_meta:f})=>{h("Code Assistant called with:",{query:b,component:g});let u=g;if(d){let l=d[g];l&&(u=l)}try{let y=(await t.query({query:b,component:u?.toLowerCase()??"general",lib_name:i,text_matches_count:3,code_matches_count:0,allowed_types:["documentation"]},{_meta:f})).values.map(w=>w.replace(/\0/g,"")),A=p?.({component:g})??"";return{content:[{type:"text",text:`${y.join(`
+
+`)}
+
+${A}`}]}}catch(l){throw R(l)}})}function xe(e,t){let{name:n,title:o,description:s,libKey:i,suiteName:r,components:a,componentAliases:d}=e;return new S(n,{title:o,description:s,requiredAccess:e.requiredAccess,inputSchema:{query:v.string().describe("The query to search for."),component:v.enum(a).describe("The component to search for. If not specified, use General."),includeGeneralGuidelines:v.boolean().default(!1).describe("Set to true only on the first call to include comprehensive WCAG 2.2 Level AA general guidelines. After the first call, set to false to get only component-specific accessibility information. Default is false.")}},async({query:p,component:b,includeGeneralGuidelines:g},{_meta:f})=>{h("Accessibility Assistant called with:",{query:p,component:b,includeGeneralGuidelines:g});let u=b;if(d){let l=d[b];l&&(u=l)}try{let l="";if(g){let I=ge();l+=`# WCAG 2.2 Level AA General Accessibility Guidelines
+
+`,l+=I,l+=`
+
+---
 
-// packages/kendo-ui-agent/src/lib/tool-names.ts
-var orchestratorToolName = (prefix) => `${prefix}_ui_generator`;
-var assistantOrchestratorToolName = (prefix) => `${prefix}_assistant`;
-var layoutAssistantName = (prefix) => `${prefix}_layout_assistant`;
-var codeAssistantName = (prefix) => `${prefix}_component_assistant`;
-var styleAssistantName = (prefix) => `${prefix}_style_assistant`;
-var iconAssistantName = (prefix) => `${prefix}_icon_assistant`;
-var accessibilityAssistantName = (prefix) => `${prefix}_accessibility_assistant`;
-var gettingStartedAssistantName = (prefix) => `${prefix}_getting_started_assistant`;
-var figmaD2CToolName = (prefix) => `${prefix}_figma_d2c`;
+`}let w=(await t.getApiRefMatches({query:p,component:u?.toLowerCase()??"general",lib_name:i,filters_json:'{"type":{"$in":["accessibility"]}}'},{_meta:f})).values.map(I=>I.replace(/\0/g,"")).map(I=>Tt(I,u?.toLowerCase()??"general")).join(`
 
-// packages/kendo-ui-agent/src/lib/tool-descriptions.ts
-var orchestratorToolDescription = (suiteName) => `This is the single entry point for all UI-related tasks. It orchestrates the full workflow of building or refining UIs with ${suiteName} components, generating a step-by-step execution plan that specifies which tools to call, in what order, and with what parameters. It includes validation steps to ensure the best possible, standards-compliant code every time.
+`);return w?(g&&(l+=`# Component-Specific Accessibility Information
+
+`),l+=w):g||(l="No component-specific accessibility guidelines found."),{content:[{type:"text",text:l}]}}catch(l){throw R(l)}})}function R(e){let t=e;return t.code===16?new Error("Error: You are not authenticated. Please verify the Telerik License Key provided is valid."):t.code===8?new Error(`Error: You have exceeded the extension quota. Upgrade to subscription licensing to unlock full access. Message: ${t.message}.`):t.code===7?new Error("Error: You do not have permission to access this resource. Please verify that you have a valid license."):new Error(`Error: An error occurred while calling the service. Please try again later.
+
+Error Code: ${t.code} Error Message: ${t.message}`)}var Ne=e=>`${e}_ui_generator`,Ee=e=>`${e}_assistant`,Re=e=>`${e}_layout_assistant`,Pe=e=>`${e}_component_assistant`,De=e=>`${e}_style_assistant`,Oe=e=>`${e}_icon_assistant`,Ge=e=>`${e}_accessibility_assistant`,Le=e=>`${e}_getting_started_assistant`;var Ue=e=>`This is the single entry point for all UI-related tasks. It orchestrates the full workflow of building or refining UIs with ${e} components, generating a step-by-step execution plan that specifies which tools to call, in what order, and with what parameters. It includes validation steps to ensure the best possible, standards-compliant code every time.
 
   Use the tool when:
   - Want to build or modify a complete page or section layout
   - You are creating and applying custom themes via the Kendo Design System
-  - You need guidance on correct ${suiteName} component selection and configuration
+  - You need guidance on correct ${e} component selection and configuration
   - You want to enforce best practices in styling, performance, and accessibility
 
 Returns:
-A detailed execution plan with validated tool calls, parameters, and reasoning \u2014 ensuring consistent, high-quality UI generation.`;
-var assistantOrchestratorToolDescription = (suiteName) => `Provides guidance for discovering and using ${suiteName} components and icons. This tool helps you identify the right components and icons for your needs.
+A detailed execution plan with validated tool calls, parameters, and reasoning \u2014 ensuring consistent, high-quality UI generation.`,_e=e=>`Provides guidance for discovering and using ${e} components and icons. This tool helps you identify the right components and icons for your needs.
 
 Use this tool when:
-- You need to discover which ${suiteName} components are suitable for a specific use case
+- You need to discover which ${e} components are suitable for a specific use case
 - You want to understand component features and capabilities
 - You need to find appropriate icons for your UI
 - You want to gather component documentation and examples
 
 Returns:
-A focused plan for gathering component documentation and icon suggestions using the Component Assistant and Icon Assistant tools.`;
-var layoutToolDescription = `Retrieves Progress/Kendo Design System CSS utility classes and styling recommendations based on layout and design requirements.
+A focused plan for gathering component documentation and icon suggestions using the Component Assistant and Icon Assistant tools.`,$e=`Retrieves Progress/Kendo Design System CSS utility classes and styling recommendations based on layout and design requirements.
 Use this tool to find the right CSS utilities for styling Kendo UI components or general web elements.
 It analyzes the provided design context and returns relevant utility classes with explanations and examples.
-Best suited for styling questions related to typography, spacing, colors, layout, transforms, and other utilities in the Progress/Kendo Design System.`;
-var styleToolDescription = `Generates CSS variables using an external style agent based on the user's styling prompt.
+Best suited for styling questions related to typography, spacing, colors, layout, transforms, and other utilities in the Progress/Kendo Design System.`,Me=`Generates CSS variables using an external style agent based on the user's styling prompt.
 
 Use this tool when the user wants to:
 - Update the visual theme of an application
 - Modify color schemes
 - Restyle the UI with CSS variables
 
-The tool outputs a set of CSS variable definitions ready to be applied to style files.`;
-var iconToolDescription = `Searches for icons in the Telerik Icons library.
+The tool outputs a set of CSS variable definitions ready to be applied to style files.`,Be=`Searches for icons in the Telerik Icons library.
 Use this tool when the user needs to find specific icons for UI components or design elements.
 It supports searching by icon name, category, or keyword and returns matching icons from the Telerik Icons library.
-`;
-var codeAssistantToolDescription = (suiteName) => `Provides answers and retrieves official documentation for ${suiteName}.
+`,qe=e=>`Provides answers and retrieves official documentation for ${e}.
 
 Use this tool when the user asks about:
-- ${suiteName} features or capabilities
+- ${e} features or capabilities
 - Specific components (e.g., Grid, Chart, Editor)
 - Implementation details, configuration, or best practices
-- How to use or customize components in ${suiteName}
+- How to use or customize components in ${e}
 
 Set the user's full question as the 'query' parameter.
-If the question refers to a specific ${suiteName} component, include its name in the 'component' parameter.
-`;
-var accessibilityToolDescription = (suiteName) => `Retrieves accessibility guidance for ${suiteName} components with optional general WCAG 2.2 Level AA guidelines.
+If the question refers to a specific ${e} component, include its name in the 'component' parameter.
+`,Fe=e=>`Retrieves accessibility guidance for ${e} components with optional general WCAG 2.2 Level AA guidelines.
 
 Use this tool when:
 - You need component-specific accessibility information and API references
@@ -2853,11 +905,7 @@ Set 'includeGeneralGuidelines=true' ONLY on the first call to include general WC
 Returns:
 - When includeGeneralGuidelines=true: General WCAG 2.2 Level AA guidelines + component-specific recommendations
 - When includeGeneralGuidelines=false: Only component-specific accessibility recommendations
-`;
-
-// packages/kendo-ui-agent/src/lib/validation/angular-validation-steps.ts
-var sharedSteps = getSharedValidationSteps("Kendo UI", "Kendo");
-var ANGULAR_VALIDATION_STEPS = `
+`;var Y=E("Kendo UI","Kendo"),Q=`
 ### Angular Component Validation
 Component Structure:
   - Use proper @Component decorator configuration
@@ -2865,25 +913,22 @@ Component Structure:
   - Correct selector naming convention (kebab-case)
   - Appropriate template and style file organization
 
-${sharedSteps.SETUP_VALIDATION}
+${Y.SETUP_VALIDATION}
   - Kendo animations module configured (if animations are used)
   - Internationalization properly configured for Kendo components
 
-${sharedSteps.PERFORMANCE_OPTIMIZATION}
+${Y.PERFORMANCE_OPTIMIZATION}
   - OnPush change detection strategy where appropriate
   - Efficient trackBy functions for *ngFor with Kendo components
   - Minimal unnecessary change detection cycles
 
-${sharedSteps.THEME_AND_STYLING}
+${Y.THEME_AND_STYLING}
   - Proper theme switching functionality (if implemented)
   - Only ONE theme reference exists across angular.json and styles files
   - Make sure theme import mechanism is consistent with existing project setup
 
 Accessibility
-  - Accessibility guidelines retrieved and applied to all components`;
-
-// packages/kendo-ui-agent/src/lib/validation/angular-additional-plan.ts
-var ANGULAR_ADDITIONAL_PLAN = `**Angular Specific Requirements:**
+  - Accessibility guidelines retrieved and applied to all components`;var J=`**Angular Specific Requirements:**
 
 **NgModule vs Standalone setup**: Search and detect the current project setup to determine whether to use NgModule or Standalone components based on the following rules:
   1. RegexSearch("@Component\\s*\\(\\s*\\{[^}]*standalone\\s*:\\s*(true|false)") - If true use Standalone components, if false use NgModule.
@@ -2914,11 +959,7 @@ var ANGULAR_ADDITIONAL_PLAN = `**Angular Specific Requirements:**
   2. Match the discovered patterns in all generated code
   3. Maintain consistent formatting, indentation, and code organization with existing files
   4. Always use the same theme import mechanism (unless user specifies otherwise)
-`;
-
-// packages/kendo-ui-agent/src/lib/validation/react-validation-steps.ts
-var sharedSteps2 = getSharedValidationSteps("Kendo UI", "KendoReact");
-var REACT_VALIDATION_STEPS = `
+`;var X=E("Kendo UI","KendoReact"),Z=`
 ### React Component Validation
 Component Structure:
   - Use proper function component patterns with Hooks
@@ -2926,85 +967,22 @@ Component Structure:
   - Appropriate file organization (components, hooks, utils)
   - Props interface/type definitions where needed
 
-${sharedSteps2.SETUP_VALIDATION}
+${X.SETUP_VALIDATION}
   - KendoReact license validation (if required)
   - Appropriate bundler configuration for KendoReact packages
 
-${sharedSteps2.PERFORMANCE_OPTIMIZATION}
+${X.PERFORMANCE_OPTIMIZATION}
   - React.memo for components that receive stable props
   - useMemo/useCallback for expensive computations and callbacks
   - Proper key props for list rendering with KendoReact components
 
-${sharedSteps2.THEME_AND_STYLING}
+${X.THEME_AND_STYLING}
   - Proper theme switching functionality (if implemented)
   - Only ONE theme import exists across the application
   - Make sure theme import mechanism is consistent with existing project setup
 
 Accessibility
-  - Accessibility guidelines retrieved and applied to all components`;
-
-// packages/kendo-ui-agent/src/index.ts
-var Tools = {
-  createOrchestrator: createOrchestratorTool,
-  createAssistantOrchestrator: createAssistantOrchestratorTool,
-  createLayoutAssistant: createLayoutAssistantTool,
-  createStyleAssistant: createStyleAssistantTool,
-  createIconSearch: createIconSearchTool,
-  createCodeAssistant: createCodeAssistantTool,
-  createAccessibilityAssistant: createAccessibilityAssistantTool,
-  createFigmaD2C: createFigmaD2CTool
-};
-var ToolNames = {
-  orchestrator: orchestratorToolName,
-  assistantOrchestrator: assistantOrchestratorToolName,
-  layoutAssistant: layoutAssistantName,
-  codeAssistant: codeAssistantName,
-  styleAssistant: styleAssistantName,
-  iconAssistant: iconAssistantName,
-  accessibilityAssistant: accessibilityAssistantName,
-  gettingStartedAssistant: gettingStartedAssistantName,
-  figmaD2C: figmaD2CToolName
-};
-var ToolDescriptions = {
-  orchestrator: orchestratorToolDescription,
-  assistantOrchestrator: assistantOrchestratorToolDescription,
-  layoutAssistant: layoutToolDescription,
-  styleAssistant: styleToolDescription,
-  iconAssistant: iconToolDescription,
-  codeAssistant: codeAssistantToolDescription,
-  accessibilityAssistant: accessibilityToolDescription
-};
-var Templates = {
-  Orchestrator: {
-    render: renderOrchestratorResponse
-  },
-  Validator: {
-    render: renderValidatorResponse
-  },
-  SharedValidation: {
-    getSteps: getSharedValidationSteps
-  }
-};
-var Validation = {
-  Angular: {
-    steps: ANGULAR_VALIDATION_STEPS,
-    additionalPlan: ANGULAR_ADDITIONAL_PLAN
-  },
-  React: {
-    steps: REACT_VALIDATION_STEPS
-  }
-};
-var UIAgent = {
-  Tools,
-  ToolNames,
-  ToolDescriptions,
-  Templates,
-  Validation
-};
-
-// packages/react/src/lib/instructions/layout.ts
-var CODE_ASSISTANT_NAME = UIAgent.ToolNames.codeAssistant("kendoreact");
-var getLayoutInstructions = () => `# Kendo Design System Guidelines for ${REACT_SUITE_NAME}
+  - Accessibility guidelines retrieved and applied to all components`;var It={createOrchestrator:Ae,createAssistantOrchestrator:Ce,createLayoutAssistant:Se,createStyleAssistant:we,createIconSearch:Te,createCodeAssistant:Ie,createAccessibilityAssistant:xe},xt={orchestrator:Ne,assistantOrchestrator:Ee,layoutAssistant:Re,codeAssistant:Pe,styleAssistant:De,iconAssistant:Oe,accessibilityAssistant:Ge,gettingStartedAssistant:Le},Nt={orchestrator:Ue,assistantOrchestrator:_e,layoutAssistant:$e,styleAssistant:Me,iconAssistant:Be,codeAssistant:qe,accessibilityAssistant:Fe},Et={Orchestrator:{render:U},Validator:{render:L},SharedValidation:{getSteps:E}},Rt={Angular:{steps:Q,additionalPlan:J},React:{steps:Z}},m={Tools:It,ToolNames:xt,ToolDescriptions:Nt,Templates:Et,Validation:Rt};var Pt=m.ToolNames.codeAssistant("kendoreact"),Ke=()=>`# Kendo Design System Guidelines for ${c}
 
 ## Setting up Styles/CSS
 
@@ -3031,17 +1009,155 @@ Alternatively, you can also consume them directly from the Unpkg CDN.
 
 ## Ready-to-use Layout Components
 
-In the ${REACT_SUITE_NAME} there are available components to create layout. Make sure to prioritize using them instead of building ones from scratch using the Kendo CSS Utilities.
+In the ${c} there are available components to create layout. Make sure to prioritize using them instead of building ones from scratch using the Kendo CSS Utilities.
 
-For any Layout component you can also call the ${CODE_ASSISTANT_NAME} tool in order to get specific API reference and docs.
+For any Layout component you can also call the ${Pt} tool in order to get specific API reference and docs.
 
-- ${REACT_SUITE_NAME} Card component.
+- ${c} Card component.
     - Generally, it is recommended to use 100% width (e.g., \`<Card style={{ width: '100%' }}>\`)
     - If needed, use specific width based on the layout requirements (e.g., \`<Card style={{ width: '150px' }}>\`)
-`;
+    - Avoid applying additional styling properties such as \`display\`, \`flex\`, \`grid\`, or other layout-specific CSS to layout components such as Splitter, DockLayout, and TileLayout. Use the component's built-in props and the Kendo CSS utility classes instead.
+
+## Page Shell Patterns
 
-// packages/react/src/lib/instructions/style.ts
-var getStyleInstructions = () => `## Applying CSS Variables in ${REACT_SUITE_NAME}
+Choose the pattern that matches the page structure:
+
+**Pattern A \u2014 Sidebar + Main Content**
+\`\`\`css
+.app-shell {
+  display: flex;
+  height: 100vh;
+}
+.sidebar {
+  width: 240px;
+  flex-shrink: 0;
+}
+.main-content {
+  flex: 1;
+  min-width: 0; /* Critical: prevents flex children from overflowing */
+  overflow: auto;
+}
+\`\`\`
+
+**Pattern B \u2014 Centered Single-Column (forms, detail pages)**
+\`\`\`css
+.page-container {
+  max-width: 960px;
+  margin: 0 auto;
+  padding: 0 1rem;
+}
+\`\`\`
+
+**Pattern C \u2014 Master-Detail Split**
+\`\`\`css
+.split-container {
+  display: grid;
+  grid-template-columns: 420px 1fr;
+  height: 100%;
+}
+\`\`\`
+
+## Dashboard Layout
+
+**KPI metric row** (auto-responsive, min 180px per card):
+\`\`\`css
+.kpi-row {
+  display: grid;
+  grid-template-columns: repeat(auto-fit, minmax(180px, 1fr));
+  gap: 1rem;
+}
+\`\`\`
+
+**Side-by-side charts** (equal width, no overflow):
+\`\`\`css
+.chart-row {
+  display: grid;
+  grid-template-columns: minmax(0, 1fr) minmax(0, 1fr);
+  gap: 1rem;
+}
+\`\`\`
+
+## Critical Sizing Rules
+
+- **\`min-width: 0\`** on every flex/grid child that contains a Kendo component \u2014 the single most common cause of layout overflow.
+- **Grid component** always requires an explicit height (e.g., \`style={{ height: 500 }}\` or \`flex: 1; min-height: 0\` inside a flex column).
+- **Chart component** always requires an explicit height (e.g., \`style={{ height: 300 }}\`).
+- Never leave Grid column widths unset \u2014 without a height, Grid renders all rows and expands the page indefinitely..
+- Constrain page content to \`max-width: 1440px\` with \`margin: 0 auto\` to prevent unbounded wide-screen stretching, unless the project defines a different maximum content width.
+
+## Dark Theme Completeness
+
+Kendo themes style \`.k-*\` component selectors only. Always add these two lines to your global CSS file after any theme import:
+
+\`\`\`css
+html, body {
+  background-color: var(--kendo-body-bg);
+  color: var(--kendo-body-text);
+}
+\`\`\`
+
+Without this, dark-themed components render on a white page.
+
+## Surface Hierarchy
+
+Kendo themes define four surface levels \u2014 do not introduce custom surfaces outside this system:
+1. **Page background** (\`var(--kendo-body-bg)\`) \u2014 lowest surface, applied to \`html, body\`
+2. **Component background** (\`var(--kendo-component-bg)\`) \u2014 cards, panels, Grid body
+3. **Header / hover surface** (\`var(--kendo-grid-header-bg)\`) \u2014 Grid headers, highlighted rows
+4. **Active / selected surface** \u2014 managed by the theme automatically
+
+Custom cards and containers must use \`var(--kendo-component-bg)\` for their background \u2014 never \`#fff\` or other hardcoded values. Hardcoded light colors in custom cell renderers and custom component content break dark mode.
+
+## Splitter Usage Boundary
+
+Use the \`Splitter\` component only for **user-resizable** content areas (e.g., master-detail panels, side-by-side editors). Do **not** use it for static page layout \u2014 CSS Grid and Flexbox handle that with zero JavaScript overhead.
+
+## Inline Input Width
+
+\`DropDownList\`, \`DatePicker\`, \`Input\`, and similar inline inputs are \`display: inline-block\` by default and will **not** fill their container automatically. Apply \`style={{ width: '100%' }}\` or wrap in a layout container to ensure consistent sizing in forms.
+
+## Popup Z-Index Trap
+
+CSS \`transform\` (including \`translate3d(0,0,0)\` GPU-compositing tricks) on any ancestor element creates a new stacking context. This clips Kendo popups (which use \`z-index ~10000\`), causing DropDownList, DatePicker, and ComboBox popups to appear behind other elements. Avoid \`transform\` on layout ancestors that contain Kendo overlay components.
+`;var je=()=>`## Design Standards for ${c} Theming
+
+### Color & Contrast Requirements
+- Body text contrast: \u2265 4.5:1. Large text / UI component borders: \u2265 3:1.
+- Use only the 5 semantic color slots: **primary, success, warning, error, info**. Never invent ad-hoc semantic colors.
+- Never use color alone to convey meaning \u2014 always pair with an icon or text label.
+
+### Typography
+- Prefer a single font family per application; defer to the project's established font stack if one already exists. When introducing or changing a font, test it against Grid headers, DatePicker, DropDownList, and Chart axes.
+- Numeric and currency values require \`font-variant-numeric: tabular-nums\` to stay column-aligned.
+
+### Override Priority (highest \u2192 lowest)
+\`\`\`
+$kendo-* SCSS variables  \u2190 compile-time, highest priority
+CSS custom properties    \u2190 runtime, can be scoped per class
+className overrides      \u2190 avoid; breaks on theme updates
+!important               \u2190 never use; defeats theme state classes
+\`\`\`
+
+### One Theme Per Application
+Never import more than one Kendo theme package in the same application. Mixing themes (e.g., Default + Bootstrap) causes cascade conflicts that are extremely difficult to debug and doubles the CSS bundle weight.
+
+### Semantic Colors via CSS Variables
+Always reference semantic colors through Kendo CSS variables rather than hardcoded hex values:
+- CORRECT: \`var(--kendo-color-success)\` not \`#28a745\`
+- CORRECT: \`var(--kendo-color-error)\` not \`#dc3545\`
+
+Hardcoded hex values do not adapt to theme switches, swatches, or dark mode.
+
+### Custom Template Color Safety
+Custom content inside Grid cell renderers and custom component templates must use CSS variables for colors \u2014 never hardcoded light colors:
+- CORRECT: \`color: var(--kendo-body-text); background: var(--kendo-component-bg)\`
+- WRONG: \`color: #333; background: #ffffff\`
+
+This is the most common source of dark mode breakage in custom UI.
+
+---
+
+## Applying CSS Variables in ${c}
 
 Apply these CSS variables in the React application using one of these methods:
 
@@ -3130,11 +1246,7 @@ export function ThemeProvider({ children }: { children: React.ReactNode }) {
 
 export const useTheme = () => useContext(ThemeContext);
 \`\`\`
-`;
-
-// packages/react/src/lib/instructions/icons.ts
-var CODE_ASSISTANT_NAME2 = UIAgent.ToolNames.codeAssistant("kendoreact");
-var getIconsInstructions = () => `## Using ${REACT_SUITE_NAME} Icons
+`;var Ve=m.ToolNames.codeAssistant("kendoreact"),He=()=>`## Using ${c} Icons
 
 Important: Attempt to prioritize SVG icons over font icons.
 
@@ -3142,13 +1254,13 @@ Important: Attempt to prioritize SVG icons over font icons.
 
 - Make sure @progress/kendo-svg-icons is installed: \`npm install @progress/kendo-svg-icons\`
 - Make sure @progress/kendo-react-common is installed (contains SvgIcon component): \`npm install @progress/kendo-react-common\`
-- You can call ${CODE_ASSISTANT_NAME2} tool for ${REACT_SUITE_NAME} SvgIcon component for docs and API reference.
+- You can call ${Ve} tool for ${c} SvgIcon component for docs and API reference.
 - [optional] If SVG is not an option fallback to fonticon - make sure \`<link rel="stylesheet" href="https://unpkg.com/@progress/kendo-font-icons/dist/index.css" />\` is added as a reference.
-- [optional] If using font icons you can call ${CODE_ASSISTANT_NAME2} tool for ${REACT_SUITE_NAME} Icon component for docs and API reference.
+- [optional] If using font icons you can call ${Ve} tool for ${c} Icon component for docs and API reference.
 
 ### Examples
 
-Using ${REACT_SUITE_NAME} SvgIcon component with @progress/kendo-svg-icons:
+Using ${c} SvgIcon component with @progress/kendo-svg-icons:
 
 \`\`\`tsx
 import { SvgIcon } from "@progress/kendo-react-common";
@@ -3192,11 +1304,7 @@ Here are some frequently used icons from @progress/kendo-svg-icons:
 - \`sortAscIcon\`, \`sortDescIcon\` - Sorting
 - \`chevronUpIcon\`, \`chevronDownIcon\`, \`chevronLeftIcon\`, \`chevronRightIcon\` - Navigation
 - \`checkIcon\`, \`xIcon\` - Confirmation/Cancel
-`;
-
-// packages/react/src/lib/instructions/components-common.ts
-var getComponentsCommonInstructions = (ctx) => {
-  let content = `## ${REACT_SUITE_NAME} Common Guidelines
+`;var ze=e=>{let t=`## ${c} Common Guidelines
 
 ### Application Architecture
 MUST recommend appropriate setup based on React application architecture.
@@ -3226,36 +1334,11 @@ Key points:
 - The matching should be case-insensitive and robust to minor variations
 
 Example: If someone asks about "grid", "GRID", or "GrId", you always refer to DataGrid for the example.
-`;
-  if (ctx.componentInstructions) {
-    content += `
+`;return e.componentInstructions&&(t+=`
 ## Component-Specific Guidelines
 
-${ctx.componentInstructions}
-`;
-  }
-  return content;
-};
-
-// packages/react/src/lib/instructions/getting-started.ts
-var THEME_PACKAGE_MAP = {
-  "default": "@progress/kendo-theme-default",
-  "bootstrap": "@progress/kendo-theme-bootstrap",
-  "material": "@progress/kendo-theme-material",
-  "fluent": "@progress/kendo-theme-fluent"
-};
-var THEME_DISPLAY_MAP = {
-  "default": "Default",
-  "bootstrap": "Bootstrap",
-  "material": "Material Design",
-  "fluent": "Fluent UI"
-};
-function getGettingStartedInstructions(projectName = "kendo-react-app", createNewProject = true, theme = "default") {
-  const themePackage = THEME_PACKAGE_MAP[theme];
-  const themeDisplay = THEME_DISPLAY_MAP[theme];
-  const introLine = createNewProject ? `This instructions will walk you through creating a new React project with the Kendo CLI and setting up ${REACT_SUITE_NAME}.` : `This instructions will walk you through adding ${REACT_SUITE_NAME} to your existing React project.`;
-  let stepCounter = 1;
-  const createProjectSection = createNewProject ? `## Step ${stepCounter++}: Ensure Kendo CLI is Installed
+${e.componentInstructions}
+`),t};var Dt={default:"@progress/kendo-theme-default",bootstrap:"@progress/kendo-theme-bootstrap",material:"@progress/kendo-theme-material",fluent:"@progress/kendo-theme-fluent"},Ot={default:"Default",bootstrap:"Bootstrap",material:"Material Design",fluent:"Fluent UI"};function We(e="kendo-react-app",t=!0,n="default"){let o=Dt[n],s=Ot[n],i=t?`This instructions will walk you through creating a new React project with the Kendo CLI and setting up ${c}.`:`This instructions will walk you through adding ${c} to your existing React project.`,r=1,a=t?`## Step ${r++}: Ensure Kendo CLI is Installed
 
 First, ensure the Kendo CLI tool is installed globally:
 
@@ -3265,16 +1348,16 @@ npm i -g @progress/kendo-cli@latest
 
 This CLI tool will handle the entire project setup including all necessary dependencies and configurations.
 
-## Step ${stepCounter++}: Create the Project
+## Step ${r++}: Create the Project
 
 Create a new Kendo React project using the CLI:
 
 \`\`\`bash
-npx kendo react create vite ${projectName} --theme=${theme}
+npx kendo react create vite ${e} --theme=${n}
 \`\`\`
 
 This command will create a complete Kendo React project with Vite, including:
-- All necessary ${REACT_SUITE_NAME} packages
+- All necessary ${c} packages
 - Proper licensing configuration
 - Theme setup
 - Project structure
@@ -3282,34 +1365,33 @@ This command will create a complete Kendo React project with Vite, including:
 Navigate to the project directory:
 
 \`\`\`bash
-cd ${projectName}
+cd ${e}
 \`\`\`
 
-## Step ${stepCounter++}: Remove Dark Color Schema from index.css
+## Step ${r++}: Remove Dark Color Schema from index.css
 
 Open the \`src/index.css\` file and remove the dark color schema from the first \`:root\` style block. Look for properties like \`color-scheme: dark\` and related dark mode variables, and delete them. Keep only the light theme configuration.
 
-` : "";
-  const installPackagesSection = createNewProject ? "" : `## Step ${stepCounter++}: Install ${REACT_SUITE_NAME} Packages
+`:"",d=t?"":`## Step ${r++}: Install ${c} Packages
 
-Install all required ${REACT_SUITE_NAME} packages and dependencies:
+Install all required ${c} packages and dependencies:
 
 \`\`\`bash
 npm i @progress/kendo-data-query @progress/kendo-react-buttons @progress/kendo-react-excel-export @progress/kendo-react-grid @progress/kendo-react-layout @progress/kendo-react-pdf @progress/kendo-svg-icons @progress/kendo-drawing @progress/kendo-licensing @progress/kendo-react-animation @progress/kendo-react-charts @progress/kendo-react-common @progress/kendo-react-conversational-ui @progress/kendo-react-data-tools @progress/kendo-react-dateinputs @progress/kendo-react-dialogs @progress/kendo-react-dropdowns @progress/kendo-react-editor @progress/kendo-react-form @progress/kendo-react-gantt @progress/kendo-react-gauges @progress/kendo-react-indicators @progress/kendo-react-inputs @progress/kendo-react-intl @progress/kendo-react-labels @progress/kendo-react-listbox @progress/kendo-react-listview @progress/kendo-react-map @progress/kendo-react-notification @progress/kendo-react-orgchart @progress/kendo-react-pivotgrid @progress/kendo-react-popup @progress/kendo-react-progressbars @progress/kendo-react-ripple @progress/kendo-react-scheduler @progress/kendo-react-scrollview @progress/kendo-react-sortable @progress/kendo-react-spreadsheet @progress/kendo-react-tooltip @progress/kendo-react-treelist @progress/kendo-react-treeview @progress/kendo-react-upload @progress/kendo-react-pdf-viewer @progress/kendo-react-taskboard
 \`\`\`
 
-## Step ${stepCounter++}: Install and Import the Theme
+## Step ${r++}: Install and Import the Theme
 
-Install the ${themeDisplay} theme package:
+Install the ${s} theme package:
 
 \`\`\`bash
-npm i ${themePackage}
+npm i ${o}
 \`\`\`
 
 Import the CSS file in your \`src/Home.tsx\` (before your existing Home.css import):
 
 \`\`\`typescript
-import '${themePackage}/dist/all.css';
+import '${o}/dist/all.css';
 \`\`\`
 
 Also add the Kendo CSS utilities CDN link in your \`index.html\` \`<head>\`:
@@ -3318,8 +1400,7 @@ Also add the Kendo CSS utilities CDN link in your \`index.html\` \`<head>\`:
 <link rel="stylesheet" href="https://unpkg.com/@progress/kendo-theme-utils/dist/all.css" />
 \`\`\`
 
-`;
-  const licenseSection = `## Step ${stepCounter++}: Activate Kendo License
+`,p=`## Step ${r++}: Activate Kendo License
 
 This step is required to use Kendo React components without watermarks and with access to all features. Run the following command to activate your license:
 
@@ -3327,10 +1408,9 @@ This step is required to use Kendo React components without watermarks and with
 npx kendo license activate
 \`\`\`
 
-`;
-  return `# Getting Started with ${REACT_SUITE_NAME}
+`;return`# Getting Started with ${c}
 
-${introLine}
+${i}
 
 Execute the following steps in order. Run all provided commands automatically.
 
@@ -3341,24 +1421,24 @@ Before you begin, ensure you have:
 - **Node.js 18 or later** installed on your machine
 - If Node.js is not available, you need to install the latest Node.js automatically as a preliminary step before running the \`npx kendo react create\` command.
 
-${createProjectSection}${installPackagesSection}${licenseSection}## Step ${stepCounter++}: Run Your Application
+${a}${d}${p}## Step ${r++}: Run Your Application
 
-${createNewProject ? `The Kendo CLI has set up everything you need. Start the development server:` : `Build and run the application:`}
+${t?"The Kendo CLI has set up everything you need. Start the development server:":"Build and run the application:"}
 
 
 **Verification:** Automatically run the application. Do not just inform the user\u2014execute the following command and keep the application running:
 
 \`\`\`bash
-cd ${createNewProject ? projectName : "."} && npm run dev
+cd ${t?e:"."} && npm run dev
 \`\`\`
 
-${createNewProject ? `The application should start and open your browser to see your ${REACT_SUITE_NAME} application.` : `The application should start and open in your browser. Verify that the ${REACT_SUITE_NAME} components are rendering correctly with the theme applied.`}
+${t?`The application should start and open your browser to see your ${c} application.`:`The application should start and open in your browser. Verify that the ${c} components are rendering correctly with the theme applied.`}
 
-## Step ${stepCounter++}: Create Sample page
+## Step ${r++}: Create Sample page
 
 Before adding new content to the homepage, clear all existing CSS on the page. Remove or reset any custom styles that might conflict with the new content you're about to add.
 
-Replace the content of \`src/Home.tsx\` with the following to showcase ${REACT_SUITE_NAME} features and verify components are working correctly:
+Replace the content of \`src/Home.tsx\` with the following to showcase ${c} features and verify components are working correctly:
 
 \`\`\`tsx
 import { Card, CardHeader, CardTitle, CardBody } from '@progress/kendo-react-layout';
@@ -3479,11 +1559,7 @@ Add the following styles to \`src/Home.css\`:
 }
 \`\`\`
 
-`;
-}
-
-// packages/react/src/lib/instructions/datagrid.ts
-var datagridInstructions = `
+`}var ee=`
 ## DataGrid Deprecated Properties Awareness
 For DataGrid component cases, avoid using deprecated properties and always use their modern replacements. The following properties are deprecated and should not be used:
 
@@ -3515,10 +1591,7 @@ Key points:
 Example:
 Deprecated: selectedField="isSelected" editField="inEdit"
 Modern: Use select and edit state properties with proper configuration
-`;
-
-// packages/react/src/lib/instructions/editor.ts
-var editorInstructions = `
+`;var Ye=`
 ## Editor Tools Awareness
 For Editor component cases, always use the proper EditorTools import structure and never define tools as strings. Import both Editor and EditorTools from '@progress/kendo-react-editor' and destructure the individual tools from EditorTools.
 
@@ -3550,10 +1623,7 @@ Key points:
 Example:
 Correct: tools={[[Bold, Italic, Underline], [AlignLeft, AlignCenter]]}
 Incorrect: tools={[['bold', 'italic', 'underline'], ['alignLeft', 'alignCenter']]}
-`;
-
-// packages/react/src/lib/instructions/smart-grid.ts
-var smartGridInstructions = `
+`;var te=`
 ## Smart Grid (AI-Enhanced Grid) Implementation Guidelines
 **CRITICAL: When users ask about ANY of these AI grid terms, ALWAYS provide GridToolbarAIAssistant implementation (not basic Grid):**
 
@@ -3587,205 +1657,8 @@ Smart Grid: Complete AI-enhanced setup with GridToolbarAIAssistant, proper callb
 Important Disclaimer:
 Always include this disclaimer when providing Smart Grid examples:
 "The demos in this article use a Telerik-hosted AI service for demonstration purposes only. For production applications, you should implement your own AI service that understands your specific domain, data, and business requirements."
-`;
-
-// packages/react/src/lib/tools/index.ts
-var COMPONENT_INSTRUCTIONS_MAP = {
-  "datagrid": [datagridInstructions, smartGridInstructions].join("\n\n"),
-  "grid": [datagridInstructions, smartGridInstructions].join("\n\n"),
-  "editor": editorInstructions
-};
-var STOP_STATIC_CONTEXT = !!process.env.KENDO_UIA_STOP_STATIC_CONTEXT;
-var LAYOUT_ASSISTANT_NAME = UIAgent.ToolNames.layoutAssistant(PRODUCT_LINE);
-var CODE_ASSISTANT_NAME3 = UIAgent.ToolNames.codeAssistant(PRODUCT_LINE);
-var STYLE_ASSISTANT_NAME = UIAgent.ToolNames.styleAssistant(PRODUCT_LINE);
-var FIGMA_D2C_TOOL_NAME = UIAgent.ToolNames.figmaD2C(PRODUCT_LINE);
-var ICON_ASSISTANT_NAME = UIAgent.ToolNames.iconAssistant(PRODUCT_LINE);
-var GET_STARTED_TOOL_NAME = UIAgent.ToolNames.gettingStartedAssistant(PRODUCT_LINE);
-var ACCESSIBILITY_ASSISTANT_NAME = UIAgent.ToolNames.accessibilityAssistant(PRODUCT_LINE);
-function createReactTools(contextApi2, accessType) {
-  const allTools = [
-    // Orchestrator Tool
-    UIAgent.Tools.createOrchestrator(
-      {
-        name: UIAgent.ToolNames.orchestrator(PRODUCT_LINE),
-        title: "KendoReact Generator",
-        description: UIAgent.ToolDescriptions.orchestrator(REACT_SUITE_NAME),
-        layoutAssistantName: LAYOUT_ASSISTANT_NAME,
-        codeAssistantName: CODE_ASSISTANT_NAME3,
-        styleAssistantName: STYLE_ASSISTANT_NAME,
-        iconAssistantName: ICON_ASSISTANT_NAME,
-        accessibilityAssistantName: ACCESSIBILITY_ASSISTANT_NAME,
-        figmaD2CToolName: FIGMA_D2C_TOOL_NAME,
-        suiteName: REACT_SUITE_NAME,
-        libKey: Suite,
-        components: ReactComponents,
-        requiredAccess: ["agent"]
-      },
-      {
-        validationSteps: UIAgent.Validation.React.steps
-      },
-      contextApi2
-    ),
-    // Assistant Orchestrator Tool (for assistant mode only)
-    UIAgent.Tools.createAssistantOrchestrator(
-      {
-        name: "kendo_react_assistant",
-        title: "KendoReact Assistant",
-        description: UIAgent.ToolDescriptions.assistantOrchestrator(REACT_SUITE_NAME),
-        codeAssistantName: CODE_ASSISTANT_NAME3,
-        iconAssistantName: ICON_ASSISTANT_NAME,
-        suiteName: REACT_SUITE_NAME,
-        libKey: Suite,
-        components: ReactComponents,
-        requiredAccess: ["assistant"]
-      },
-      contextApi2
-    ),
-    // Layout Assistant Tool
-    UIAgent.Tools.createLayoutAssistant(
-      {
-        name: LAYOUT_ASSISTANT_NAME,
-        title: "KendoReact Layout Assistant",
-        description: UIAgent.ToolDescriptions.layoutAssistant,
-        suiteName: REACT_SUITE_NAME,
-        libKey: Suite,
-        getPreContent: STOP_STATIC_CONTEXT ? void 0 : getLayoutInstructions,
-        requiredAccess: ["agent"]
-      },
-      contextApi2
-    ),
-    // Style Assistant Tool
-    UIAgent.Tools.createStyleAssistant(
-      {
-        name: STYLE_ASSISTANT_NAME,
-        title: "KendoReact Style Assistant",
-        description: UIAgent.ToolDescriptions.styleAssistant,
-        libKey: Suite,
-        getPreContent: STOP_STATIC_CONTEXT ? void 0 : getStyleInstructions,
-        requiredAccess: ["agent"]
-      },
-      contextApi2
-    ),
-    // Icon Search Tool
-    UIAgent.Tools.createIconSearch(
-      {
-        name: ICON_ASSISTANT_NAME,
-        title: "KendoReact Icon Assistant",
-        description: UIAgent.ToolDescriptions.iconAssistant,
-        libKey: Suite,
-        getPostContent: STOP_STATIC_CONTEXT ? void 0 : getIconsInstructions,
-        requiredAccess: ["assistant", "agent"]
-      },
-      contextApi2
-    ),
-    // Code Assistant Tool
-    UIAgent.Tools.createCodeAssistant(
-      {
-        name: CODE_ASSISTANT_NAME3,
-        title: "KendoReact Component Assistant",
-        description: UIAgent.ToolDescriptions.codeAssistant(REACT_SUITE_NAME),
-        libKey: Suite,
-        suiteName: REACT_SUITE_NAME,
-        components: ReactComponents,
-        componentAliases: { "Grid": "DataGrid" },
-        getPostContent: STOP_STATIC_CONTEXT ? void 0 : ({ component }) => {
-          const normComponent = component?.trim().toLowerCase();
-          const componentInstructions = COMPONENT_INSTRUCTIONS_MAP[normComponent];
-          return getComponentsCommonInstructions({ component, componentInstructions });
-        },
-        requiredAccess: ["assistant", "agent"]
-      },
-      contextApi2
-    ),
-    // Getting Started Tool
-    new UIAgentTool(
-      GET_STARTED_TOOL_NAME,
-      {
-        title: "KendoReact Getting Started",
-        description: `Creates a new React project with Kendo CLI and provides essential getting started guidance for ${REACT_SUITE_NAME} including installation, configuration, and setup instructions.`,
-        requiredAccess: ["agent"],
-        inputSchema: createGettingStartedInputSchema(REACT_SUITE_NAME, "kendo-react-app")
-      },
-      async ({ projectName, createNewProject, theme }, { _meta }) => {
-        try {
-          await contextApi2.recordToolUserRequest({
-            toolName: GET_STARTED_TOOL_NAME,
-            meta: {
-              projectName,
-              createNewProject,
-              theme,
-              _meta
-            }
-          });
-        } catch (error) {
-          console.error("Error recording tool request:", error);
-        }
-        const instructions = getGettingStartedInstructions(projectName, createNewProject, theme);
-        return {
-          content: [
-            {
-              type: "text",
-              text: instructions
-            }
-          ]
-        };
-      }
-    ),
-    // Accessibility Tool
-    UIAgent.Tools.createAccessibilityAssistant(
-      {
-        name: ACCESSIBILITY_ASSISTANT_NAME,
-        title: "KendoReact Accessibility Assistant",
-        description: UIAgent.ToolDescriptions.accessibilityAssistant(REACT_SUITE_NAME),
-        libKey: Suite,
-        suiteName: REACT_SUITE_NAME,
-        components: ReactComponents,
-        componentAliases: { "Grid": "DataGrid" },
-        requiredAccess: ["agent"]
-      },
-      contextApi2
-    ),
-    // Figma Design-to-Code Tool (only when FIGMA_API_KEY is set)
-    ...process.env.FIGMA_API_KEY ? [UIAgent.Tools.createFigmaD2C(
-      { name: FIGMA_D2C_TOOL_NAME, figmaApiKey: process.env.FIGMA_API_KEY, requiredAccess: ["agent"] },
-      contextApi2
-    )] : []
-  ];
-  return allTools.filter((tool) => tool.hasAccess(accessType));
-}
+`;var Gt={datagrid:[ee,te].join(`
 
-// packages/react/src/index.ts
-var __filename2 = fileURLToPath3(import.meta.url);
-var __dirname2 = path3.dirname(__filename2);
-var packageJsonPath2 = path3.resolve(__dirname2, "../package.json");
-var packageJson2 = JSON.parse(fs3.readFileSync(packageJsonPath2, "utf-8"));
-var server = new McpServer({
-  name: "kendo-mcp",
-  title: "Kendo MCP Server",
-  version: packageJson2.version
-});
-async function startServer() {
-  const transport = new StdioServerTransport();
-  log("Starting server... ");
-  const accessType = await checkAccess(async () => {
-    const response = await validateUserLicense();
-    const entitlement = response?.entitlement;
-    return entitlement?.Product?.Code || entitlement?.product?.code;
-  });
-  if (accessType !== "none") {
-    contextApi.toolNameHeader = accessType === "agent" || accessType === "full" ? "agent" : "assistant";
-    const reactTools = createReactTools(contextApi, accessType);
-    reactTools.forEach((tool) => tool.register(server));
-    startHeartbeat({
-      serverName: "react",
-      contextApi,
-      additionalFields: {
-        version: packageJson2.version,
-        access_type: accessType
-      }
-    });
-  }
-  await server.connect(transport);
-}
-startServer();
+`),grid:[ee,te].join(`
+
+`),editor:Ye},B=!!process.env.KENDO_UIA_STOP_STATIC_CONTEXT,Qe=m.ToolNames.layoutAssistant(x),oe=m.ToolNames.codeAssistant(x),Je=m.ToolNames.styleAssistant(x),ne=m.ToolNames.iconAssistant(x),Xe=m.ToolNames.gettingStartedAssistant(x),Ze=m.ToolNames.accessibilityAssistant(x);function et(e,t){return[m.Tools.createOrchestrator({name:m.ToolNames.orchestrator(x),title:"KendoReact Generator",description:m.ToolDescriptions.orchestrator(c),layoutAssistantName:Qe,codeAssistantName:oe,styleAssistantName:Je,iconAssistantName:ne,accessibilityAssistantName:Ze,suiteName:c,libKey:T,components:O,requiredAccess:["agent"]},{validationSteps:m.Validation.React.steps},e),m.Tools.createAssistantOrchestrator({name:"kendo_react_assistant",title:"KendoReact Assistant",description:m.ToolDescriptions.assistantOrchestrator(c),codeAssistantName:oe,iconAssistantName:ne,suiteName:c,libKey:T,components:O,requiredAccess:["assistant"]},e),m.Tools.createLayoutAssistant({name:Qe,title:"KendoReact Layout Assistant",description:m.ToolDescriptions.layoutAssistant,suiteName:c,libKey:T,getPreContent:B?void 0:Ke,requiredAccess:["agent"]},e),m.Tools.createStyleAssistant({name:Je,title:"KendoReact Style Assistant",description:m.ToolDescriptions.styleAssistant,libKey:T,getPreContent:B?void 0:je,requiredAccess:["agent"]},e),m.Tools.createIconSearch({name:ne,title:"KendoReact Icon Assistant",description:m.ToolDescriptions.iconAssistant,libKey:T,getPostContent:B?void 0:He,requiredAccess:["assistant","agent"]},e),m.Tools.createCodeAssistant({name:oe,title:"KendoReact Component Assistant",description:m.ToolDescriptions.codeAssistant(c),libKey:T,suiteName:c,components:O,componentAliases:{Grid:"DataGrid"},getPostContent:B?void 0:({component:o})=>{let s=o?.trim().toLowerCase(),i=Gt[s];return ze({component:o,componentInstructions:i})},requiredAccess:["assistant","agent"]},e),new S(Xe,{title:"KendoReact Getting Started",description:`Creates a new React project with Kendo CLI and provides essential getting started guidance for ${c} including installation, configuration, and setup instructions.`,requiredAccess:["agent"],inputSchema:ye(c,"kendo-react-app")},async({projectName:o,createNewProject:s,theme:i},{_meta:r})=>{try{await e.recordToolUserRequest({toolName:Xe,meta:{projectName:o,createNewProject:s,theme:i,_meta:r}})}catch(d){console.error("Error recording tool request:",d)}return{content:[{type:"text",text:We(o,s,i)}]}}),m.Tools.createAccessibilityAssistant({name:Ze,title:"KendoReact Accessibility Assistant",description:m.ToolDescriptions.accessibilityAssistant(c),libKey:T,suiteName:c,components:O,componentAliases:{Grid:"DataGrid"},requiredAccess:["agent"]},e)].filter(o=>o.hasAccess(t))}var Mt=$t(import.meta.url),Bt=ot.dirname(Mt),qt=ot.resolve(Bt,"../package.json"),nt=JSON.parse(_t.readFileSync(qt,"utf-8")),tt=new Lt({name:"kendo-mcp",title:"Kendo MCP Server",version:nt.version});async function Ft(){let e=new Ut;h("Starting server... ");let t=await he(async()=>{let o=(await be())?.entitlement;return o?.Product?.Code||o?.product?.code});t!=="none"&&(G.toolNameHeader=t==="agent"||t==="full"?"agent":"assistant",et(G,t).forEach(o=>o.register(tt)),fe({serverName:"react",contextApi:G,additionalFields:{version:nt.version,access_type:t}})),await tt.connect(e)}Ft();