一键在 Manus 中运行任何 Skill

kendo-react-getting-started

星标0

分支0

更新时间2026年5月18日 12:21

Creates a new KendoReact project from scratch or adds KendoReact to an existing project. Use when the user wants to set up, scaffold, bootstrap, or get started with a React application using KendoReact. Trigger on "create new React project", "set up KendoReact", "add KendoReact to my app", "scaffold React with Kendo", "getting started with KendoReact", "bootstrap React project", "install kendo-react".

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

telerik

telerik/ai-plugins

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

KendoReact — Getting Started

Arguments

Usage: /kendo-react-getting-started [mode] [project-name] [--theme=<theme>]

[mode]: new (default) — create a brand-new project with the Kendo CLI, or existing — add KendoReact to an existing project
[project-name]: The name for your project (default: kendo-react-app). Only used in new mode.
[--theme=<theme>]: One of default (default), bootstrap, material, fluent

Instructions

Determine the mode from $ARGUMENTS:
- If $ARGUMENTS contains existing, add, existing-project, or add-to-existing (case-insensitive) → read and follow existing-project.md
- Otherwise → read and follow new-project.md (this is the default)
Extract the project name from $ARGUMENTS. If no name is provided, use kendo-react-app.
Extract the theme from $ARGUMENTS (e.g., --theme=bootstrap). If no theme is provided, use default.
Replace every placeholder in the loaded setup file:
- <project-name> → the actual project name
- <theme> → the chosen theme (default, bootstrap, material, or fluent)
- <theme-package> → the npm package for the theme:
  - default → @progress/kendo-theme-default
  - bootstrap → @progress/kendo-theme-bootstrap
  - material → @progress/kendo-theme-material
  - fluent → @progress/kendo-theme-fluent
- <theme-display> → the human-readable name:
  - default → Default
  - bootstrap → Bootstrap
  - material → Material Design
  - fluent → Fluent UI
Run all commands sequentially. Do not skip any step.
After completing all steps, run the application and keep it running.

同仓库更多 Skills

同仓库

kendo-angular-mcp-licensing

telerik/ai-plugins

Diagnose and resolve MCP server entitlement failures for @progress/kendo-angular-mcp. Use when MCP tool calls return PERMISSION_DENIED despite a working server, when premium MCP tools don't appear in the IDE, when the AI Coding Assistant stops working (deprecated, migrated to Agentic UI Generator), or when the developer asks whether their license type supports MCP AI tools. Do NOT use for watermarks, banners, or TKL activation codes — those are project licensing issues, route to kendo-angular-product-licensing. Do NOT use for first-time install or onboarding — route to kendo-angular-getting-started. Scoped to Kendo UI for Angular. Trigger on "PERMISSION_DENIED from

2026-07-140

kendo-angular-version-upgrade

telerik/ai-plugins

Guides Kendo UI for Angular version upgrades, including breaking changes and safe migration paths. Use when a developer asks whether an upgrade is safe, what changed between versions, how to plan a multi-version upgrade path, or how to prepare before running migration tools. This skill provides guidance and reasoning about upgrades; it does not execute migrations. For execution, it bridges to the Kendo CLI (`kendo migrate`) and the Upgrade Assistant in the Kendo Angular MCP server. Do NOT use for first-time install (route to kendo-angular-getting-started) or for licensing failures unrelated to version coverage (route to kendo-angular-product-licensing). Trigger on "Should I upgrade Kendo UI for Angular?", "Is it safe to go from v20 to v24?", "What broke in v23?", "What broke in v24?", "How do I upgrade Kendo Angular?", "kendo migrate", "breaking changes between Angular Kendo versions", "my components broke after ng update", "appearance options undefined", "fillMode none removed", "themeColor dark light remove

2026-07-140

kendo-react-mcp-licensing

telerik/ai-plugins

