원클릭으로 Manus에서 모든 스킬 실행

kendo-ui-angular

스타2

포크0

업데이트2026년 4월 17일 10:02

Use this skill whenever the user is working with Kendo UI for Angular — including the Data Grid, TreeList, TreeView, DropDownList, AutoComplete, or any @progress/kendo-angular-* package. Covers server-side paging/filtering/sorting, inline CRUD editing, row selection, custom cell templates, master-detail rows, grouping, Excel export, and virtualization for large datasets. Trigger on any mention of kendo grid, kendo treelist, kendo treeview, telerik angular, @progress/kendo-angular-grid, or when the user is building a sortable/filterable/pageable data table in Angular. Also trigger when a user asks about adding editing, export, tree navigation, or dropdown filtering to an existing Kendo Angular component.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

bmsuisse

bmsuisse/skills

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

관련 직업SOC

SOC 직업 분류 기준

웹 개발자컴퓨터 및 수학직·SOC 15-1254

파일 탐색기

5 개 파일

SKILL.md

readonly

이 저장소의 다른 Skills

같은 저장소

rich-data-tables

bmsuisse/skills

Use whenever building a UI table, list view, or dashboard panel showing records with amounts, dates, or statuses (invoices, tickets, orders, tasks, leads, log entries, etc.) — in React/HTML/artifacts, TanStack Table column defs, or when writing/reviewing component code for one. Consult before rendering a "flat" table (raw columns, no aggregation, no visual encoding), even if the user just says "make a table" or "show this data" — a bare table is rarely the best answer once rows carry a magnitude, a due date, or a status. Also use when asked to "make this table nicer", "more like a dashboard", or to add KPIs/summary above a table.

2026-07-142

init-app-stack

bmsuisse/skills

Use this skill whenever the user wants to bootstrap, scaffold, or initialize a new full-stack app with a Vite + React + TanStack + shadcn/ui frontend and a FastAPI + Postgres backend. Triggers on requests like "create a new app", "set up a project", "scaffold a full-stack app", "init a new project", or anything involving starting a fresh React/FastAPI application from scratch.

2026-07-132

cross-repo-discovery

bmsuisse/skills

Discover repos across the whole Azure DevOps org — not just the one you're sitting in — and figure out where a piece of functionality actually lives before assuming it doesn't exist locally. Generates ALL_REPOS.md, a map of every project/repo in the org, each repo's description, and whether it's already cloned locally (and where). Use this whenever the user asks about "other repos", "which repo has X", cross-repo/cross-service work, wants to find or clone a repo they don't have locally yet, or when you're stuck looking for code that isn't in the current repo and it might live elsewhere in the org. Trigger on things like "is there already a repo for this", "check across our other repos", "what repos do we have", "where's the shared X library", or "I don't think this exists yet, can you check devops".

2026-07-132

database-in-source

bmsuisse/skills

Conventions for versioning a PostgreSQL schema as plain `.sql` files inside a `database/` folder in the repo, instead of an ORM migration framework. Use when creating/organising a `database/` folder, adding a new table/view/function/type, or deciding where a migration script goes. Triggers on things like "add a new table to database/", "where do table definitions live", "database folder structure", "schema layer", "migration script", ".prod file", ".init.sql".

2026-07-102

postgres-best-practices

bmsuisse/skills

PostgreSQL coding standards for Python projects using psycopg (no ORM). Use this skill whenever the user is writing or reviewing code that queries PostgreSQL with psycopg, creates SQL files, maps query results to Python objects, or asks how to structure database access code. Triggers on things like "add a database query", "write a SQL query", "create a repository", "fetch from postgres", "insert into the database", "update the DB", "parameterized query", "pydantic model from DB row", "sql file", "dynamic SQL", or any mention of psycopg, psycopg2, asyncpg, or SQLAlchemy where the user seems open to a different approach. Also use when the user asks about connection pooling, transactions, cursor factories, or how to organise database code.

2026-07-102

postgres-test-setup

bmsuisse/skills

Set up and work with a local PostgreSQL test database in Docker for integration/e2e tests. Use this skill whenever the user wants to add, configure, troubleshoot, or run queries against a local test Postgres instance — even if they don't say "postgres" explicitly. Triggers on things like "set up a test database", "add postgres fixtures", "init test DB", "local postgres for tests", "add a column", "create a table", "change the schema", "run a SQL query on my test DB", "reset the database", "database is out of sync", "test data", or anything involving the local test Postgres database. Also use this skill when the user asks how to inspect the test DB, seed rows, or apply a migration to the local environment.

