@progress/kendo-react-mcp 1.8.1 → 1.10.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/index.js +127 -656
- package/package.json +4 -4
package/dist/index.js
CHANGED
|
@@ -1,52 +1,45 @@
|
|
|
1
1
|
#!/usr/bin/env node
|
|
2
|
-
import{McpServer as
|
|
3
|
-
`,
|
|
2
|
+
import{McpServer as $t}from"@modelcontextprotocol/sdk/server/mcp.js";import{StdioServerTransport as qt}from"@modelcontextprotocol/sdk/server/stdio.js";import{dirname as vt,join as Ct}from"path";import{fileURLToPath as At}from"url";import{loadLicense as it,decodeLicenseKey as lt,decodeLicenseEvidence as ct}from"@progress/kendo-licensing/utils";var z=class extends Error{constructor(t){super(t),this.name="LicenseError"}};function ne(e){return e.replace(/^\uFEFF/,"")}async function Y(e){let t=null,o=null;try{let r=it();if(!r.success){let n=new z(r.message);throw e&&await e("license_load_failed",{error:r.message}).catch(()=>{}),n}try{t=(await lt(r.value)).licenses.find(async a=>!!(await ct(a)).userId)}catch(n){console.log(n.message),e&&await e("license_load_failed",{error:n.message||"Unknown decoding error"}).catch(()=>{})}if(!t)return[ne(r.value),null]}catch(r){return o=r.message||"Unknown error loading license.",e&&await e("license_load_failed",{error:o}).catch(()=>{}),[null,o]}return[ne(t),null]}import _ from"node:fs";import j from"node:path";var V=!1,P=process.env.DEBUG_LOG_FILE,se=!!(P&&typeof P=="string");if(se){let e=j.resolve(P),t=j.dirname(e);if(t!=="."&&t!==process.cwd()&&!_.existsSync(t))try{_.mkdirSync(t,{recursive:!0})}catch(o){console.error("Error creating log directory:",o)}if(!_.existsSync(e))try{_.writeFileSync(e,"")}catch(o){console.error("Error creating log file:",o)}}else V=!1;V=se&&!!P&&_.existsSync(j.resolve(P));function v(...e){if(V&&P){let r=`${new Date().toISOString()}: ${e.join(" ")}
|
|
3
|
+
`,n=j.resolve(P);_.appendFile(n,r,a=>{a&&console.error("Error writing to log file:",a)})}}import pt from"@grpc/proto-loader";import O from"@grpc/grpc-js";import le from"path";import ae from"fs";import{fileURLToPath as ut}from"url";var mt=ut(import.meta.url),ht=le.dirname(mt),ce={version:"unknown"},ie=le.resolve(ht,"../package.json");ae.existsSync(ie)&&(ce=JSON.parse(ae.readFileSync(ie,"utf-8")));function gt(e){return e.replace(/\u2014/g,"--").replace(/\u2013/g,"-").replace(/[^\x20-\x7E]/g,"")}var W=class{constructor(t,o,r){this.contextApiUrl=t;this.protoPath=o;this.options=r;this.toolNameHeader="assistant";let n=pt.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"),v("Using ContextApi URl:",this.contextApiUrl);let a=O.loadPackageDefinition(n);this.client=new a.ContextQueryService(this.contextApiUrl||"contextapi.telerik.com:443",this.isDev?O.credentials.createInsecure():O.credentials.createSsl())}buildRequestMetadata(t={}){return gt(JSON.stringify({...t,source:"npm",version:ce.version,os:process.platform,node_version:process.version,plugin_mode:!!process.env.PLUGIN_MODE,install_source:process.env.INSTALL_SOURCE?.toLowerCase()}))}async getMetadata({meta:t}={meta:{}}){let[o,r]=this.isDev?["fake_license",null]:await Y((l,p)=>this.logEvent(l,p)),n=process.env.CONTEXTAPI_API_KEY,a=n&&typeof n=="string",s=o&&typeof o=="string";if(!s&&!a&&r)throw new Error(`Failed to authenticate with API key or License key!
|
|
4
4
|
|
|
5
|
-
License Error: ${o}`);let r=new $.Metadata;if(a)try{r.add("x-license-key",n)}catch(d){throw C("Error adding license key to metadata:",d),new Error(`Failed to use license key: ${d.message}`)}return i&&r.add("x-api-key",s),this.options?.libName&&r.add("x-library-name",this.options.libName),r.add("x-tool-name",this.toolNameHeader),r.add("x-request-metadata",this.buildRequestMetadata(t)),r}async query(t,n){let o=await this.getMetadata({meta:n});return new Promise((s,i)=>{this.client.query(t,o,(a,r)=>{a?i(new Error(a)):s(r)})})}async getApiRefMatches(t,n){let o=await this.getMetadata({meta:n});return new Promise((s,i)=>{this.client.getApiRefMatches(t,o,(a,r)=>{a?i(new Error(a)):s(r)})})}async queryCssUtils(t,n){let o=await this.getMetadata({meta:n});return new Promise((s,i)=>{this.client.cssUtilsSearch(t,o,(a,r)=>{a?(C("Error querying CSS Utils:",a),i(new Error(a))):s(r)})})}async queryIconsSearch(t,n){let o=await this.getMetadata({meta:n});return new Promise((s,i)=>{this.client.iconsSearch(t,o,(a,r)=>{a?(C("Error querying Icons Search:",a),i(new Error(a))):s(r)})})}async queryBuildingBlocks(t,n){let o=await this.getMetadata({meta:n});return new Promise((s,i)=>{this.client.buildingBlocksSearch(t,o,(a,r)=>{a?(C("Error querying Building Blocks:",a),i(new Error(a))):s(r)})})}async validateUserLicense(){let t=await this.getMetadata();return new Promise((n,o)=>{this.client.validateUserLicense(null,t,(s,i)=>{s?(C("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,(a,r)=>{a?(C("Error querying context API/GenerateTheme:",a),i(new Error(a))):s(r)})})}async recordOrchestratorUserRequest({meta:t}){let n=await this.getMetadata({meta:t});return new Promise((o,s)=>{this.client.recordOrchestratorUserRequest(null,n,(i,a)=>{i?(C("Error recording orchestrator user request:",i),s(new Error(i))):o(a)})})}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,(a,r)=>{a?(C("Error recording tool user request:",a),i(new Error(a))):s(r)})})}async logEvent(t,n,o={}){let s="h8utJ6rk4PpIWX4JMn9beQDsjVUri6KV0XYfiVwq",{enrichWithUserData:i=!1,meta:a={}}=o,r=s&&typeof s=="string",d=null;if(i)try{let[g]=this.isDev?["fake_license",null]:await z();g&&typeof g=="string"&&(d=g)}catch{}if(!r&&!d){C("Neither LOGGING_API_KEY nor license key available, skipping log event");return}let p=new $.Metadata;return r&&p.add("x-api-key",s),d&&(p.add("x-license-key",d),p.add("x-request-metadata",this.buildRequestMetadata(a)),this.options?.libName&&p.add("x-library-name",this.options.libName)),new Promise((g,b)=>{this.client.logEvent({event_name:t,fields:n||{}},p,(l,m)=>{l?(C("Error logging event:",l),b(new Error(l))):g()})})}};import{z as Q}from"zod";var mo=Q.object({user_id:Q.string(),user_email:Q.string().email()});import{z as w}from"zod";var wt=w.object({Product:w.object({Id:w.number().int(),Code:w.string(),Name:w.string()}),License:w.nullable(w.object({Id:w.number().int(),Name:w.string(),Type:w.string(),Active:w.boolean()})),Availability:w.array(w.object({LicenseStart:w.nullable(w.string().datetime()),LicenseEnd:w.nullable(w.string().datetime())})),IsLicenseAvailable:w.optional(w.boolean())}),fo=w.array(wt);function T(e,t){let n=e.server?.server.getClientVersion?.(),o=t||{};return n&&(o.clientInfo={name:n.name,version:n.version}),o}async function Ae(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 Ce(){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 St=1440*60*1e3;function ve(e){let{serverName:t,contextApi:n,additionalFields:o={},intervalMs:s=St,enrichWithUserData:i=!1}=e,a="mcp_server_heartbeat",r=async()=>{try{let p={server_name:t,timestamp:new Date().toISOString(),...o};await n.logEvent(a,p,{enrichWithUserData:i})}catch(p){C(`Failed to send heartbeat for ${t}:`,p)}};r();let d=setInterval(r,s);return()=>{clearInterval(d),C(`Heartbeat stopped for ${t}`)}}import{z as X}from"zod";var kt=["default","bootstrap","material","fluent"];function we(e,t){return{projectName:X.string().default(t).describe("The name of the project. Used as the project folder name when creating a new project."),createNewProject:X.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:X.enum(kt).default("default").describe("The Kendo UI theme to use. Determines which theme package is installed and imported.")}}var u="Kendo UI for React",N="react",D="kendo";var _=["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 Nt=xt(Tt(It(import.meta.url)),"../proto/service.proto"),F=new H("contextapi.telerik.com:443",Nt,{libName:N});var Se=async()=>F.validateUserLicense();import Vt from"fs";import ut from"path";import{fileURLToPath as Ht}from"url";import{z as v}from"zod";var k=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 q=(e,t)=>`# ${e.suiteName} - Code Validation & Quality Assurance
|
|
5
|
+
License Error: ${r}`);let i=new O.Metadata;if(s)try{i.add("x-license-key",o)}catch(l){throw v("Error adding license key to metadata:",l),new Error(`Failed to use license key: ${l.message}`)}return a&&i.add("x-api-key",n),this.options?.libName&&i.add("x-library-name",this.options.libName),i.add("x-tool-name",this.toolNameHeader),i.add("x-request-metadata",this.buildRequestMetadata(t)),i}async query(t,o){let r=await this.getMetadata({meta:o});return new Promise((n,a)=>{this.client.query(t,r,(s,i)=>{s?a(s):n(i)})})}async getApiRefMatches(t,o){let r=await this.getMetadata({meta:o});return new Promise((n,a)=>{this.client.getApiRefMatches(t,r,(s,i)=>{s?a(s):n(i)})})}async queryCssUtils(t,o){let r=await this.getMetadata({meta:o});return new Promise((n,a)=>{this.client.cssUtilsSearch(t,r,(s,i)=>{s?(v("Error querying CSS Utils:",s),a(s)):n(i)})})}async queryIconsSearch(t,o){let r=await this.getMetadata({meta:o});return new Promise((n,a)=>{this.client.iconsSearch(t,r,(s,i)=>{s?(v("Error querying Icons Search:",s),a(s)):n(i)})})}async queryBuildingBlocks(t,o){let r=await this.getMetadata({meta:o});return new Promise((n,a)=>{this.client.buildingBlocksSearch(t,r,(s,i)=>{s?(v("Error querying Building Blocks:",s),a(s)):n(i)})})}async validateUserLicense(){let t=await this.getMetadata();return new Promise((o,r)=>{this.client.validateUserLicense({},t,(n,a)=>{n?(v("Error validating user license:",n),r(n)):o(a)})})}async queryThemeGenerate(t,o){let r=await this.getMetadata({meta:o});return new Promise((n,a)=>{this.client.generateTheme(t,r,(s,i)=>{s?(v("Error querying context API/GenerateTheme:",s),a(s)):n(i)})})}async recordOrchestratorUserRequest({meta:t}){let o=await this.getMetadata({meta:t});return new Promise((r,n)=>{this.client.recordOrchestratorUserRequest({},o,(a,s)=>{a?(v("Error recording orchestrator user request:",a),n(a)):r(s)})})}async recordToolUserRequest({toolName:t,meta:o}){let r=await this.getMetadata({meta:o});return new Promise(n=>{this.client.recordToolUserRequest({tool_name:t},r,(a,s)=>{a?(a.code===7?v("recordToolUserRequest: license does not cover Kendo AI Tools, skipping telemetry."):v("Error recording tool user request:",a),n(null)):n(s)})})}async logEvent(t,o,r={}){let n="h8utJ6rk4PpIWX4JMn9beQDsjVUri6KV0XYfiVwq",{enrichWithUserData:a=!1,meta:s={}}=r,i=n&&typeof n=="string",l=null;if(a)try{let[g]=this.isDev?["fake_license",null]:await Y();g&&typeof g=="string"&&(l=g)}catch{}if(!i&&!l){v("Neither LOGGING_API_KEY nor license key available, skipping log event");return}let p=new O.Metadata;return i&&p.add("x-api-key",n),l&&(p.add("x-license-key",l),p.add("x-request-metadata",this.buildRequestMetadata(s)),this.options?.libName&&p.add("x-library-name",this.options.libName)),new Promise((g,C)=>{this.client.logEvent({event_name:t,fields:o||{}},p,(h,u)=>{h?(v("Error logging event:",h),C(h)):g()})})}};import{z as X}from"zod";var io=X.object({user_id:X.string(),user_email:X.string().email()});import{z as x}from"zod";var ft=x.object({Product:x.object({Id:x.number().int(),Code:x.string(),Name:x.string()}),License:x.nullable(x.object({Id:x.number().int(),Name:x.string(),Type:x.string(),Active:x.boolean()})),Availability:x.array(x.object({LicenseStart:x.nullable(x.string().datetime()),LicenseEnd:x.nullable(x.string().datetime())})),IsLicenseAvailable:x.optional(x.boolean())}),po=x.array(ft);function T(e,t){let o=e.server?.server.getClientVersion?.(),r=t||{};return o&&(r.clientInfo={name:o.name,version:o.version}),r}async function de(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 o=await e();return o?.toLocaleLowerCase()==="agentic_ui_generator"?"agent":o?.toLocaleLowerCase()==="ai_coding_assistants"?"assistant":"none"}function pe(){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 yt=1440*60*1e3;function ue(e){let{serverName:t,contextApi:o,additionalFields:r={},intervalMs:n=yt,enrichWithUserData:a=!1}=e,s="mcp_server_heartbeat",i=async()=>{try{let p={server_name:t,timestamp:new Date().toISOString(),...r};await o.logEvent(s,p,{enrichWithUserData:a})}catch(p){v(`Failed to send heartbeat for ${t}:`,p)}};i();let l=setInterval(i,n);return()=>{clearInterval(l),v(`Heartbeat stopped for ${t}`)}}import{z as Q}from"zod";var bt=["meridian","default","bootstrap","material","fluent"];function me(e,t){return{projectName:Q.string().default(t).describe("The name of the project. Used as the project folder name when creating a new project."),createNewProject:Q.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:Q.enum(bt).default("meridian").describe("The Kendo UI theme to use. Determines which theme package is installed and imported. Available themes: meridian (default), default, bootstrap, material, fluent.")}}var d="Kendo UI for React",I="react",D="kendo";var M=["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","SegmentedControl","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 xt=Ct(vt(At(import.meta.url)),"../proto/service.proto"),F=new W("contextapi.telerik.com:443",xt,{libName:I});var he=async()=>F.validateUserLicense();import Ot from"fs";import rt from"path";import{fileURLToPath as Mt}from"url";import{z as A}from"zod";var k=class{constructor(t,o,r){this.name=t;this.config=o;this.cb=r}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 B=e=>{let t=[`1. \`${e.accessibilityAssistantName}\`: Call first with \`includeGeneralGuidelines=true\`; use \`false\` for component-specific follow-ups.`];if(e.includeLayout){let n=e.includeResponsive?"structure, responsive behavior, and UX policy":"structure and UX policy";t.push(`${t.length+1}. \`${e.layoutAssistantName}\`: Get Kendo Design System utilities for the requested ${n}. Use only those utilities for styling and layout.`)}if(e.includeTheming&&t.push(`${t.length+1}. \`${e.styleAssistantName}\`: Generate the requested Kendo theme variables.`),e.includeIcons&&t.push(`${t.length+1}. \`${e.iconAssistantName}\`: Find icons only for the required actions and states.`),e.includeComponentsDocs){let n=e.components?.length?e.components.join(", "):"each Kendo component selected for the implementation";t.push(`${t.length+1}. \`${e.codeAssistantName}\`: Call once per component (${n}) with a concise, feature-specific query before writing Kendo markup.`)}t.push(`${t.length+1}. Implement the requested UI using ${e.suiteName} components and the gathered guidance.`),t.push(`${t.length+1}. Run \`npm run build\`, resolve failures, and repeat until it succeeds.`);let o=e.libKey==="angular"?"- Before editing, inspect the project for Standalone or NgModule setup, built-in or structural template syntax, and the existing Kendo theme import mechanism. Match those conventions; default to Standalone and built-in control flow for Angular 17+ only when no existing pattern is found.":"- Use React function components, Hooks, typed props where needed, stable list keys, and the project's existing KendoReact theme and package setup.",r=e.libKey==="angular"?`
|
|
6
|
+
- When drag-and-drop is required, consider the DragAndDrop and Sortable components.`:"";return`# ${e.suiteName} Execution Plan
|
|
6
7
|
|
|
7
|
-
|
|
8
|
-
|
|
9
|
-
|
|
10
|
-
|
|
11
|
-
|
|
12
|
-
|
|
13
|
-
|
|
14
|
-
|
|
15
|
-
|
|
16
|
-
|
|
17
|
-
-
|
|
18
|
-
|
|
19
|
-
-
|
|
20
|
-
|
|
21
|
-
|
|
22
|
-
|
|
23
|
-
-
|
|
24
|
-
|
|
25
|
-
-
|
|
26
|
-
|
|
27
|
-
|
|
28
|
-
|
|
29
|
-
|
|
30
|
-
|
|
31
|
-
|
|
32
|
-
-
|
|
33
|
-
-
|
|
34
|
-
-
|
|
35
|
-
|
|
36
|
-
|
|
37
|
-
|
|
38
|
-
|
|
39
|
-
-
|
|
40
|
-
|
|
41
|
-
-
|
|
42
|
-
|
|
43
|
-
### Validation Phase: Error Handling & Edge Cases
|
|
44
|
-
|
|
45
|
-
Error Handling:
|
|
46
|
-
- Graceful error handling for all user interactions
|
|
47
|
-
- Meaningful error messages for users
|
|
48
|
-
- Network error handling for API calls
|
|
49
|
-
`;var J=()=>`## UX/UI Design Best Practices
|
|
8
|
+
<orchestrator-plan>
|
|
9
|
+
<goal>${e.userIntent}</goal>
|
|
10
|
+
<execution-order>
|
|
11
|
+
${t.map(n=>` ${n}`).join(`
|
|
12
|
+
`)}
|
|
13
|
+
</execution-order>
|
|
14
|
+
<required-invariants>
|
|
15
|
+
- Accessibility guidance is retrieved before implementation; meet WCAG 2.2 Level AA.
|
|
16
|
+
- Do not generate code until the required tool calls above are complete and their guidance is incorporated.
|
|
17
|
+
- Use focused component queries; do not batch unrelated components.
|
|
18
|
+
- Build failures block completion and must be fixed before reporting success.
|
|
19
|
+
${o}${r}
|
|
20
|
+
</required-invariants>
|
|
21
|
+
<completion>
|
|
22
|
+
- \`npm run build\` succeeds without errors.
|
|
23
|
+
- Required Kendo component, accessibility, layout, and framework-specific requirements are implemented.
|
|
24
|
+
- Do not report completion while either condition is unresolved.
|
|
25
|
+
</completion>
|
|
26
|
+
</orchestrator-plan>`};var J=e=>{let t=e.components?.length?e.components.join(", "):"each Kendo component selected for the implementation",o=[`1. \`${e.codeAssistantName}\`: Call once per component (${t}) with a concise, feature-specific query before writing Kendo markup.`];return e.includeIcons&&o.push(`${o.length+1}. \`${e.iconAssistantName}\`: Find icons only for the required actions and states.`),o.push(`${o.length+1}. Implement using the gathered ${e.suiteName} documentation.`),o.push(`${o.length+1}. Run \`npm run build\`, resolve failures, and repeat until it succeeds.`),`# ${e.suiteName} Execution Plan
|
|
27
|
+
|
|
28
|
+
<assistant-plan>
|
|
29
|
+
<goal>${e.userIntent}</goal>
|
|
30
|
+
<execution-order>
|
|
31
|
+
${o.map(r=>` ${r}`).join(`
|
|
32
|
+
`)}
|
|
33
|
+
</execution-order>
|
|
34
|
+
<required-invariants>
|
|
35
|
+
- Build failures block completion and must be fixed before reporting success.
|
|
36
|
+
- Use the selected components and gathered guidance rather than generic substitutions.
|
|
37
|
+
</required-invariants>
|
|
38
|
+
<completion>
|
|
39
|
+
- \`npm run build\` succeeds without errors.
|
|
40
|
+
- Do not report completion while the build is failing.
|
|
41
|
+
</completion>
|
|
42
|
+
</assistant-plan>`};var $=()=>`## UX/UI Design Best Practices
|
|
50
43
|
|
|
51
44
|
> **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.
|
|
52
45
|
|
|
@@ -147,379 +140,7 @@ When no design token system is defined by the project, apply these minimum spaci
|
|
|
147
140
|
- Section separators: \u2265 24px vertical gap between distinct content areas.
|
|
148
141
|
- Card internal padding: 16\u201324px.
|
|
149
142
|
- Form field vertical gap: \u2265 16px between fields (24px for multi-column groups).
|
|
150
|
-
- Page left/right margin: 24\u201332px minimum, even at desktop widths.`;var
|
|
151
|
-
|
|
152
|
-
**Current Goal:**
|
|
153
|
-
|
|
154
|
-
${e.userIntent}
|
|
155
|
-
|
|
156
|
-
**Requirements Summary:**
|
|
157
|
-
- **Framework:** ${e.libKey}
|
|
158
|
-
${e.includeComponentsDocs?`- **Component Library:** ${e.suiteName}
|
|
159
|
-
- Ensure to use ONLY ${e.suiteName} components for all UI elements.
|
|
160
|
-
- And use the ${e.codeAssistantName} tool to get ${e.suiteName} component documentation and code snippets.
|
|
161
|
-
- 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}.
|
|
162
|
-
`:""}${e.includeLayout?`- **Layout:** Yes
|
|
163
|
-
- And use the ${e.layoutAssistantName} tool to get Kendo CSS utility classes needed for layout structure and responsive design.
|
|
164
|
-
`:""}${e.includeIcons?`- **Icons:** Yes
|
|
165
|
-
- Use icons that align with the project theme and enhance usability.
|
|
166
|
-
- Use the ${e.iconAssistantName} tool to search for icons that fit the theme and purpose of your project.
|
|
167
|
-
`:""}${e.includeTheming?`- **Custom Theming:**
|
|
168
|
-
- Create a custom theme that aligns with the current goal and branding needs.
|
|
169
|
-
- Use Kendo Themes and Design System guidelines.
|
|
170
|
-
- Make sure to include strict CSS variables or theme requirements from the current goal.
|
|
171
|
-
- And use the ${e.styleAssistantName} tool to create a custom theme for your project.
|
|
172
|
-
`:""}${e.includeResponsive?`- **Responsive:**
|
|
173
|
-
- Ensure the layout is fully responsive across mobile, tablet, and desktop views.
|
|
174
|
-
- And use the ${e.layoutAssistantName} tool to get Kendo CSS utility classes needed for responsive design.
|
|
175
|
-
`:""}
|
|
176
|
-
- **Accessible (WCAG 2.2 Level AA):**
|
|
177
|
-
- CRITICAL: You must call the ${e.accessibilityAssistantName} tool with includeGeneralGuidelines=true on your first call to get WCAG 2.2 Level AA guidelines.
|
|
178
|
-
- For subsequent calls, use includeGeneralGuidelines=false to get only component-specific accessibility information.
|
|
179
|
-
- Ensure all components meet WCAG 2.2 Level AA standards.
|
|
180
|
-
|
|
181
|
-
${e.includeLayout?`**STYLING AND LAYOUT REQUIREMENTS:**
|
|
182
|
-
## CRITICAL DESIGN SYSTEM CONSTRAINTS
|
|
183
|
-
- **USE ONLY KENDO DESIGN SYSTEM UTILITIES** for ALL styling, layout, spacing, positioning, and responsive behavior
|
|
184
|
-
- Avoid custom CSS, inline styles, or other CSS framework classes
|
|
185
|
-
- The ${e.layoutAssistantName} tool will provide the specific Kendo CSS utility classes needed
|
|
186
|
-
- All layout requirements must use Kendo utilities exclusively
|
|
187
|
-
|
|
188
|
-
`:""}---
|
|
189
|
-
|
|
190
|
-
${J()}
|
|
191
|
-
|
|
192
|
-
---
|
|
193
|
-
|
|
194
|
-
## Detailed Execution Plan
|
|
195
|
-
Follow these steps strictly in order to achieve a complete and polished implementation of the current goal:
|
|
196
|
-
|
|
197
|
-
### Phase: Accessibility Foundation
|
|
198
|
-
|
|
199
|
-
**Step 1: Retrieve WCAG 2.2 Level AA Guidelines**
|
|
200
|
-
|
|
201
|
-
**MANDATORY REQUIREMENT:**
|
|
202
|
-
|
|
203
|
-
- Before implementing any UI components or features, you must call the accessibility assistant with general guidelines
|
|
204
|
-
- On your first call to "${e.accessibilityAssistantName}", set "includeGeneralGuidelines=true" to get foundational WCAG 2.2 Level AA best practices
|
|
205
|
-
- These general guidelines apply to all components and must be considered throughout implementation
|
|
206
|
-
- For all subsequent calls, set "includeGeneralGuidelines=false" to get only component-specific information
|
|
207
|
-
|
|
208
|
-
**First tool call (includes general WCAG guidelines):**
|
|
209
|
-
\`\`\`
|
|
210
|
-
${e.accessibilityAssistantName}({
|
|
211
|
-
query="What are the accessibility requirements for [COMPONENT_NAME]?",
|
|
212
|
-
component="[COMPONENT_NAME]",
|
|
213
|
-
includeGeneralGuidelines=true // ONLY true on first call
|
|
214
|
-
})
|
|
215
|
-
\`\`\`
|
|
216
|
-
|
|
217
|
-
**Step 2: Get Component-Specific Accessibility Information**
|
|
218
|
-
|
|
219
|
-
For each additional ${e.suiteName} component you plan to use, call the tool with "includeGeneralGuidelines=false":
|
|
220
|
-
|
|
221
|
-
**Tool call example:**
|
|
222
|
-
\`\`\`
|
|
223
|
-
${e.accessibilityAssistantName}({
|
|
224
|
-
query="What are the accessibility features and requirements for [COMPONENT_NAME]? Include ARIA attributes, keyboard navigation, and screen reader support.",
|
|
225
|
-
component="[COMPONENT_NAME]",
|
|
226
|
-
includeGeneralGuidelines=false // false for all calls after the first
|
|
227
|
-
})
|
|
228
|
-
\`\`\`
|
|
229
|
-
|
|
230
|
-
**Example:**
|
|
231
|
-
\`\`\`
|
|
232
|
-
${e.accessibilityAssistantName}({
|
|
233
|
-
query="How to associate the label with another component or HTML input?",
|
|
234
|
-
component="Label",
|
|
235
|
-
includeGeneralGuidelines=false
|
|
236
|
-
})
|
|
237
|
-
\`\`\`
|
|
238
|
-
${e.includeLayout?`
|
|
239
|
-
### Phase: Layout Foundation
|
|
240
|
-
|
|
241
|
-
**Step 1: Create Base Layout Structure**
|
|
242
|
-
**IMPORTANT LAYOUT REQUIREMENTS:**
|
|
243
|
-
- Consider the hierarchy and nesting of layout elements (page \u2192 sections \u2192 components)
|
|
244
|
-
- Each layout level should have appropriate wrapper containers with proper Kendo utilities
|
|
245
|
-
- Sections should be wrapped in containers that provide the necessary layout structure
|
|
246
|
-
|
|
247
|
-
**Tool call example:**
|
|
248
|
-
\`\`\`
|
|
249
|
-
${e.layoutAssistantName}({
|
|
250
|
-
prompt="Provide Kendo Design System utility classes for the following layout structure: [LAYOUT DESCRIPTION HERE]",
|
|
251
|
-
includeBuildingBlockExamples=true // Optional, include examples of Kendo building blocks (Grid, Flex, Stack, etc.)
|
|
252
|
-
})
|
|
253
|
-
\`\`\`
|
|
254
|
-
`:""}
|
|
255
|
-
${e.includeComponentsDocs?`
|
|
256
|
-
### Phase: Component Integration
|
|
257
|
-
**Step 1: Identify and Implement Core Components**
|
|
258
|
-
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:
|
|
259
|
-
|
|
260
|
-
**Component Selection Guidelines:**
|
|
261
|
-
- **Landing Pages**: Consider Button, Card, Form components, Layout containers, Navigation elements
|
|
262
|
-
- **Dashboards**: Consider Grid, Chart, TileLayout, Drawer, Notification, ToolBar components
|
|
263
|
-
- **Data Entry**: Consider Form, TextBox, DatePicker, DropDownList, Upload, Validation components
|
|
264
|
-
- **Content Management**: Consider Grid, Editor, TreeView, FileManager, Dialog components
|
|
265
|
-
- **E-commerce**: Consider ListView, Card, Button, Rating, Badge, Carousel components
|
|
266
|
-
${o}
|
|
267
|
-
|
|
268
|
-
**IMPORTANT COMPONENT USAGE REQUIREMENTS:**
|
|
269
|
-
- Make sure to identify all necessary features related to the ${s} based on the current goal.
|
|
270
|
-
- Make sure to identify specific features needed for other ${e.suiteName} components based on the current goal.
|
|
271
|
-
- Make sure to generate a query for ${e.codeAssistantName} tool for each component and call the tool for each specific feature or functionality.
|
|
272
|
-
- 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.
|
|
273
|
-
|
|
274
|
-
**Tool call examples:**
|
|
275
|
-
\`\`\`
|
|
276
|
-
${e.codeAssistantName}({
|
|
277
|
-
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' -->
|
|
278
|
-
component="[COMPONENT_NAME]" <!-- For example: 'Grid', 'Button', 'Chart', etc. -->
|
|
279
|
-
})
|
|
280
|
-
\`\`\`
|
|
281
|
-
|
|
282
|
-
For broad queries, break them down into specific features (e.g., paging, sorting, filtering for Grid) and call the tool separately for each feature:
|
|
283
|
-
\`\`\`
|
|
284
|
-
${e.codeAssistantName}({
|
|
285
|
-
query="How to implement [SPECIFIC_FEATURE] in [COMPONENT_NAME]?" <!-- For example: 'paging in Grid' -->
|
|
286
|
-
component="[COMPONENT_NAME]" <!-- For example: 'Grid', 'Button', etc. -->
|
|
287
|
-
})
|
|
288
|
-
\`\`\`
|
|
289
|
-
|
|
290
|
-
\`\`\`
|
|
291
|
-
${e.codeAssistantName}({
|
|
292
|
-
query="How to implement [SPECIFIC_FEATURE] in [COMPONENT_NAME]?" <!-- For example: 'sorting in Grid' -->
|
|
293
|
-
component="[COMPONENT_NAME]" <!-- For example: 'Grid', 'Button', etc. -->
|
|
294
|
-
})
|
|
295
|
-
\`\`\`
|
|
296
|
-
|
|
297
|
-
\`\`\`
|
|
298
|
-
${e.codeAssistantName}({
|
|
299
|
-
query="How to implement [SPECIFIC_FEATURE] in [COMPONENT_NAME]?" <!-- For example: 'filtering in Grid' -->
|
|
300
|
-
component="[COMPONENT_NAME]" <!-- For example: 'Grid', 'Button', etc. -->
|
|
301
|
-
})
|
|
302
|
-
\`\`\`
|
|
303
|
-
`:""}
|
|
304
|
-
${e.includeResponsive?`
|
|
305
|
-
### Phase: Layout Responsive Finalization
|
|
306
|
-
|
|
307
|
-
**Step 1: Implement Responsive Behavior**
|
|
308
|
-
|
|
309
|
-
**Tool call example:**
|
|
310
|
-
\`\`\`
|
|
311
|
-
${e.layoutAssistantName}({
|
|
312
|
-
prompt="Provide Kendo Design System utility classes to make the following layout structure responsive across mobile, tablet, and desktop views: [LAYOUT DESCRIPTION HERE]",
|
|
313
|
-
includeBuildingBlockExamples=false // Optional, include examples of Kendo building blocks (Grid, Flex, Stack, etc.)
|
|
314
|
-
})
|
|
315
|
-
\`\`\`
|
|
316
|
-
`:""}
|
|
317
|
-
${e.includeTheming?`
|
|
318
|
-
**Step 2: Custom Theme Implementation**
|
|
319
|
-
|
|
320
|
-
**CUSTOM THEME REQUIREMENTS:**
|
|
321
|
-
- Create a custom theme that aligns with the current goal and branding needs.
|
|
322
|
-
- Use Kendo Themes and Design System guidelines.
|
|
323
|
-
- Make sure to include strict CSS variables or theme requirements from the current goal.
|
|
324
|
-
|
|
325
|
-
**Tool call example:**
|
|
326
|
-
\`\`\`
|
|
327
|
-
${e.styleAssistantName}({
|
|
328
|
-
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.",
|
|
329
|
-
includeThemeVariables=true // Optional, include specific CSS variables for colors, typography, spacing, etc.
|
|
330
|
-
})
|
|
331
|
-
\`\`\`
|
|
332
|
-
`:""}
|
|
333
|
-
${e.includeIcons?`
|
|
334
|
-
**Step 3: Iconography and Visual Enhancements**
|
|
335
|
-
|
|
336
|
-
**ICONOGRAPHY GUIDELINES:**
|
|
337
|
-
- Select icons that align with the project theme and enhance usability.
|
|
338
|
-
- Ensure icons are consistent in style and size.
|
|
339
|
-
- Use icons to improve navigation and highlight key actions.
|
|
340
|
-
|
|
341
|
-
**Tool call example:**
|
|
342
|
-
\`\`\`
|
|
343
|
-
${e.iconAssistantName}({
|
|
344
|
-
query="Suggest icons that fit the theme and purpose of the following current goal: [CURRENT GOAL HERE]. Provide icon names and usage context.",
|
|
345
|
-
})
|
|
346
|
-
\`\`\`
|
|
347
|
-
`:""}
|
|
348
|
-
### Phase: Code Generation
|
|
349
|
-
**IMPORTANT:** Do NOT generate ANY code or create files until ALL information gathering phases (1-3) are complete.
|
|
350
|
-
**Step 1: Generate Complete Implementation**
|
|
351
|
-
After completing all information gathering phases above, generate the complete ${e.libKey} component/page implementation:
|
|
352
|
-
**Code Generation Requirements:**
|
|
353
|
-
- Create complete, functional ${e.libKey} components/pages
|
|
354
|
-
- Include all identified ${e.suiteName} components with their configurations
|
|
355
|
-
- Apply ALL Kendo Design System utility classes gathered from layout assistant
|
|
356
|
-
- Implement proper component event handling and data binding
|
|
357
|
-
- Ensure responsive behavior using Kendo utility classes
|
|
358
|
-
- Include necessary import statements and dependencies
|
|
359
|
-
|
|
360
|
-
${t.injectedPlan??""}
|
|
361
|
-
|
|
362
|
-
### Phase: Validation and Finalization
|
|
363
|
-
|
|
364
|
-
**Step 1: Code Validation**
|
|
365
|
-
** CRITICAL REQUIREMENT: You MUST validate the generated UI code using this comprehensive checklist to ensure code quality and compliance:**
|
|
366
|
-
|
|
367
|
-
${n}
|
|
368
|
-
|
|
369
|
-
**Step 2: Final Review and Testing**
|
|
370
|
-
** Implementation Validation:**
|
|
371
|
-
${e.includeComponentsDocs?` - Components render correctly without errors
|
|
372
|
-
- Running \`npm run build\` compiles the application successfully without any build errors or crashes.
|
|
373
|
-
- All ${e.suiteName} component features function as expected
|
|
374
|
-
- Event handling and data binding operate correctly`:""}
|
|
375
|
-
${e.includeResponsive?"- Responsive layout works across breakpoints":""}
|
|
376
|
-
|
|
377
|
-
**Quick Fixes (if needed):**
|
|
378
|
-
|
|
379
|
-
After code implementation and validation you can make quick fixes as needed:
|
|
380
|
-
- If any build errors are found, fix them and re-run the application. Do NOT present the implementation as complete until the build succeeds without errors.
|
|
381
|
-
- Use ${e.codeAssistantName} for component-specific issues
|
|
382
|
-
- Use ${e.layoutAssistantName} for styling adjustments
|
|
383
|
-
|
|
384
|
-
+### Before You Begin
|
|
385
|
-
- When following/executing the plan call tools are defined from the same function_ecosystem/MCP_server which ${e.name} was called.
|
|
386
|
-
- Do NOT generate or suggest any code until all tools have been used and validated responses are incorporated.
|
|
387
|
-
- Focus on planning and sequencing.
|
|
388
|
-
- Summarize the components, layouts, and utilities gathered.
|
|
389
|
-
- Confirm all required inputs from tools have been provided.`};var Z=e=>`# ${e.suiteName} Assistant
|
|
390
|
-
|
|
391
|
-
**What you're looking for:**
|
|
392
|
-
|
|
393
|
-
${e.userIntent}
|
|
394
|
-
|
|
395
|
-
**Available Tools:**
|
|
396
|
-
- **${e.codeAssistantName}** - Get component documentation, features, and usage examples
|
|
397
|
-
- **${e.iconAssistantName}** - Search for icons from the Kendo icon library
|
|
398
|
-
|
|
399
|
-
---
|
|
400
|
-
|
|
401
|
-
## Discovery Plan
|
|
402
|
-
|
|
403
|
-
Follow these steps to find the right components and resources:
|
|
404
|
-
|
|
405
|
-
### Step 1: Identify Components
|
|
406
|
-
|
|
407
|
-
Based on your needs, consider these ${e.suiteName} component categories:
|
|
408
|
-
|
|
409
|
-
**Common Use Cases:**
|
|
410
|
-
- **Data Display**: Grid, ListView, TreeView, Card, TileLayout
|
|
411
|
-
- **Forms & Input**: Form, TextBox, DatePicker, DropDownList, ComboBox, MultiSelect, Upload
|
|
412
|
-
- **Navigation**: Menu, Drawer, Breadcrumb, TabStrip, Stepper
|
|
413
|
-
- **Data Visualization**: Chart, Gauge, Sparkline
|
|
414
|
-
- **Editing**: Editor (Rich Text)
|
|
415
|
-
- **Notifications**: Dialog, Notification, Tooltip
|
|
416
|
-
- **Layout**: Splitter, PanelBar, ExpansionPanel
|
|
417
|
-
|
|
418
|
-
**How to explore components:**
|
|
419
|
-
|
|
420
|
-
Use the ${e.codeAssistantName} tool to learn about specific components:
|
|
421
|
-
|
|
422
|
-
\`\`\`
|
|
423
|
-
${e.codeAssistantName}({
|
|
424
|
-
query: "What are the main features of [COMPONENT_NAME]?",
|
|
425
|
-
component: "[COMPONENT_NAME]"
|
|
426
|
-
})
|
|
427
|
-
\`\`\`
|
|
428
|
-
|
|
429
|
-
**Examples:**
|
|
430
|
-
\`\`\`
|
|
431
|
-
${e.codeAssistantName}({
|
|
432
|
-
query: "How to use Grid with paging and sorting?",
|
|
433
|
-
component: "Grid"
|
|
434
|
-
})
|
|
435
|
-
\`\`\`
|
|
436
|
-
|
|
437
|
-
\`\`\`
|
|
438
|
-
${e.codeAssistantName}({
|
|
439
|
-
query: "What features does DatePicker have?",
|
|
440
|
-
component: "DatePicker"
|
|
441
|
-
})
|
|
442
|
-
\`\`\`
|
|
443
|
-
|
|
444
|
-
**Pro Tips:**
|
|
445
|
-
- Ask about specific features (e.g., "Grid with filtering" instead of just "Grid")
|
|
446
|
-
- Break complex queries into multiple calls focusing on one feature at a time
|
|
447
|
-
- Specify the exact component name in the component parameter
|
|
448
|
-
|
|
449
|
-
${e.includeIcons?`
|
|
450
|
-
### Step 2: Find Icons
|
|
451
|
-
|
|
452
|
-
Use the ${e.iconAssistantName} tool to search for icons:
|
|
453
|
-
|
|
454
|
-
\`\`\`
|
|
455
|
-
${e.iconAssistantName}({
|
|
456
|
-
query: "Search for icons related to [YOUR THEME/PURPOSE]"
|
|
457
|
-
})
|
|
458
|
-
\`\`\`
|
|
459
|
-
|
|
460
|
-
**Examples:**
|
|
461
|
-
\`\`\`
|
|
462
|
-
${e.iconAssistantName}({
|
|
463
|
-
query: "icons for navigation menu"
|
|
464
|
-
})
|
|
465
|
-
\`\`\`
|
|
466
|
-
|
|
467
|
-
\`\`\`
|
|
468
|
-
${e.iconAssistantName}({
|
|
469
|
-
query: "icons for user actions like edit, delete, save"
|
|
470
|
-
})
|
|
471
|
-
\`\`\`
|
|
472
|
-
`:""}
|
|
473
|
-
|
|
474
|
-
### Step 3: Review and Implement
|
|
475
|
-
|
|
476
|
-
After gathering information:
|
|
477
|
-
1. Review the component documentation provided by ${e.codeAssistantName}
|
|
478
|
-
2. Check which icons are available from ${e.iconAssistantName}
|
|
479
|
-
3. Use the official ${e.suiteName} documentation for detailed implementation guides
|
|
480
|
-
4. Refer to the component examples and code snippets provided
|
|
481
|
-
|
|
482
|
-
### Step 4: Build and Validation
|
|
483
|
-
|
|
484
|
-
After implementing the code:
|
|
485
|
-
- Run \`npm run build\` to verify the implementation compiles successfully without any build errors.
|
|
486
|
-
- If any build errors are found, fix them and re-run the build.
|
|
487
|
-
- Use ${e.codeAssistantName} for component-specific issues.
|
|
488
|
-
- Do NOT present the implementation as complete until the build succeeds without errors.
|
|
489
|
-
|
|
490
|
-
---
|
|
491
|
-
|
|
492
|
-
## Getting Started
|
|
493
|
-
|
|
494
|
-
**Next Actions:**
|
|
495
|
-
1. Start by calling ${e.codeAssistantName} for the components you need
|
|
496
|
-
2. ${e.includeIcons?`Search for icons using ${e.iconAssistantName}`:"Review the component documentation"}
|
|
497
|
-
3. Follow the ${e.suiteName} official documentation for implementation details
|
|
498
|
-
4. Run \`npm run build\` to verify the implementation compiles successfully
|
|
499
|
-
|
|
500
|
-
**Important Notes:**
|
|
501
|
-
- These tools provide documentation and guidance, not code generation
|
|
502
|
-
- Always refer to official ${e.suiteName} documentation for the most up-to-date information
|
|
503
|
-
- Tool responses include usage examples and best practices`;var O=(e,t)=>({SETUP_VALIDATION:`
|
|
504
|
-
UI Library Setup:
|
|
505
|
-
- ${e} modules properly imported and configured
|
|
506
|
-
- ${e} theme properly loaded and applied
|
|
507
|
-
- ${e} license properly configured
|
|
508
|
-
- Globalization and localization properly configured for ${e} components
|
|
509
|
-
- Required ${e} dependencies installed and up-to-date`,PERFORMANCE_OPTIMIZATION:`
|
|
510
|
-
Performance Optimization:
|
|
511
|
-
- Efficient rendering patterns to prevent unnecessary re-renders
|
|
512
|
-
- Lazy loading of ${e} components when appropriate
|
|
513
|
-
- Virtualization enabled for large datasets in ${e} components
|
|
514
|
-
- Only required ${e} modules imported and tree-shaken`,THEME_AND_STYLING:`
|
|
515
|
-
${e} Theme & Styling:
|
|
516
|
-
- Prioritize the ${t} Design System utilities
|
|
517
|
-
- Avoid custom CSS or other framework classes
|
|
518
|
-
- Do not use inline styles
|
|
519
|
-
- Consistent ${e} theme application across all components
|
|
520
|
-
- Custom theme variables properly defined and scoped
|
|
521
|
-
- ${e} icons properly loaded and optimized
|
|
522
|
-
- Brand colors integrated with ${e} component themes`});var ee=()=>`
|
|
143
|
+
- Page left/right margin: 24\u201332px minimum, even at desktop widths.`;var Z=()=>`
|
|
523
144
|
**REQUIRED ACTIONS \u2014 apply all fixes directly to the source files:**
|
|
524
145
|
- Search all .ts files for every outdated API mentioned in the codemod output \u2014 this includes renamed or removed properties, method names, and enum values.
|
|
525
146
|
- Search all .ts, .css, and .scss files for every outdated CSS class mentioned in the codemod output and update it with an appropriate replacement.
|
|
@@ -532,91 +153,91 @@ After implementing the code:
|
|
|
532
153
|
**OUTPUT REQUIREMENTS:**
|
|
533
154
|
- For each file you change, briefly describe what was wrong and what fix you applied
|
|
534
155
|
- If a problem requires a decision from the developer that you cannot make automatically, call it out explicitly with the file path
|
|
535
|
-
- If all automated changes look correct and no further fixes are needed, explicitly confirm this`;import{execFile as
|
|
536
|
-
- Name: ${
|
|
537
|
-
- Type: ${
|
|
538
|
-
- Summary: ${
|
|
539
|
-
- Syntax: ${
|
|
540
|
-
`,
|
|
156
|
+
- If all automated changes look correct and no further fixes are needed, explicitly confirm this`;import{execFile as wt}from"child_process";import{access as kt}from"fs/promises";import{promisify as St}from"util";var ge=St(wt);function Tt(e,t){let o;try{o=JSON.parse(e)}catch{return e}let r=o?.Item;if(!r)return e;let n=[],a=r.FullName??r.Name??"",s=r.Type??"",i=r.Summary??"",l=r.SyntaxContent??"";n.push(`## API Reference Item
|
|
157
|
+
- Name: ${a}
|
|
158
|
+
- Type: ${s}
|
|
159
|
+
- Summary: ${i}
|
|
160
|
+
- Syntax: ${l}`);let p=o.RelatedItemsByType?.return_type;if(p?.length){let u=p[0].Text;u&&n.push(`- Return Type: ${u}`)}let g=r.Examples??[];if(g.length>0){let u=`## Examples
|
|
161
|
+
`,m=0;for(let b of g){let c=(b.Component??"").toLowerCase(),f=t.toLowerCase();if(c&&c!==f&&c!=="general")continue;m+=1;let w=b.Code??"";u+=`### Example ${m}
|
|
541
162
|
\`\`\`
|
|
542
|
-
${
|
|
163
|
+
${w}
|
|
543
164
|
\`\`\`
|
|
544
|
-
`}
|
|
545
|
-
${f}`)}return
|
|
546
|
-
`+
|
|
165
|
+
`}m>0&&n.push(u)}let C=o.RelatedItemsByType??{},h=[];for(let[u,m]of Object.entries(C))if(!(u==="return_type"||u==="render_fragment"))for(let b of m??[]){let c=b.FullName??"",f=b.ShortText??"";h.push(`### ${c} (${u})
|
|
166
|
+
${f}`)}return h.length>0&&n.push(`## Additional Context
|
|
167
|
+
`+h.join(`
|
|
547
168
|
---
|
|
548
|
-
`)),
|
|
169
|
+
`)),n.join(`
|
|
549
170
|
|
|
550
|
-
`)}function
|
|
551
|
-
`)||"No CSS utilities found for the given prompt.",
|
|
171
|
+
`)}function ye(e,t){let{name:o,title:r,description:n,layoutAssistantName:a,codeAssistantName:s,styleAssistantName:i,iconAssistantName:l,accessibilityAssistantName:p,suiteName:g,libKey:C,components:h}=e,u=new k(o,{title:r,description:n,requiredAccess:e.requiredAccess,inputSchema:{userIntent:A.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:A.number().min(0).max(1).default(1).describe("Confidence (0-1) to include Component Documentation assistance. Default is 1."),needsLayoutConfidence:A.number().min(0).max(1).default(0).describe("Confidence (0-1) to include Layout assistance. Default is 0."),needsStylingConfidence:A.number().min(0).max(1).default(0).describe("Confidence (0-1) to include Theming/Styling assistance. Default is 0."),needsResponsiveBehaviorConfidence:A.number().min(0).max(1).default(0).describe("Confidence (0-1) to include Responsive Behavior assistance. Default is 0."),needsIconsConfidence:A.number().min(0).max(1).default(0).describe("Confidence (0-1) to include Icons assistance. Default is 0."),componentsNeeded:A.array(A.enum(h)).optional().describe(`Optional list of specific ${g} components needed for the project.`)}},async({userIntent:m,needsComponentsDocsConfidence:b,needsLayoutConfidence:c,needsStylingConfidence:f,needsResponsiveBehaviorConfidence:w,needsIconsConfidence:S,componentsNeeded:R},{_meta:N})=>{let H=T(u,N);v("UI Orchestrator called with:",{userIntent:m,needsComponentsDocsConfidence:b,needsLayoutConfidence:c,needsStylingConfidence:f,needsResponsiveBehaviorConfidence:w,needsIconsConfidence:S});try{await t.recordOrchestratorUserRequest({meta:{userIntent:m,componentsNeeded:R,...H}})}catch(L){throw G(L)}let E=u.server?.server.getClientCapabilities?.()?.elicitation,K;if(E&&f>.3&&f<=.6){let L=await u.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"]}});L?.action==="accept"&&L.content?.includeCustomTheming&&(K=!0)}return{content:[{type:"text",text:B({name:o,userIntent:m,includeComponentsDocs:b>.3,includeTheming:f>.6||!!K,includeLayout:c>.5,includeIcons:S>.6,includeResponsive:c>.5&&w>.4,layoutAssistantName:a,codeAssistantName:s,styleAssistantName:i,iconAssistantName:l,accessibilityAssistantName:p,suiteName:g,libKey:C,components:R})}]}});return u}function be(e,t){let{name:o,title:r,description:n,iconAssistantName:a,codeAssistantName:s,suiteName:i,libKey:l,components:p}=e,g=new k(o,{title:r,description:n,inputSchema:{userIntent:A.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 ${i}.`),needsIconsConfidence:A.number().min(0).max(1).default(.7).describe("Confidence (0-1) to include Icons assistance. Default is 0.7."),componentsNeeded:A.array(A.enum(p)).optional().describe(`Optional list of specific ${i} components you want to learn about.`)},requiredAccess:e.requiredAccess},async({userIntent:C,needsIconsConfidence:h,componentsNeeded:u},{_meta:m})=>{let b=T(g,m);v("Assistant Orchestrator called with:",{userIntent:C,needsIconsConfidence:h,componentsNeeded:u});try{await t.recordOrchestratorUserRequest({meta:{userIntent:C,componentsNeeded:u,...b}})}catch(f){throw G(f)}return{content:[{type:"text",text:J({name:o,userIntent:C,includeComponentsDocs:!0,includeIcons:h>.5,codeAssistantName:s,iconAssistantName:a,suiteName:i,libKey:l,components:u})}]}});return g}function ve(e,t){let{name:o,title:r,description:n,suiteName:a,libKey:s,getPreContent:i}=e,l=new k(o,{title:r,description:n,requiredAccess:e.requiredAccess,inputSchema:{prompt:A.string().describe("An enhanced prompt describing the HTML layout structure, design requirements or specific visual effects you want to achieve."),includeBuildingBlockExamples:A.boolean().describe("Whether to include building block examples. Defaults to false.").default(!1)}},async({prompt:p,includeBuildingBlockExamples:g},{_meta:C})=>{let h=T(l,C);v("Layout Assistant called with:",{prompt:p,includeBuildingBlockExamples:g});try{let m=(await t.queryCssUtils({query:p},{...h})).values.join(`
|
|
172
|
+
`)||"No CSS utilities found for the given prompt.",b=i?.()??"",c=f=>`${b}
|
|
552
173
|
|
|
553
174
|
# Kendo Design System CSS Utilities
|
|
554
175
|
|
|
555
|
-
${
|
|
176
|
+
${m}
|
|
556
177
|
${f??""}
|
|
557
|
-
`;if(g)try{let f=await t.queryBuildingBlocks({query:p,lib_name:
|
|
178
|
+
`;if(g)try{let f=await t.queryBuildingBlocks({query:p,lib_name:s},{...h}),w="";f.items?.length>0&&(w=`
|
|
558
179
|
## Building Blocks Examples
|
|
559
180
|
|
|
560
181
|
The examples here are for demonstration purpose how CSS utils can be implemented in various building blocks.
|
|
561
182
|
However, consider your own design requirements and specifics in order to implement your templates/building blocks correctly.
|
|
562
183
|
|
|
563
|
-
${f.items.map(
|
|
564
|
-
### ${
|
|
184
|
+
${f.items.map(S=>`
|
|
185
|
+
### ${S.name}
|
|
565
186
|
|
|
566
|
-
${
|
|
187
|
+
${S.description}
|
|
567
188
|
|
|
568
189
|
\`\`\`code
|
|
569
|
-
${
|
|
190
|
+
${S.code}
|
|
570
191
|
\`\`\`
|
|
571
192
|
`).join(`
|
|
572
|
-
`)}`),
|
|
193
|
+
`)}`),m=c(w)}catch(f){v("Error calling building-blocks service:",f),m=c()}else m=c();return{content:[{type:"text",text:m}]}}catch(u){throw G(u)}});return l}function Ce(e,t){let{name:o,title:r,description:n,libKey:a,getPreContent:s}=e,i=new k(o,{title:r,description:n,requiredAccess:e.requiredAccess,inputSchema:{prompt:A.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:l},{_meta:p})=>{let g=T(i,p);v("Style Assistant called with:",{prompt:l});let C="";try{let m=await t.queryThemeGenerate({prompt:l},{...g});if(m.variables_json){let b=JSON.parse(m.variables_json),c=[];if(b)for(let f of Object.keys(b))typeof b[f]=="string"&&c.push(`${f}: ${b[f]}`);C=c.join(`
|
|
573
194
|
|
|
574
|
-
`)}}catch(
|
|
195
|
+
`)}}catch(m){throw G(m)}let h=s?.()??"";return{content:[{type:"text",text:C?`Use the following CSS variables to style the web application, including colors, typography, spacing, and component appearance.
|
|
575
196
|
Ensure the variables are applied consistently across all relevant elements.
|
|
576
197
|
Do NOT set any inline styles. CSS variables should be defined in global or component-level CSS files, or via supported theming mechanisms.
|
|
577
198
|
|
|
578
|
-
${
|
|
199
|
+
${h}
|
|
579
200
|
|
|
580
201
|
## Generated CSS Variables
|
|
581
202
|
|
|
582
203
|
\`\`\`css
|
|
583
|
-
${
|
|
204
|
+
${C}
|
|
584
205
|
\`\`\`
|
|
585
|
-
`:"No CSS variables were generated for the given prompt."}]}});return
|
|
206
|
+
`:"No CSS variables were generated for the given prompt."}]}});return i}function Ae(e,t){let{name:o,title:r,description:n,libKey:a,getPostContent:s}=e,i=new k(o,{title:r,description:n,requiredAccess:e.requiredAccess,inputSchema:{query:A.string().describe("A search query for finding icons. Be specific about the icon purpose, style, or action."),limit:A.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:l,limit:p},{_meta:g})=>{let C=T(i,g);v("Icon Search called with:",{query:l,limit:p});try{let h=await t.queryIconsSearch({query:l,limit:p*100},{...C}),u=s?.()??"";return{content:[{type:"text",text:`${h.values.join(`
|
|
586
207
|
|
|
587
208
|
`)}
|
|
588
209
|
|
|
589
|
-
${
|
|
210
|
+
${u}`}]}}catch(h){throw G(h)}});return i}function xe(e,t){let{name:o,title:r,description:n,libKey:a,suiteName:s,components:i,componentAliases:l,getPostContent:p}=e,g=new k(o,{title:r,description:n,requiredAccess:e.requiredAccess,inputSchema:{query:A.string().describe("The query to search for."),component:A.enum(i).describe("The component to search for. If not specified, use General.")}},async({query:C,component:h},{_meta:u})=>{let m=T(g,u);v("Code Assistant called with:",{query:C,component:h});let b=h;if(l){let c=l[h];c&&(b=c)}try{let f=(await t.query({query:C,component:b?.toLowerCase()??"general",lib_name:a,text_matches_count:3,code_matches_count:0,allowed_types:["documentation"]},{...m})).values.map(R=>R.replace(/\0/g,"")),w=p?.({component:h})??"";return{content:[{type:"text",text:`${f.join(`
|
|
590
211
|
|
|
591
212
|
`)}
|
|
592
213
|
|
|
593
|
-
${
|
|
214
|
+
${w}`}]}}catch(c){throw G(c)}});return g}function we(e,t){let{name:o,title:r,description:n,libKey:a,suiteName:s,components:i,componentAliases:l}=e,p=new k(o,{title:r,description:n,requiredAccess:e.requiredAccess,inputSchema:{query:A.string().describe("The query to search for."),component:A.enum(i).describe("The component to search for. If not specified, use General."),includeGeneralGuidelines:A.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:g,component:C,includeGeneralGuidelines:h},{_meta:u})=>{let m=T(p,u);v("Accessibility Assistant called with:",{query:g,component:C,includeGeneralGuidelines:h});let b=C;if(l){let c=l[C];c&&(b=c)}try{let c="";if(h){let N=pe();c+=`# WCAG 2.2 Level AA General Accessibility Guidelines
|
|
594
215
|
|
|
595
|
-
`,c+=
|
|
216
|
+
`,c+=N,c+=`
|
|
596
217
|
|
|
597
218
|
---
|
|
598
219
|
|
|
599
|
-
`}let
|
|
220
|
+
`}let R=(await t.getApiRefMatches({query:g,component:b?.toLowerCase()??"general",lib_name:a,filters_json:'{"type":{"$in":["accessibility"]}}'},{...m})).values.map(N=>N.replace(/\0/g,"")).map(N=>Tt(N,b?.toLowerCase()??"general")).join(`
|
|
600
221
|
|
|
601
|
-
`);return
|
|
222
|
+
`);return R?(h&&(c+=`# Component-Specific Accessibility Information
|
|
602
223
|
|
|
603
|
-
`),c+=
|
|
224
|
+
`),c+=R):h||(c="No component-specific accessibility guidelines found."),{content:[{type:"text",text:c}]}}catch(c){throw G(c)}});return p}function G(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.
|
|
604
225
|
|
|
605
|
-
Error Code: ${t.code} Error Message: ${t.message}`)}var
|
|
226
|
+
Error Code: ${t.code} Error Message: ${t.message}`)}var It=20*1024*1024,ke=1200*1e3;function fe(e){return{content:[{type:"text",text:`Upgrade timed out after ${ke/6e4} minutes.
|
|
606
227
|
|
|
607
228
|
**Some codemods may have already been applied to your files.** Review any modified files before proceeding.
|
|
608
229
|
|
|
609
230
|
To complete the upgrade, run this tool again with specific package names via the \`packageNames\` parameter to upgrade one package at a time.${e?`
|
|
610
231
|
|
|
611
232
|
## Partial output before timeout
|
|
612
|
-
`+e:""}`}]}}function
|
|
233
|
+
`+e:""}`}]}}function Se(e,t){let{name:o,title:r,description:n,suiteName:a,packagePrefix:s}=e,i=new k(o,{title:r,description:n,requiredAccess:e.requiredAccess,inputSchema:{workingDirectory:A.string().describe('The absolute path to the project directory where the upgrade should be executed (e.g., "/Users/username/my-app")'),packageNames:A.array(A.string()).optional().describe(`The package names to target for codemod upgrade (e.g., ["${s}grid", "${s}buttons"]). Defaults to upgrading all installed @progress packages if not specified. When specified, skips package installation and only runs codemods \u2014 the packages must already be installed at the target version before calling this tool.`),skipInstall:A.boolean().optional().describe("Skip npm package installation and only run codemods. Use this when package installation has already been done manually.")}},async({workingDirectory:l,packageNames:p,skipInstall:g},{_meta:C})=>{let h=T(i,C);try{await t.recordToolUserRequest({toolName:o,meta:h})}catch(u){console.error("Error recording tool request:",u)}try{try{await kt(l)}catch{return{content:[{type:"text",text:`The working directory does not exist: "${l}". Please provide a valid absolute path to your project.`}]}}let u=!1;try{await ge("npx",["--no","--","kendo","--version"],{cwd:l}),u=!0}catch{u=!1}let m=[],b=async(E,K=!1)=>{try{let U=!K&&u?["--no","--","kendo",...E]:["-y","@progress/kendo-cli",...E],{stdout:L,stderr:at}=await ge("npx",U,{cwd:l,maxBuffer:It,timeout:ke});return{timedOut:!1,stdout:L,stderr:at}}catch(U){return U.killed?{timedOut:!0,partialOutput:U.stdout?.trim()}:{timedOut:!1,stdout:U.stdout||"",stderr:U.stderr||U.message}}},c=["migrate",...p??[],"--codemods","--force","--ai-mode"];(g||p?.length)&&c.push("--no-install");let f=await b(c);if(f.timedOut)return fe(f.partialOutput);let w=f.stdout,S=f.stderr;if(S?.includes("Unknown argument")){let E=await b(c,!0);if(E.timedOut)return fe(E.partialOutput);w=E.stdout,S=E.stderr}S?.trim()&&m.push(`
|
|
613
234
|
Errors:
|
|
614
|
-
${S}`),
|
|
235
|
+
${S}`),w?.trim()&&m.push(w.trim());let R=w.includes("Packages installed successfully."),N=w.includes("Package installation failed:"),H=w.includes("Running codemod:");return N?m.push(`
|
|
615
236
|
## Upgrade Status
|
|
616
|
-
Package installation failed. The npm packages were not updated. Inform the user of the error and update the package versions in package.json manually to the target version. Once done, call this tool again with skipInstall set to true.`):
|
|
237
|
+
Package installation failed. The npm packages were not updated. Inform the user of the error and update the package versions in package.json manually to the target version. Once done, call this tool again with skipInstall set to true.`):R&&m.push(`
|
|
617
238
|
## Upgrade Status
|
|
618
|
-
Upgrade complete. npm packages have been installed and updated in the project.`),
|
|
619
|
-
`)}]}}catch(
|
|
239
|
+
Upgrade complete. npm packages have been installed and updated in the project.`),H&&m.push(Z()),{content:[{type:"text",text:m.join(`
|
|
240
|
+
`)}]}}catch(u){return{content:[{type:"text",text:`Error: ${u.message||u.toString()}`}]}}});return i}var Te=e=>`${e}_ui_generator`,Ie=e=>`${e}_assistant`,Re=e=>`${e}_layout_assistant`,Ne=e=>`${e}_component_assistant`,Ee=e=>`${e}_style_assistant`,De=e=>`${e}_icon_assistant`,Ue=e=>`${e}_accessibility_assistant`,Pe=e=>`${e}_getting_started_assistant`,Ge=e=>`${e}_upgrade_assistant`;var Le=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.
|
|
620
241
|
|
|
621
242
|
Use the tool when:
|
|
622
243
|
- Want to build or modify a complete page or section layout
|
|
@@ -625,7 +246,7 @@ Upgrade complete. npm packages have been installed and updated in the project.`)
|
|
|
625
246
|
- You want to enforce best practices in styling, performance, and accessibility
|
|
626
247
|
|
|
627
248
|
Returns:
|
|
628
|
-
A detailed execution plan with validated tool calls, parameters, and reasoning \u2014 ensuring consistent, high-quality UI generation.`,
|
|
249
|
+
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.
|
|
629
250
|
|
|
630
251
|
Use this tool when:
|
|
631
252
|
- You need to discover which ${e} components are suitable for a specific use case
|
|
@@ -634,20 +255,20 @@ Use this tool when:
|
|
|
634
255
|
- You want to gather component documentation and examples
|
|
635
256
|
|
|
636
257
|
Returns:
|
|
637
|
-
A focused plan for gathering component documentation and icon suggestions using the Component Assistant and Icon Assistant tools
|
|
258
|
+
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.
|
|
638
259
|
Use this tool to find the right CSS utilities for styling Kendo UI components or general web elements.
|
|
639
260
|
It analyzes the provided design context and returns relevant utility classes with explanations and examples.
|
|
640
|
-
Best suited for styling questions related to typography, spacing, colors, layout, transforms, and other utilities in the Progress/Kendo Design System.`,
|
|
261
|
+
Best suited for styling questions related to typography, spacing, colors, layout, transforms, and other utilities in the Progress/Kendo Design System.`,qe=`Generates CSS variables using an external style agent based on the user's styling prompt.
|
|
641
262
|
|
|
642
263
|
Use this tool when the user wants to:
|
|
643
264
|
- Update the visual theme of an application
|
|
644
265
|
- Modify color schemes
|
|
645
266
|
- Restyle the UI with CSS variables
|
|
646
267
|
|
|
647
|
-
The tool outputs a set of CSS variable definitions ready to be applied to style files.`,
|
|
268
|
+
The tool outputs a set of CSS variable definitions ready to be applied to style files.`,Oe=`Searches for icons in the Telerik Icons library.
|
|
648
269
|
Use this tool when the user needs to find specific icons for UI components or design elements.
|
|
649
270
|
It supports searching by icon name, category, or keyword and returns matching icons from the Telerik Icons library.
|
|
650
|
-
`,
|
|
271
|
+
`,Me=e=>`Provides answers and retrieves official documentation for ${e}.
|
|
651
272
|
|
|
652
273
|
Use this tool when the user asks about:
|
|
653
274
|
- ${e} features or capabilities
|
|
@@ -657,7 +278,7 @@ Use this tool when the user asks about:
|
|
|
657
278
|
|
|
658
279
|
Set the user's full question as the 'query' parameter.
|
|
659
280
|
If the question refers to a specific ${e} component, include its name in the 'component' parameter.
|
|
660
|
-
`,
|
|
281
|
+
`,Fe=e=>`Retrieves accessibility guidance for ${e} components with optional general WCAG 2.2 Level AA guidelines.
|
|
661
282
|
|
|
662
283
|
Use this tool when:
|
|
663
284
|
- You need component-specific accessibility information and API references
|
|
@@ -675,12 +296,12 @@ Set 'includeGeneralGuidelines=true' ONLY on the first call to include general WC
|
|
|
675
296
|
Returns:
|
|
676
297
|
- When includeGeneralGuidelines=true: General WCAG 2.2 Level AA guidelines + component-specific recommendations
|
|
677
298
|
- When includeGeneralGuidelines=false: Only component-specific accessibility recommendations
|
|
678
|
-
`,
|
|
299
|
+
`,Be=(e,t)=>`Runs codemods to upgrade ${e} code from one version directly to another using @progress/kendo-cli.
|
|
679
300
|
|
|
680
301
|
To upgrade to the latest version, call this tool directly. It handles installation automatically.
|
|
681
302
|
|
|
682
303
|
To upgrade to a specific version:
|
|
683
|
-
1. Set all
|
|
304
|
+
1. Set all ${t}* package versions to the target version (e.g. "20.0.0")
|
|
684
305
|
2. Run: npm install
|
|
685
306
|
3. Call this tool with skipInstall: true
|
|
686
307
|
|
|
@@ -700,90 +321,7 @@ Workflow:
|
|
|
700
321
|
1. Run this upgrade tool to apply codemods.
|
|
701
322
|
2. After the codemods complete, grep the project source files for every outdated value mentioned in the codemod output (e.g. old property names, renamed enum values) to find any remaining occurrences the codemod doesn't handle automatically, and fix them all.
|
|
702
323
|
3. Follow the additional instructions to complete the upgrade process.
|
|
703
|
-
`;var
|
|
704
|
-
### Angular Component Validation
|
|
705
|
-
Component Structure:
|
|
706
|
-
- Use proper @Component decorator configuration
|
|
707
|
-
- If using NgModule setup use @Component decorator with \`standalone: false\` and declare component in NgModule declarations array
|
|
708
|
-
- Correct selector naming convention (kebab-case)
|
|
709
|
-
- Appropriate template and style file organization
|
|
710
|
-
|
|
711
|
-
${te.SETUP_VALIDATION}
|
|
712
|
-
- Kendo animations module configured (if animations are used)
|
|
713
|
-
- Internationalization properly configured for Kendo components
|
|
714
|
-
|
|
715
|
-
${te.PERFORMANCE_OPTIMIZATION}
|
|
716
|
-
- OnPush change detection strategy where appropriate
|
|
717
|
-
- Efficient \`track\` expression used in \`@for\` blocks with Kendo components
|
|
718
|
-
- Minimal unnecessary change detection cycles
|
|
719
|
-
|
|
720
|
-
${te.THEME_AND_STYLING}
|
|
721
|
-
- Proper theme switching functionality (if implemented)
|
|
722
|
-
- Only ONE theme reference exists across angular.json and styles files
|
|
723
|
-
- Make sure theme import mechanism is consistent with existing project setup
|
|
724
|
-
|
|
725
|
-
Accessibility
|
|
726
|
-
- Accessibility guidelines retrieved and applied to all components`;var ne=`**Angular Specific Requirements:**
|
|
727
|
-
|
|
728
|
-
**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:
|
|
729
|
-
1. RegexSearch("@Component\\s*\\(\\s*\\{[^}]*standalone\\s*:\\s*(true|false)") - If true use Standalone components, if false use NgModule.
|
|
730
|
-
2. RegexSearch("bootstrapApplication\\s*\\(") - If found use Standalone components.
|
|
731
|
-
3. RegexSearch("bootstrapModule\\s*\\(") - If found use NgModule.
|
|
732
|
-
4. If neither is found, default to Standalone components.
|
|
733
|
-
|
|
734
|
-
**Template Syntax**: Detect which Angular template syntax the project uses and apply it consistently:
|
|
735
|
-
1. RegexSearch("@if\\s*\\(|@for\\s*\\(|@switch\\s*\\(") - If found, use built-in control flow syntax (\`@if\`, \`@for\`, \`@switch\`) in all templates.
|
|
736
|
-
2. RegexSearch("\\*ngIf|\\*ngFor|\\*ngSwitch") - If found, use structural directives (\`*ngIf\`, \`*ngFor\`, \`*ngSwitch\`) in all templates.
|
|
737
|
-
3. Do NOT mix both syntaxes in the same project.
|
|
738
|
-
4. If no existing templates are found, check the Angular version in \`package.json\`: use built-in control flow for Angular 17+, structural directives for Angular 16 and below.
|
|
739
|
-
|
|
740
|
-
**Kendo UI Theme Management Instructions for Angular**:
|
|
741
|
-
|
|
742
|
-
**Determine existing Kendo Theme/Utils package and Theme Import Mechanism**:
|
|
743
|
-
|
|
744
|
-
- Read angular.json file
|
|
745
|
-
- Look for theme/utils entries containing "@progress/kendo-theme-" in projects.[project-name].architect.build.options.styles array
|
|
746
|
-
- Read styles.css or styles.scss, or any css/scss file
|
|
747
|
-
- Look for @import statements containing "@progress/kendo-theme-" to determine existing theme/utils usage
|
|
748
|
-
- Read the application's main html file (e.g., index.html)
|
|
749
|
-
- Look for link tags containing "@progress/kendo-theme-" referencing Kendo theme/util CSS files
|
|
750
|
-
- Note which theme is found (default, material, bootstrap, or fluent)
|
|
751
|
-
- Note whether the kendo-theme-utils package is already used
|
|
752
|
-
- Note the mechanism used to include the theme (angular.json or styles file)
|
|
753
|
-
|
|
754
|
-
**Project Consistency**: Before generating or modifying any code:
|
|
755
|
-
1. Use RegexSearch to identify existing patterns in the project:
|
|
756
|
-
- Component naming conventions (e.g., "export class \\w+Component")
|
|
757
|
-
- File naming patterns (e.g., "*.component.ts", "*.service.ts")
|
|
758
|
-
- Import statement styles
|
|
759
|
-
- TypeScript configuration (strict mode, decorators, etc.)
|
|
760
|
-
2. Match the discovered patterns in all generated code
|
|
761
|
-
3. Maintain consistent formatting, indentation, and code organization with existing files
|
|
762
|
-
4. Always use the same theme import mechanism (unless user specifies otherwise)
|
|
763
|
-
`;var se=O("Kendo UI","KendoReact"),ae=`
|
|
764
|
-
### React Component Validation
|
|
765
|
-
Component Structure:
|
|
766
|
-
- Use proper function component patterns with Hooks
|
|
767
|
-
- Correct component naming convention (PascalCase)
|
|
768
|
-
- Appropriate file organization (components, hooks, utils)
|
|
769
|
-
- Props interface/type definitions where needed
|
|
770
|
-
|
|
771
|
-
${se.SETUP_VALIDATION}
|
|
772
|
-
- KendoReact license validation (if required)
|
|
773
|
-
- Appropriate bundler configuration for KendoReact packages
|
|
774
|
-
|
|
775
|
-
${se.PERFORMANCE_OPTIMIZATION}
|
|
776
|
-
- React.memo for components that receive stable props
|
|
777
|
-
- useMemo/useCallback for expensive computations and callbacks
|
|
778
|
-
- Proper key props for list rendering with KendoReact components
|
|
779
|
-
|
|
780
|
-
${se.THEME_AND_STYLING}
|
|
781
|
-
- Proper theme switching functionality (if implemented)
|
|
782
|
-
- Only ONE theme import exists across the application
|
|
783
|
-
- Make sure theme import mechanism is consistent with existing project setup
|
|
784
|
-
|
|
785
|
-
Accessibility
|
|
786
|
-
- Accessibility guidelines retrieved and applied to all components`;var Ot={createOrchestrator:xe,createAssistantOrchestrator:Ie,createLayoutAssistant:Ne,createStyleAssistant:Ee,createIconSearch:Re,createCodeAssistant:Pe,createAccessibilityAssistant:De,createUpgrade:Oe},Gt={orchestrator:Ge,assistantOrchestrator:Le,layoutAssistant:Me,codeAssistant:$e,styleAssistant:_e,iconAssistant:Fe,accessibilityAssistant:qe,gettingStartedAssistant:Be,upgradeAssistant:Ke},Lt={orchestrator:je,assistantOrchestrator:Ve,layoutAssistant:He,styleAssistant:We,iconAssistant:ze,codeAssistant:Ye,accessibilityAssistant:Qe,upgradeAssistant:Xe},Mt={Orchestrator:{render:B},Validator:{render:q},SharedValidation:{getSteps:O}},$t={Angular:{steps:oe,additionalPlan:ne},React:{steps:ae}},A={Tools:Ot,ToolNames:Gt,ToolDescriptions:Lt,Templates:Mt,Validation:$t};var _t=A.ToolNames.codeAssistant("kendoreact"),Je=()=>`# Kendo Design System Guidelines for ${u}
|
|
324
|
+
`;var Rt={createOrchestrator:ye,createAssistantOrchestrator:be,createLayoutAssistant:ve,createStyleAssistant:Ce,createIconSearch:Ae,createCodeAssistant:xe,createAccessibilityAssistant:we,createUpgrade:Se},Nt={orchestrator:Te,assistantOrchestrator:Ie,layoutAssistant:Re,codeAssistant:Ne,styleAssistant:Ee,iconAssistant:De,accessibilityAssistant:Ue,gettingStartedAssistant:Pe,upgradeAssistant:Ge},Et={orchestrator:Le,assistantOrchestrator:_e,layoutAssistant:$e,styleAssistant:qe,iconAssistant:Oe,codeAssistant:Me,accessibilityAssistant:Fe,upgradeAssistant:Be},Dt={Orchestrator:{render:B},UX:{getInstructions:$}},y={Tools:Rt,ToolNames:Nt,ToolDescriptions:Et,Templates:Dt};var Ut=y.ToolNames.codeAssistant("kendoreact"),Ke=()=>`# Kendo Design System Guidelines for ${d}
|
|
787
325
|
|
|
788
326
|
## Setting up Styles/CSS
|
|
789
327
|
|
|
@@ -810,11 +348,11 @@ Alternatively, you can also consume them directly from the Unpkg CDN.
|
|
|
810
348
|
|
|
811
349
|
## Ready-to-use Layout Components
|
|
812
350
|
|
|
813
|
-
In the ${
|
|
351
|
+
In the ${d} there are available components to create layout. Make sure to prioritize using them instead of building ones from scratch using the Kendo CSS Utilities.
|
|
814
352
|
|
|
815
|
-
For any Layout component you can also call the ${
|
|
353
|
+
For any Layout component you can also call the ${Ut} tool in order to get specific API reference and docs.
|
|
816
354
|
|
|
817
|
-
- ${
|
|
355
|
+
- ${d} Card component.
|
|
818
356
|
- Generally, it is recommended to use 100% width (e.g., \`<Card style={{ width: '100%' }}>\`)
|
|
819
357
|
- If needed, use specific width based on the layout requirements (e.g., \`<Card style={{ width: '150px' }}>\`)
|
|
820
358
|
- 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.
|
|
@@ -920,7 +458,7 @@ Use the \`Splitter\` component only for **user-resizable** content areas (e.g.,
|
|
|
920
458
|
## Popup Z-Index Trap
|
|
921
459
|
|
|
922
460
|
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.
|
|
923
|
-
`;var
|
|
461
|
+
`;var je=()=>`## Design Standards for ${d} Theming
|
|
924
462
|
|
|
925
463
|
### Color & Contrast Requirements
|
|
926
464
|
- Body text contrast: \u2265 4.5:1. Large text / UI component borders: \u2265 3:1.
|
|
@@ -958,7 +496,7 @@ This is the most common source of dark mode breakage in custom UI.
|
|
|
958
496
|
|
|
959
497
|
---
|
|
960
498
|
|
|
961
|
-
## Applying CSS Variables in ${
|
|
499
|
+
## Applying CSS Variables in ${d}
|
|
962
500
|
|
|
963
501
|
Apply these CSS variables in the React application using one of these methods:
|
|
964
502
|
|
|
@@ -1047,7 +585,7 @@ export function ThemeProvider({ children }: { children: React.ReactNode }) {
|
|
|
1047
585
|
|
|
1048
586
|
export const useTheme = () => useContext(ThemeContext);
|
|
1049
587
|
\`\`\`
|
|
1050
|
-
`;var
|
|
588
|
+
`;var We=y.ToolNames.codeAssistant("kendoreact"),He=()=>`## Using ${d} Icons
|
|
1051
589
|
|
|
1052
590
|
Important: Attempt to prioritize SVG icons over font icons.
|
|
1053
591
|
|
|
@@ -1055,13 +593,13 @@ Important: Attempt to prioritize SVG icons over font icons.
|
|
|
1055
593
|
|
|
1056
594
|
- Make sure @progress/kendo-svg-icons is installed: \`npm install @progress/kendo-svg-icons\`
|
|
1057
595
|
- Make sure @progress/kendo-react-common is installed (contains SvgIcon component): \`npm install @progress/kendo-react-common\`
|
|
1058
|
-
- You can call ${
|
|
596
|
+
- You can call ${We} tool for ${d} SvgIcon component for docs and API reference.
|
|
1059
597
|
- [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.
|
|
1060
|
-
- [optional] If using font icons you can call ${
|
|
598
|
+
- [optional] If using font icons you can call ${We} tool for ${d} Icon component for docs and API reference.
|
|
1061
599
|
|
|
1062
600
|
### Examples
|
|
1063
601
|
|
|
1064
|
-
Using ${
|
|
602
|
+
Using ${d} SvgIcon component with @progress/kendo-svg-icons:
|
|
1065
603
|
|
|
1066
604
|
\`\`\`tsx
|
|
1067
605
|
import { SvgIcon } from "@progress/kendo-react-common";
|
|
@@ -1105,87 +643,18 @@ Here are some frequently used icons from @progress/kendo-svg-icons:
|
|
|
1105
643
|
- \`sortAscIcon\`, \`sortDescIcon\` - Sorting
|
|
1106
644
|
- \`chevronUpIcon\`, \`chevronDownIcon\`, \`chevronLeftIcon\`, \`chevronRightIcon\` - Navigation
|
|
1107
645
|
- \`checkIcon\`, \`xIcon\` - Confirmation/Cancel
|
|
1108
|
-
`;var
|
|
1109
|
-
|
|
1110
|
-
### Application Architecture
|
|
1111
|
-
MUST recommend appropriate setup based on React application architecture.
|
|
1112
|
-
|
|
1113
|
-
Implementation Patterns:
|
|
1114
|
-
- Function components with Hooks (Recommended): Use modern React patterns
|
|
1115
|
-
- Class components: Support when needed for legacy code
|
|
1116
|
-
- When architecture is unclear: Default to function components with Hooks
|
|
1117
|
-
|
|
1118
|
-
### Package Installation
|
|
1119
|
-
Always use minimal, targeted package installation.
|
|
646
|
+
`;var ze=e=>{let t=`## ${d} Implementation Rules
|
|
1120
647
|
|
|
1121
|
-
|
|
1122
|
-
|
|
1123
|
-
|
|
1124
|
-
|
|
1125
|
-
|
|
1126
|
-
Example: \`npm install @progress/kendo-react-grid @progress/kendo-data-query\`
|
|
1127
|
-
|
|
1128
|
-
### Component Awareness
|
|
1129
|
-
Whenever a component name is mentioned\u2014regardless of how it's written (all lowercase, all uppercase, mixed case, separate words, or even with typos)\u2014you should always look up the correct example from the corresponding component.
|
|
1130
|
-
|
|
1131
|
-
Key points:
|
|
1132
|
-
- Match component names case-insensitively and robustly to minor variations
|
|
1133
|
-
- If someone refers to a component (e.g., "button", "BUTTON", "BuTtOn"), match it to the correct component (Button)
|
|
1134
|
-
- After matching, use the example or information associated with that component
|
|
1135
|
-
- The matching should be case-insensitive and robust to minor variations
|
|
1136
|
-
|
|
1137
|
-
Example: If someone asks about "grid", "GRID", or "GrId", you always refer to DataGrid for the example.
|
|
1138
|
-
|
|
1139
|
-
### TypeScript Strictness
|
|
1140
|
-
All generated code MUST compile under strict TypeScript.
|
|
1141
|
-
|
|
1142
|
-
Rules:
|
|
1143
|
-
- Define a TypeScript \`interface\` or \`type\` for every source record / data shape
|
|
1144
|
-
- Type every event, render, and callback parameter using the component's exported types
|
|
1145
|
-
- Never use \`any\`, \`as any\`, \`as number\`, or any other unsafe cast
|
|
1146
|
-
- No implicit \`any\` in callback parameters (e.g. avoid \`(e) => ...\` without a type)
|
|
1147
|
-
- Prefer the narrowest correct type from the package's public types
|
|
1148
|
-
|
|
1149
|
-
### Import Hygiene
|
|
1150
|
-
Keep imports minimal, explicit, and side-effect free.
|
|
1151
|
-
|
|
1152
|
-
Rules:
|
|
1153
|
-
- Use NAMED imports only from \`@progress/kendo-react-*\` packages
|
|
1154
|
-
- No side-effect imports (e.g. \`import "@progress/kendo-react-xxx"\`, \`import "hammerjs"\`)
|
|
1155
|
-
- Import only the subcomponents actually used in the generated code
|
|
1156
|
-
- No unused imports
|
|
1157
|
-
|
|
1158
|
-
### Data and State Quality
|
|
1159
|
-
Keep data flow predictable and resilient.
|
|
1160
|
-
|
|
1161
|
-
Rules:
|
|
1162
|
-
- Use a single typed dataset per logical concept; derive multiple views from one source
|
|
1163
|
-
- Memoize derived datasets with \`useMemo\` when the source data is dynamic
|
|
1164
|
-
- Render a graceful empty state for empty / invalid data instead of a broken component
|
|
1165
|
-
- Prefer function components with Hooks for new code
|
|
1166
|
-
|
|
1167
|
-
### API Correctness
|
|
1168
|
-
Only emit current, runnable KendoReact APIs.
|
|
1169
|
-
|
|
1170
|
-
Rules:
|
|
1171
|
-
- Do not invent props, components, or methods \u2014 verify against the installed package
|
|
1172
|
-
- Do not use deprecated APIs when a current replacement exists
|
|
1173
|
-
- Match prop names and casing exactly as exported by the package
|
|
1174
|
-
|
|
1175
|
-
|
|
1176
|
-
### Mandatory Pre-Output Self-Check
|
|
1177
|
-
Before emitting code, internally verify ALL of the following. If ANY fails, fix and re-check:
|
|
1178
|
-
- [ ] All callbacks and event handlers are typed (no implicit \`any\`, no unsafe casts)
|
|
1179
|
-
- [ ] Only NAMED imports from \`@progress/kendo-react-*\` (no side-effect imports)
|
|
1180
|
-
- [ ] No \`any\`, \`as any\`, or \`as number\` anywhere
|
|
1181
|
-
- [ ] No deprecated or invented APIs
|
|
1182
|
-
- [ ] Source data shape is defined as a TypeScript \`interface\` / \`type\`
|
|
1183
|
-
- [ ] Component-specific guidelines below (if any) are satisfied
|
|
648
|
+
- Follow the project's existing React and ${d} setup; use function components and Hooks for new code.
|
|
649
|
+
- Before using a component, confirm its required ${d} package is already declared in the project. Install only missing, required packages using the project's approved package-management workflow.
|
|
650
|
+
- Keep imports named, minimal, and limited to packages and subcomponents actually used. Do not use side-effect imports or leave unused imports.
|
|
651
|
+
- Compile under strict TypeScript: define source-data types; type component events, render callbacks, and handlers with exported types; do not use \`any\` or unsafe casts.
|
|
652
|
+
- Keep data flow predictable and render a graceful empty state for invalid or empty data.
|
|
1184
653
|
`;return e.componentInstructions&&(t+=`
|
|
1185
654
|
## Component-Specific Guidelines
|
|
1186
655
|
|
|
1187
656
|
${e.componentInstructions}
|
|
1188
|
-
`),t};var
|
|
657
|
+
`),t};var Pt={meridian:"@progress/kendo-theme-meridian",default:"@progress/kendo-theme-default",bootstrap:"@progress/kendo-theme-bootstrap",material:"@progress/kendo-theme-material",fluent:"@progress/kendo-theme-fluent"},Gt={meridian:"Meridian",default:"Default",bootstrap:"Bootstrap",material:"Material Design",fluent:"Fluent UI"};function Ye(e="kendo-react-app",t=!0,o="meridian"){let r=Pt[o],n=Gt[o],a=t?`This instructions will walk you through creating a new React project with the Kendo CLI and setting up ${d}.`:`This instructions will walk you through adding ${d} to your existing React project.`,s=1,i=t?`## Step ${s++}: Ensure Kendo CLI is Installed
|
|
1189
658
|
|
|
1190
659
|
First, ensure the Kendo CLI tool is installed globally:
|
|
1191
660
|
|
|
@@ -1195,16 +664,16 @@ npm i -g @progress/kendo-cli@latest
|
|
|
1195
664
|
|
|
1196
665
|
This CLI tool will handle the entire project setup including all necessary dependencies and configurations.
|
|
1197
666
|
|
|
1198
|
-
## Step ${
|
|
667
|
+
## Step ${s++}: Create the Project
|
|
1199
668
|
|
|
1200
669
|
Create a new Kendo React project using the CLI:
|
|
1201
670
|
|
|
1202
671
|
\`\`\`bash
|
|
1203
|
-
npx kendo react create vite ${e} --theme=${
|
|
672
|
+
npx kendo react create vite ${e} --theme=${o}
|
|
1204
673
|
\`\`\`
|
|
1205
674
|
|
|
1206
675
|
This command will create a complete Kendo React project with Vite, including:
|
|
1207
|
-
- All necessary ${
|
|
676
|
+
- All necessary ${d} packages
|
|
1208
677
|
- Proper licensing configuration
|
|
1209
678
|
- Theme setup
|
|
1210
679
|
- Project structure
|
|
@@ -1215,30 +684,30 @@ Navigate to the project directory:
|
|
|
1215
684
|
cd ${e}
|
|
1216
685
|
\`\`\`
|
|
1217
686
|
|
|
1218
|
-
## Step ${
|
|
687
|
+
## Step ${s++}: Remove Dark Color Schema from index.css
|
|
1219
688
|
|
|
1220
689
|
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.
|
|
1221
690
|
|
|
1222
|
-
`:"",
|
|
691
|
+
`:"",l=t?"":`## Step ${s++}: Install ${d} Packages
|
|
1223
692
|
|
|
1224
|
-
Install all required ${
|
|
693
|
+
Install all required ${d} packages and dependencies:
|
|
1225
694
|
|
|
1226
695
|
\`\`\`bash
|
|
1227
696
|
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
|
|
1228
697
|
\`\`\`
|
|
1229
698
|
|
|
1230
|
-
## Step ${
|
|
699
|
+
## Step ${s++}: Install and Import the Theme
|
|
1231
700
|
|
|
1232
|
-
Install the ${
|
|
701
|
+
Install the ${n} theme package:
|
|
1233
702
|
|
|
1234
703
|
\`\`\`bash
|
|
1235
|
-
npm i ${
|
|
704
|
+
npm i ${r}
|
|
1236
705
|
\`\`\`
|
|
1237
706
|
|
|
1238
707
|
Import the CSS file in your \`src/Home.tsx\` (before your existing Home.css import):
|
|
1239
708
|
|
|
1240
709
|
\`\`\`typescript
|
|
1241
|
-
import '${
|
|
710
|
+
import '${r}/dist/all.css';
|
|
1242
711
|
\`\`\`
|
|
1243
712
|
|
|
1244
713
|
Also add the Kendo CSS utilities CDN link in your \`index.html\` \`<head>\`:
|
|
@@ -1247,7 +716,7 @@ Also add the Kendo CSS utilities CDN link in your \`index.html\` \`<head>\`:
|
|
|
1247
716
|
<link rel="stylesheet" href="https://unpkg.com/@progress/kendo-theme-utils/dist/all.css" />
|
|
1248
717
|
\`\`\`
|
|
1249
718
|
|
|
1250
|
-
`,p=`## Step ${
|
|
719
|
+
`,p=`## Step ${s++}: Activate Kendo License
|
|
1251
720
|
|
|
1252
721
|
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:
|
|
1253
722
|
|
|
@@ -1255,9 +724,9 @@ This step is required to use Kendo React components without watermarks and with
|
|
|
1255
724
|
npx kendo license activate
|
|
1256
725
|
\`\`\`
|
|
1257
726
|
|
|
1258
|
-
`;return`# Getting Started with ${
|
|
727
|
+
`;return`# Getting Started with ${d}
|
|
1259
728
|
|
|
1260
|
-
${
|
|
729
|
+
${a}
|
|
1261
730
|
|
|
1262
731
|
Execute the following steps in order. Run all provided commands automatically.
|
|
1263
732
|
|
|
@@ -1268,7 +737,7 @@ Before you begin, ensure you have:
|
|
|
1268
737
|
- **Node.js 18 or later** installed on your machine
|
|
1269
738
|
- 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.
|
|
1270
739
|
|
|
1271
|
-
${
|
|
740
|
+
${i}${l}${p}## Step ${s++}: Run Your Application
|
|
1272
741
|
|
|
1273
742
|
${t?"The Kendo CLI has set up everything you need. Start the development server:":"Build and run the application:"}
|
|
1274
743
|
|
|
@@ -1279,13 +748,13 @@ ${t?"The Kendo CLI has set up everything you need. Start the development server:
|
|
|
1279
748
|
cd ${t?e:"."} && npm run dev
|
|
1280
749
|
\`\`\`
|
|
1281
750
|
|
|
1282
|
-
${t?`The application should start and open your browser to see your ${
|
|
751
|
+
${t?`The application should start and open your browser to see your ${d} application.`:`The application should start and open in your browser. Verify that the ${d} components are rendering correctly with the theme applied.`}
|
|
1283
752
|
|
|
1284
|
-
## Step ${
|
|
753
|
+
## Step ${s++}: Create Sample page
|
|
1285
754
|
|
|
1286
755
|
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.
|
|
1287
756
|
|
|
1288
|
-
Replace the content of \`src/Home.tsx\` with the following to showcase ${
|
|
757
|
+
Replace the content of \`src/Home.tsx\` with the following to showcase ${d} features and verify components are working correctly:
|
|
1289
758
|
|
|
1290
759
|
\`\`\`tsx
|
|
1291
760
|
import { Card, CardHeader, CardTitle, CardBody } from '@progress/kendo-react-layout';
|
|
@@ -1406,7 +875,7 @@ Add the following styles to \`src/Home.css\`:
|
|
|
1406
875
|
}
|
|
1407
876
|
\`\`\`
|
|
1408
877
|
|
|
1409
|
-
`}var
|
|
878
|
+
`}var Ve=`
|
|
1410
879
|
## KendoReact Chart Reliability Instructions
|
|
1411
880
|
Applies to ALL KendoReact chart types. Generate only current, runnable KendoReact Chart APIs with strongly typed data. You MUST follow every rule in addition to the common guidelines. If any rule cannot be satisfied, fix and re-check before emitting code.
|
|
1412
881
|
|
|
@@ -1548,7 +1017,7 @@ const pieLabel = (e: { category?: string; percentage?: number }) =>
|
|
|
1548
1017
|
|
|
1549
1018
|
### 11. Expected output behavior
|
|
1550
1019
|
- The generated page MUST compile under strict TypeScript and render the requested chart(s) with correct data shape, required axes/labels for the chosen series family, formatted tooltips/labels, and no forbidden patterns.
|
|
1551
|
-
`;var
|
|
1020
|
+
`;var ee=`
|
|
1552
1021
|
## DataGrid Deprecated Properties Awareness
|
|
1553
1022
|
For DataGrid component cases, avoid using deprecated properties and always use their modern replacements. The following properties are deprecated and should not be used:
|
|
1554
1023
|
|
|
@@ -1580,7 +1049,7 @@ Key points:
|
|
|
1580
1049
|
Example:
|
|
1581
1050
|
Deprecated: selectedField="isSelected" editField="inEdit"
|
|
1582
1051
|
Modern: Use select and edit state properties with proper configuration
|
|
1583
|
-
`;var
|
|
1052
|
+
`;var Xe=`
|
|
1584
1053
|
## Editor Tools Awareness
|
|
1585
1054
|
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.
|
|
1586
1055
|
|
|
@@ -1612,7 +1081,7 @@ Key points:
|
|
|
1612
1081
|
Example:
|
|
1613
1082
|
Correct: tools={[[Bold, Italic, Underline], [AlignLeft, AlignCenter]]}
|
|
1614
1083
|
Incorrect: tools={[['bold', 'italic', 'underline'], ['alignLeft', 'alignCenter']]}
|
|
1615
|
-
`;var
|
|
1084
|
+
`;var te=`
|
|
1616
1085
|
## Smart Grid (AI-Enhanced Grid) Implementation Guidelines
|
|
1617
1086
|
**CRITICAL: When users ask about ANY of these AI grid terms, ALWAYS provide GridToolbarAIAssistant implementation (not basic Grid):**
|
|
1618
1087
|
|
|
@@ -1646,8 +1115,10 @@ Smart Grid: Complete AI-enhanced setup with GridToolbarAIAssistant, proper callb
|
|
|
1646
1115
|
Important Disclaimer:
|
|
1647
1116
|
Always include this disclaimer when providing Smart Grid examples:
|
|
1648
1117
|
"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."
|
|
1649
|
-
`;var
|
|
1118
|
+
`;var Lt={datagrid:[ee,te].join(`
|
|
1119
|
+
|
|
1120
|
+
`),grid:[ee,te].join(`
|
|
1650
1121
|
|
|
1651
|
-
`),
|
|
1122
|
+
`),editor:Xe,chart:Ve},q=!!process.env.PLUGIN_MODE,Qe=y.ToolNames.layoutAssistant(D),oe=y.ToolNames.codeAssistant(D),Je=y.ToolNames.styleAssistant(D),re=y.ToolNames.iconAssistant(D),Ze=y.ToolNames.gettingStartedAssistant(D),et=y.ToolNames.accessibilityAssistant(D),_t=y.ToolNames.upgradeAssistant(D);function tt(e,t){return[...q?[]:[y.Tools.createOrchestrator({name:y.ToolNames.orchestrator(D),title:"KendoReact Generator",description:y.ToolDescriptions.orchestrator(d),layoutAssistantName:Qe,codeAssistantName:oe,styleAssistantName:Je,iconAssistantName:re,accessibilityAssistantName:et,suiteName:d,libKey:I,components:M,requiredAccess:["agent"]},e),y.Tools.createAssistantOrchestrator({name:"kendo_react_assistant",title:"KendoReact Assistant",description:y.ToolDescriptions.assistantOrchestrator(d),codeAssistantName:oe,iconAssistantName:re,suiteName:d,libKey:I,components:M,requiredAccess:["assistant"]},e)],y.Tools.createLayoutAssistant({name:Qe,title:"KendoReact Layout Assistant",description:y.ToolDescriptions.layoutAssistant,suiteName:d,libKey:I,getPreContent:q?void 0:()=>`${Ke()}
|
|
1652
1123
|
|
|
1653
|
-
|
|
1124
|
+
${$()}`,requiredAccess:["agent"]},e),y.Tools.createStyleAssistant({name:Je,title:"KendoReact Style Assistant",description:y.ToolDescriptions.styleAssistant,libKey:I,getPreContent:q?void 0:je,requiredAccess:["agent"]},e),y.Tools.createIconSearch({name:re,title:"KendoReact Icon Assistant",description:y.ToolDescriptions.iconAssistant,libKey:I,getPostContent:q?void 0:He,requiredAccess:["assistant","agent"]},e),y.Tools.createCodeAssistant({name:oe,title:"KendoReact Component Assistant",description:y.ToolDescriptions.codeAssistant(d),libKey:I,suiteName:d,components:M,componentAliases:{Grid:"DataGrid"},getPostContent:q?void 0:({component:r})=>{let n=r?.trim().toLowerCase(),a=Lt[n];return ze({component:r,componentInstructions:a})},requiredAccess:["assistant","agent"]},e),...q?[]:[(()=>{let r=new k(Ze,{title:"KendoReact Getting Started",description:`Creates a new React project with Kendo CLI and provides essential getting started guidance for ${d} including installation, configuration, and setup instructions.`,requiredAccess:["agent"],inputSchema:me(d,"kendo-react-app")},async({projectName:n,createNewProject:a,theme:s},{_meta:i})=>{let l=T(r,i);try{await e.recordToolUserRequest({toolName:Ze,meta:{projectName:n,createNewProject:a,theme:s,...l}})}catch(g){console.error("Error recording tool request:",g)}return{content:[{type:"text",text:Ye(n,a,s)}]}});return r})()],y.Tools.createAccessibilityAssistant({name:et,title:"KendoReact Accessibility Assistant",description:y.ToolDescriptions.accessibilityAssistant(d),libKey:I,suiteName:d,components:M,componentAliases:{Grid:"DataGrid"},requiredAccess:["agent"]},e),y.Tools.createUpgrade({name:_t,title:"KendoReact Upgrade Assistant",description:y.ToolDescriptions.upgradeAssistant(d,"@progress/kendo-react-"),suiteName:d,packagePrefix:"@progress/kendo-react-",requiredAccess:["agent"]},e)].filter(r=>r.hasAccess(t))}var Ft=Mt(import.meta.url),Bt=rt.dirname(Ft),Kt=rt.resolve(Bt,"../package.json"),nt=JSON.parse(Ot.readFileSync(Kt,"utf-8")),ot=new $t({name:"kendo-mcp",title:"Kendo MCP Server",version:nt.version});async function jt(){let e=new qt;v("Starting server... ");let t=await de(async()=>{let r=(await he())?.entitlement;return r?.Product?.Code||r?.product?.code});t!=="none"&&(F.toolNameHeader=t==="agent"||t==="full"?"agent":"assistant",tt(F,t).forEach(r=>r.register(ot)),ue({serverName:"react",contextApi:F,enrichWithUserData:!0,additionalFields:{version:nt.version,access_type:t}})),await ot.connect(e)}jt();
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@progress/kendo-react-mcp",
|
|
3
|
-
"version": "1.
|
|
3
|
+
"version": "1.10.1",
|
|
4
4
|
"type": "module",
|
|
5
5
|
"bin": "./dist/index.js",
|
|
6
6
|
"license": "See LICENSE.md",
|
|
@@ -24,10 +24,10 @@
|
|
|
24
24
|
"!**/*.tsbuildinfo"
|
|
25
25
|
],
|
|
26
26
|
"dependencies": {
|
|
27
|
-
"@grpc/grpc-js": "^1.14.
|
|
27
|
+
"@grpc/grpc-js": "^1.14.4",
|
|
28
28
|
"@grpc/proto-loader": "^0.8.1",
|
|
29
|
-
"@modelcontextprotocol/sdk": "^1.
|
|
30
|
-
"@progress/kendo-licensing": "^1.11.
|
|
29
|
+
"@modelcontextprotocol/sdk": "^1.30.0",
|
|
30
|
+
"@progress/kendo-licensing": "^1.11.2",
|
|
31
31
|
"tslib": "^2.3.0"
|
|
32
32
|
},
|
|
33
33
|
"devDependencies": {
|