skill-authoring

Provides rules for writing or updating a SKILL.md in this repository: frontmatter validation for license, name and description, the WHEN TO USE and WHEN NOT TO USE description format, and the 500-line body budget with progressive disclosure into reference files. WHEN TO USE: creating a new skill under .agents/skills/ or skills/, or editing an existing skill's frontmatter, scope, or length. WHEN NOT TO USE: writing component code, styles, or tests (use create-new-component, add-component-property, or update-component-styles), reviewing a component pull request (use review-component-pr), or changing the coding rules themselves (edit .github/CODING_GUIDELINES.md).

설치로 이동 파일 검토

저장소: IgniteUI/igniteui-webcomponents
최근 소스 활동: 2026년 9월 24일 12:19
감지된 SKILL.md 언어: 영어
스타: 170
포크: 12

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

AI 어시스턴트로 설치

이 프롬프트를 복사해 사용 중인 AI 어시스턴트에 입력하세요.

Follow https://skillsmp.com/skill-install/prompt.md to install only the Agent Skill at https://github.com/IgniteUI/igniteui-webcomponents/tree/master/.agents/skills/skill-authoring.

직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.

npx skills add https://github.com/IgniteUI/igniteui-webcomponents --skill skill-authoring

명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.

로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

SKILL.md

소스 지침 · 읽기 전용 미리보기

license: MIT
name: skill-authoring
description: Provides rules for writing or updating a SKILL.md in this repository: frontmatter validation for license, name and description, the WHEN TO USE and WHEN NOT TO USE description format, and the 500-line body budget with progressive disclosure into reference files. WHEN TO USE: creating a new skill under .agents/skills/ or skills/, or editing an existing skill's frontmatter, scope, or length. WHEN NOT TO USE: writing component code, styles, or tests (use create-new-component, add-component-property, or update-component-styles), reviewing a component pull request (use review-component-pr), or changing the coding rules themselves (edit .github/CODING_GUIDELINES.md).
user-invocable: true

# Ignite UI for Web Components — Skill Authoring Quick-reference for writing a `SKILL.md` that agents can discover and load reliably. ## Location - Internal, contributor-facing skills: `.agents/skills/<name>/SKILL.md` - Public skills that ship with the package: `skills/<name>/SKILL.md` - The folder name must match the `name` field. ## Frontmatter | Field | Rules | |---|---| | `license` | Required. Must specify the license under which the skill is released. Default is MIT. | | `name` | Required. Max 64 characters. Lowercase letters, numbers, and hyphens only. No XML tags. No reserved words (`anthropic`, `claude`). Public skills use the `igniteui-wc-` prefix; internal skills use a plain kebab-case name. | | `description` | Required. Non-empty. Max 1,024 characters. No XML tags. | Write the description in the third person: say what the skill covers, then add both markers: - `WHEN TO USE:` the tasks or triggers that should load the skill. - `WHEN NOT TO USE:` nearby tasks it does not cover, naming the skill to use instead. Agents see only `name` and `description` until they load the skill, so the description decides whether it is ever used. ## Token Budget - Keep the `SKILL.md` body under 500 lines. - If it grows past that, use progressive disclosure: keep the overview and core rules in `SKILL.md` and move detail into `references/<topic>.md` files. - Link each reference file directly from `SKILL.md` (one level deep) and say when to read it, so agents load it only when needed. ## Checklist 1. Frontmatter passes the rules above. 2. The description includes `WHEN TO USE:` and `WHEN NOT TO USE:`. 3. The body is under 500 lines, and every reference file is linked from `SKILL.md`. 4. The skill is listed in the Skills table of its README: [.agents/skills/README.md](../README.md) for internal skills, [skills/README.md](../../../skills/README.md) for public skills. Internal skills are also listed in the Workflow section of [.agents/context/project.md](../../context/project.md). ## Related Skills - [`create-new-component`](../create-new-component/SKILL.md) — Scaffolding a new component - [`add-component-property`](../add-component-property/SKILL.md) — Adding a reactive property - [`update-component-styles`](../update-component-styles/SKILL.md) — Changing SCSS or themes - [`review-component-pr`](../review-component-pr/SKILL.md) — Reviewing a component pull request

GitHub에서 보기

검색으로 돌아가기 설치로 돌아가기

review-component-pr

Code review checklist for component pull requests covering structure, public API, specification accuracy, accessibility, behavior, styles, tests, and build hygiene

2026-10-02

igniteui-wc-migrate-grid-lite-to-premium

Step-by-step migration from igniteui-grid-lite (IgcGridLite, <igc-grid-lite>) to the premium igniteui-webcomponents-grids data grid (IgcGridComponent, <igc-grid>), covering imports, class names, HTML tags, properties, events, templates, sorting, filtering, remote data, and theming API changes. WHEN TO USE: the user wants to upgrade from Grid Lite to the premium grid, or needs enterprise features Grid Lite lacks (editing, selection, paging, grouping, summaries, Excel export, state persistence). WHEN NOT TO USE: starting a new grid from scratch (use choose-components), migrating between other grids (Tree Grid, Hierarchical Grid, Pivot Grid) or across major versions of the same package, the project uses igniteui-angular or Blazor grids, or the user only needs theming (use customize-component-theme).

2026-09-28

igniteui-wc-figma-to-app

Builds Ignite UI Web Components views from Figma designs, supporting Indigo.Design kits, third-party kits (Material 3, Fluent 2, shadcn/ui, Untitled UI, in-house), and plain frames. Uses the Figma, Ignite UI CLI, Ignite UI Theming, and Playwright MCP servers. WHEN TO USE: implementing a Figma design, artboard, or Figma URL with Ignite UI Web Components, including inside React, Angular, or Vue apps. WHEN NOT TO USE: screenshots or mockups without a Figma file (use igniteui-wc-generate-from-image-design), component selection or theme-only changes (use igniteui-wc-choose-components or igniteui-wc-customize-component-theme), or the native Ignite UI for Angular or Blazor packages.

2026-09-25

이 저장소의 모든 Skills 보기

skill-authoring

소스 정보

설치 방법

AI 어시스턴트로 설치

소스 파일 검토

이 저장소의 다른 Skills

AI 어시스턴트로 설치

이 저장소의 다른 Skills