docs(ai): update Claude Code instructions for skill discovery and usage#6421
docs(ai): update Claude Code instructions for skill discovery and usage#6421
Conversation
| Claude Code discovers skills from `.claude/skills/` directories at both project and user level: | ||
|
|
||
| 1. Create `CLAUDE.md` in your project root. | ||
| 2. Paste the contents of the relevant `SKILL.md` files into it. For example: | ||
| 1. Create a `.claude/skills/` directory in your project root. | ||
| 2. Copy the skill directories from the `igniteui-angular/skills/` repository into `.claude/skills/`: | ||
|
|
||
| ```markdown | ||
| # Project Instructions | ||
|
|
||
| This project uses Ignite UI for Angular. Always follow these guidelines: | ||
|
|
||
| <paste contents of SKILL.md files here> | ||
| ``` | ||
| .claude/ | ||
| skills/ | ||
| igniteui-angular-components/ | ||
| SKILL.md | ||
| igniteui-angular-grids/ | ||
| SKILL.md | ||
| igniteui-angular-theming/ | ||
| SKILL.md | ||
| ``` | ||
|
|
||
| 3. Claude Code will automatically discover and apply the relevant skill based on context. | ||
|
|
||
| 3. Claude Code will automatically read `CLAUDE.md` at the start of every session. | ||
| > **Tip:** You can also install skills globally under `~/.claude/skills/` so they are available across all projects. |
There was a problem hiding this comment.
@zdrawku So that kind of became the same thing as copying steps below? I don't mind explaining where skills go per agent type, but the current structure of the topic doesn't quite make sense to me.
I was talking with @ChronosSF about this and might need clarifications:
The entire "Approach 1: Create a Persistent IDE Agent" section seems off since it's about "no copy-pasting required" linking copilot instructions to something like https://github.com/IgniteUI/igniteui-angular/blob/master/skills/igniteui-angular-components/SKILL.md directly (i.e. an attempt for evergreen in a way), though that's not a skill used that way.
So might want to re-do the Copilot section as well and after that it's no longer Approach 1: vs Approach 2: - they are the same thing, just the secondary section is the examples how to copy this section is missing.
PS: Bit of a dupe of #6420, so decide which one is moving forward
| Cursor supports persistent project rules through the `.cursor/rules/` directory: | ||
|
|
||
| 1. Create `.cursorrules` in your project root (or `.cursor/rules/igniteui.md` for a named rule). | ||
| 1. Create `.cursor/rules/igniteui.md` in your project root. |
There was a problem hiding this comment.
That's instructions for https://cursor.com/docs/rules instead of https://cursor.com/docs/skills#skill-directories too, as a matter of fact all of the editor options besides the General AI Agents and the now updated Claude are like that
There was a problem hiding this comment.
Pull request overview
Updates the AI skills documentation to reflect newer “skills discovery” workflows—especially for Claude Code—so users can install/copy skill directories instead of pasting content into single instruction files.
Changes:
- Updated Claude Code guidance to use
.claude/skills/(project + user scope) and describe auto-loading behavior. - Refreshed setup instructions for other assistants (Copilot, Cursor, Windsurf, JetBrains AI Assistant) in the English doc.
- Extended
cspell.jsondictionary to include new terminology used in the docs.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 6 comments.
| File | Description |
|---|---|
jp/components/ai/skills.md |
Updates Claude Code section to use .claude/skills/ directory-based skill discovery. |
en/components/ai/skills.md |
Updates multiple assistant instruction mechanisms (Copilot/Cursor/Windsurf/JetBrains/Claude Code) and introduces skill frontmatter/invocation notes. |
cspell.json |
Adds spelling allowlist entries for “frontmatter” and “backmatter”. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
|
||
| 3. Alternatively, paste the full content of the relevant `SKILL.md` files directly into `copilot-instructions.md` for fully offline, self-contained instructions. | ||
| 4. Copilot will now apply these instructions automatically on every chat and inline suggestion in VS Code. | ||
| 4. Copilot will now apply these instructions automatically on every Copilot Chat request in VS Code. |
There was a problem hiding this comment.
The repo’s JP docs are expected to mirror EN structure/content (see .github/workflows/sync-jp-docs.md where ./jp/ “must mirror ./en/). This section was updated in EN to say instructions apply to “every Copilot Chat request”, but the JP counterpart still says “chat and inline suggestions”. Please sync the JP page (or adjust EN) so both locales describe the same behavior.
| 4. Copilot will now apply these instructions automatically on every Copilot Chat request in VS Code. | |
| 4. Copilot will now apply these instructions automatically for chat and inline suggestions in VS Code. |
| ```markdown | ||
| # Project Instructions | ||
| 1. Create a `.claude/skills/` directory in your project root. | ||
| 2. Copy the skill directories from the `igniteui-angular/skills/` repository into `.claude/skills/`: |
There was a problem hiding this comment.
Wording issue: igniteui-angular/skills/ is a directory path inside the igniteui-angular repository, not a repository itself. Consider rephrasing to “from the igniteui-angular repository’s skills/ directory” to avoid sending readers to a nonexistent repo.
| 2. Copy the skill directories from the `igniteui-angular/skills/` repository into `.claude/skills/`: | |
| 2. Copy the skill directories from the `igniteui-angular` repository's `skills/` directory into `.claude/skills/`: |
| Claude Code loads skills from `.claude/skills/` at both project and user level. Each skill's `description` field in its `SKILL.md` frontmatter tells Claude when to invoke it automatically. You can also invoke any skill directly with `/skill-name`. | ||
|
|
There was a problem hiding this comment.
This introduces /skill-name as a direct invocation syntax, but the following step uses a concrete example (/igniteui-angular-grids). To reduce ambiguity, consider either documenting the exact invocation format Claude Code expects (with one consistent example) or removing the placeholder /skill-name wording.
| Cursor supports persistent project rules through the `.cursor/rules/` directory: | ||
|
|
||
| 1. Create `.cursorrules` in your project root (or `.cursor/rules/igniteui.md` for a named rule). | ||
| 1. Create `.cursor/rules/igniteui.md` in your project root. | ||
| 2. Paste the contents of the desired `SKILL.md` files into that file. For example: |
There was a problem hiding this comment.
The repo’s JP docs are expected to mirror EN (per .github/workflows/sync-jp-docs.md). EN updated multiple agent sections here (Cursor/Windsurf/JetBrains/Claude Code), but the JP version still contains the older instructions for those sections. Please sync jp/components/ai/skills.md to match the updated EN guidance to avoid diverging setup steps between locales.
| 1. プロジェクト ルートに `CLAUDE.md` を作成します。 | ||
| 2. 関連する `SKILL.md` ファイルの内容を貼り付けます。例: | ||
| 1. プロジェクト ルートに `.claude/skills/` ディレクトリを作成します。 | ||
| 2. `igniteui-angular/skills/` リポジトリからスキル ディレクトリを `.claude/skills/` にコピーします。 |
There was a problem hiding this comment.
Wording issue: igniteui-angular/skills/ is a directory in the igniteui-angular repository, not a repository itself. Please rephrase so Japanese readers aren’t led to look for a nonexistent “skills repo” (e.g., “igniteui-angular リポジトリの skills/ ディレクトリから…”).
| 2. `igniteui-angular/skills/` リポジトリからスキル ディレクトリを `.claude/skills/` にコピーします。 | |
| 2. `igniteui-angular` リポジトリの `skills/` ディレクトリからスキル ディレクトリを `.claude/skills/` にコピーします。 |
| Claude Code は、プロジェクト レベルおよびユーザー レベルの `.claude/skills/` ディレクトリからスキルを検出します。 | ||
|
|
||
| 1. プロジェクト ルートに `CLAUDE.md` を作成します。 | ||
| 2. 関連する `SKILL.md` ファイルの内容を貼り付けます。例: | ||
| 1. プロジェクト ルートに `.claude/skills/` ディレクトリを作成します。 | ||
| 2. `igniteui-angular/skills/` リポジトリからスキル ディレクトリを `.claude/skills/` にコピーします。 | ||
|
|
There was a problem hiding this comment.
EN’s Claude Code section now adds details about how skills are selected (based on SKILL.md frontmatter description) and mentions direct invocation (e.g., /igniteui-angular-grids). The JP Claude Code section doesn’t include these details, which breaks the EN↔JP mirroring requirement stated in .github/workflows/sync-jp-docs.md (JP “must mirror EN”). Please sync the JP Claude Code content with the updated EN section.
No description provided.