2026-07-102

name

kendo-ui-angular

description

Kendo UI for Angular — Development Guidelines

Setup & Installation

All packages are installed via the Angular schematics command, which handles dependencies and theme registration automatically:

ng add @progress/kendo-angular-grid
ng add @progress/kendo-angular-treelist
ng add @progress/kendo-angular-treeview
ng add @progress/kendo-angular-dropdowns

Standalone vs. NgModule

Modern Angular (15+) uses standalone components. All Kendo packages expose a barrel token (e.g. KENDO_GRID) that replaces the module import:

Approach	Import
Standalone (preferred)	`imports: [KENDO_GRID]` in `@Component`
NgModule	`GridModule` in `@NgModule`

Architecture Decisions

Client-Side vs. Server-Side Operations

Client-side (< ~5,000 rows): use the process() function from @progress/kendo-data-query. Pass your raw array + the current state and bind the result as GridDataResult.
Server-side (large datasets): handle (dataStateChange), send the state to your API, and bind the returned { data: T[], total: number }. RxJS switchMap is the cleanest pattern to avoid race conditions.

Change Detection

Kendo components work with both Default and OnPush change detection. With OnPush:

Pass data as Observable (use async pipe) — preferred
Or manually call cdr.markForCheck() after mutating bound data

Forms Integration

All input/dropdown components support both template-driven (ngModel) and reactive (formControl) forms natively — no wrapper needed.

Component Overview

Component	Package	Use when
`kendo-grid`	`@progress/kendo-angular-grid`	Flat tabular data with sort/filter/page/edit
`kendo-treelist`	`@progress/kendo-angular-treelist`	Hierarchical data in a table layout (org charts, file trees with columns)
`kendo-treeview`	`@progress/kendo-angular-treeview`	Navigation tree / sidebar menu / selection tree
`kendo-dropdownlist`	`@progress/kendo-angular-dropdowns`	Pick from a fixed list — no free-text entry
`kendo-autocomplete`	`@progress/kendo-angular-dropdowns`	Free-text input with suggestion list

Grid — Key API

kendo-grid Inputs (most commonly used)
────────────────────────────────────────────────────────
[data]               T[] | GridDataResult      Bound data (page-slice for server-side)
[pageSize]           number                    Page size
[skip]               number                    Current page offset (0-based)
[pageable]           boolean | PagerSettings   Enable pager
[sortable]           boolean | SortSettings    Enable sorting
[filterable]         boolean | FilterSettings  Enable filter row or menu
[groupable]          boolean | GroupSettings   Enable grouping drag-and-drop
[selectable]         boolean | SelectSettings  Enable row selection
[loading]            boolean                   Show loading overlay
[sort]               SortDescriptor[]          Current sort state (bind for controlled sort)
[filter]             CompositeFilterDescriptor Current filter state
[group]              GroupDescriptor[]         Current group state
[rowHeight]          number                    Required for virtual scrolling
[height]             number                    Container height in px (virtual scrolling)
[rowClass]           (row) => string           Dynamic CSS class per row

kendo-grid Outputs
────────────────────────────────────────────────────────
(dataStateChange)    Combined: sort+filter+page+group changed — use for server-side
(pageChange)         Page changed (use instead of dataStateChange for paging-only)
(sortChange)         Sort changed
(filterChange)       Filter changed
(groupChange)        Group changed
(selectionChange)    Row selection changed
(add)                Add new row triggered
(edit)               Row enters edit mode
(save)               Row saved
(cancel)             Edit canceled
(remove)             Row removed
(detailExpand)       Detail row expanded
(detailCollapse)     Detail row collapsed
(excelExport)        Excel export triggered

Column directives
────────────────────────────────────────────────────────
kendo-grid-column          Standard column (field, title, width, format, filter, editable, etc.)
kendo-grid-checkbox-column Checkbox selection column
kendo-grid-command-column  Buttons: edit/save/cancel/remove via built-in commands
kendo-grid-toolbar         Toolbar slot (add buttons, search)

See references/grid-samples.md for complete code samples:

Client-side sort/filter/page with process()
Server-side paging, filtering & sorting with RxJS
Inline row editing (Add / Edit / Save / Cancel / Delete)
Row selection — single-click, multi-checkbox + bulk actions, programmatic, cross-page persistence, drag-to-select
Custom cell template (status badge)
Master-detail expandable rows
Excel export
Virtual scrolling for large datasets

TreeList — Key API