Diagnose and resolve MCP server entitlement failures for @progress/kendo-react-mcp. Use when MCP tool calls return PERMISSION_DENIED despite a working server, when premium MCP tools don't appear in the IDE, when the AI Coding Assistant stops working (deprecated, migrated to Agentic UI Generator), or when the developer asks whether their license type supports MCP AI tools. Do NOT use for watermarks, banners, or TKL activation codes — those are project licensing issues, route to kendo-react-product-licensing. Do NOT use for first-time install or onboarding — route to kendo-react-getting-started. Scoped to KendoReact. Trigger on "PERMISSION_DENIED from

2026-07-140

kendo-react-version-upgrade

telerik/ai-plugins

Guides KendoReact version upgrades, including breaking changes and safe migration paths. Use when a developer asks whether an upgrade is safe, what changed between versions, how to plan a multi-version upgrade path, or how to prepare before running migration tools. This skill provides guidance and reasoning about upgrades; it does not execute migrations. For execution, it bridges to the Kendo CLI (`kendo migrate`) and the MCP server. Do NOT use for first-time install (route to kendo-react-getting-started) or for licensing failures unrelated to version coverage (route to kendo-react-product-licensing). Trigger on "Should I upgrade KendoReact?", "Is it safe to go from v12 to v15?", "What broke in v15?", "How do I upgrade KendoReact?", "kendo migrate", "breaking changes between versions", "my components broke after npm update", "themeColor dark light removed", "ref returns Handle instead of class", "icon names changed", "TKL102 version not covered", "perpetual license upgrade", "what changed in the latest releas

2026-07-140

kendo-angular-ui-generator

telerik/ai-plugins

Main entry point for building or refining UI with Kendo UI for Angular. Orchestrates the full workflow including accessibility, layout, components, theming, icons, and validation. Use when the user wants to build or modify a complete page, section, or UI feature with Kendo UI for Angular components. Trigger on "build a page", "create a dashboard", "implement a UI", "generate a form", "build UI with Kendo Angular", "create an Angular page", "#kendo_ui_generator".

2026-06-160

kendo-react-ui-generator

telerik/ai-plugins

Main entry point for building or refining UI with KendoReact. Orchestrates the full workflow including accessibility, layout, components, theming, icons, and validation. Use when the user wants to build or modify a complete page, section, or UI feature with KendoReact components. Trigger on "build a page", "create a dashboard", "implement a UI", "generate a form", "build UI with KendoReact", "create a React page", "#kendo_ui_generator".

2026-06-160

name	kendo-react-getting-started
description	Creates a new KendoReact project from scratch or adds KendoReact to an existing project. Use when the user wants to set up, scaffold, bootstrap, or get started with a React application using KendoReact. Trigger on "create new React project", "set up KendoReact", "add KendoReact to my app", "scaffold React with Kendo", "getting started with KendoReact", "bootstrap React project", "install kendo-react".
allowed-tools	Bash

KendoReact — Getting Started

Arguments

Usage: /kendo-react-getting-started [mode] [project-name] [--theme=<theme>]

[mode]: new (default) — create a brand-new project with the Kendo CLI, or existing — add KendoReact to an existing project
[project-name]: The name for your project (default: kendo-react-app). Only used in new mode.
[--theme=<theme>]: One of default (default), bootstrap, material, fluent

Instructions

Determine the mode from $ARGUMENTS:
- If $ARGUMENTS contains existing, add, existing-project, or add-to-existing (case-insensitive) → read and follow existing-project.md
- Otherwise → read and follow new-project.md (this is the default)
Extract the project name from $ARGUMENTS. If no name is provided, use kendo-react-app.
Extract the theme from $ARGUMENTS (e.g., --theme=bootstrap). If no theme is provided, use default.
Replace every placeholder in the loaded setup file:
- <project-name> → the actual project name
- <theme> → the chosen theme (default, bootstrap, material, or fluent)
- <theme-package> → the npm package for the theme:
  - default → @progress/kendo-theme-default
  - bootstrap → @progress/kendo-theme-bootstrap
  - material → @progress/kendo-theme-material
  - fluent → @progress/kendo-theme-fluent
- <theme-display> → the human-readable name:
  - default → Default
  - bootstrap → Bootstrap
  - material → Material Design
  - fluent → Fluent UI
Run all commands sequentially. Do not skip any step.
After completing all steps, run the application and keep it running.