TreeList renders hierarchical data as an expandable table — each row can have child rows, shown with an expand arrow. Unlike TreeView, it supports the full column / sort / filter / edit feature set.

kendo-treelist Inputs
────────────────────────────────────────────────────────
[kendoTreeListFlatBinding]      directive   Flat array data binding (use idField + parentIdField)
[kendoTreeListHierarchyBinding] directive   Nested object data binding (use childrenField)
[idField]            string                 Unique id field (flat binding)
[parentIdField]      string                 Parent reference field (flat binding)
[childrenField]      string                 Child array field (hierarchy binding)
[fetchChildren]      (node) => Observable   Load children on demand (async tree)
[hasChildren]        (node) => boolean      Whether a node is expandable
[isExpanded]         (node) => boolean      Whether a node is expanded by default
[pageSize]           number                 Page size
[pageable]           boolean | PagerSettings
[sortable]           boolean | SortSettings
[filterable]         boolean | FilterSettings
[selectable]         boolean | SelectSettings
[loading]            boolean

kendo-treelist Outputs
────────────────────────────────────────────────────────
(expand)             Node expanded
(collapse)           Node collapsed
(dataStateChange)    State changed (sort/filter/page)
(selectionChange)    Selection changed
(add) (edit) (save) (cancel) (remove)   CRUD events (same pattern as Grid)

See references/treelist-treeview-samples.md for:

Flat-data binding with idField / parentIdField
Hierarchical (nested) data binding
On-demand async children loading
Inline editing in TreeList

TreeView — Key API

TreeView is a navigation component — a collapsible tree with optional checkboxes. It does not have columns, sorting, or pagination.

kendo-treeview Inputs
────────────────────────────────────────────────────────
[kendoTreeViewHierarchyBinding] directive   Nested data (use textField + childrenField)
[kendoTreeViewFlatDataBinding]  directive   Flat data (use idField + parentIdField)
[nodes]              any[]                  Root-level items (used without a binding directive)
[textField]          string | string[]      Field(s) to display as node text
[children]           (item) => Observable   Function returning child nodes
[hasChildren]        (item) => boolean      Whether a node has children
[isExpanded]         (item, index) => bool  Control expansion state
[isSelected]         (item, index) => bool  Control selection state
[isChecked]          (item, index) => CheckedState   Checkbox state
[loadOnDemand]       boolean                Load children only when parent expands
[filterable]         boolean                Show a filter input
[filter]             string                 Current filter value (controlled)
[navigable]          boolean                Enable keyboard navigation
[animate]            boolean                Expand/collapse animation (default: true)

kendo-treeview Outputs
────────────────────────────────────────────────────────
(nodeClick)          Node clicked
(expand)             Node expanded — use to update your isExpanded state
(collapse)           Node collapsed
(selectionChange)    Selection changed
(checkedChange)      Checkbox state changed
(filterChange)       Filter text changed

See references/treelist-treeview-samples.md for:

Hierarchical binding with expand/collapse state
Flat data binding
Load-on-demand (async children via Observable)
Checkboxes with tri-state parent nodes
Filterable tree

DropDownList & AutoComplete — Quick Reference

Choose based on whether the user can enter free text:

Component	Package token	Use when
`kendo-dropdownlist`	`KENDO_DROPDOWNLIST`	Must pick from a list; free-text not allowed
`kendo-autocomplete`	`KENDO_AUTOCOMPLETE`	Free text with suggestions; bound value stays a string
`kendo-combobox`	`KENDO_COMBOBOX`	Either: pick from list OR enter custom text

Shared best practices:

Enable [filterable]="true" + (filterChange) for large lists — never push 10k items to the client
Set a minimum filter length guard (if (filter.length < 2) return) to avoid server calls on every keystroke
Use [loading]="isLoading" while async calls are in flight

See references/dropdown-samples.md for complete samples covering DropDownList and AutoComplete.

General Principles

Always set field on grid columns even when using a custom cell template — sorting, filtering, and export depend on it.
Normalize data before binding: compute derived fields (e.g. fullName) before binding to the grid instead of combining fields in a template, which breaks sort/filter.
Manage [loading]: always set it true while async calls are in-flight to prevent users from interacting with stale data.
Z-index for dialogs: if you wrap a Kendo component inside a modal/overlay, ensure overflow: visible on the modal and set a higher z-index for Kendo popups so filter menus and dropdowns are not clipped.
Production builds: Kendo dev builds add diagnostics that slow rendering — always benchmark against a ng build --configuration production output.