Skip to content

Commit 07a3a36

Browse files
authored
Merge pull request #9616 from microsoft/ntrogh/fix-customization-location
Remove misleading language about customization locations
2 parents d59d7e9 + 975ef7f commit 07a3a36

4 files changed

Lines changed: 21 additions & 26 deletions

File tree

docs/copilot/customization/agent-skills.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -66,11 +66,10 @@ Skills are stored in directories with a `SKILL.md` file that defines the skill's
6666
| Project skills, stored in your repository | `.github/skills/`, `.claude/skills/`, `.agents/skills/` |
6767
| Personal skills, stored in your user profile | `~/.copilot/skills/`, `~/.claude/skills/`, `~/.agents/skills/` |
6868

69-
> [!TIP]
70-
> In a monorepo, enable `setting(chat.useCustomizationsInParentRepositories)` to discover skills from the parent repository root. Learn more about [parent repository discovery](/docs/copilot/customization/overview.md#parent-repository-discovery).
69+
You can configure additional file locations for project skills with the `setting(chat.skillsLocations)` setting. This is useful if you want to organize skills in a different folder structure or have multiple skill directories.
7170

7271
> [!TIP]
73-
> You can configure additional locations where VS Code searches for skills by using the `setting(chat.agentSkillsLocations)` setting. This is useful for sharing skills across projects or keeping them in a central location.
72+
> In a monorepo, enable `setting(chat.useCustomizationsInParentRepositories)` to discover skills from the parent repository root. Learn more about [parent repository discovery](/docs/copilot/customization/overview.md#parent-repository-discovery).
7473
7574
To create a skill:
7675

docs/copilot/customization/custom-agents.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -76,18 +76,18 @@ When users see the handoff button and select it, they switch to the target agent
7676

7777
## Custom agent file locations
7878

79-
You can define custom agents for a specific workspace or at the user level, where they are available across all your workspaces.
80-
81-
> [!TIP]
82-
> In a monorepo, enable `setting(chat.useCustomizationsInParentRepositories)` to discover custom agents from the parent repository root. Learn more about [parent repository discovery](/docs/copilot/customization/overview.md#parent-repository-discovery).
79+
You can define custom agents for a specific workspace or at the user level, where they are available across all your workspaces. The following table lists the default file locations for custom agents based on their scope. You can configure additional file locations for workspace custom agent files with the `setting(chat.agentFilesLocations)` setting.
8380

8481
| Scope | Default file location |
8582
|-------|-----------------------|
8683
| Workspace | `.github/agents` folder |
8784
| Workspace (Claude format) | `.claude/agents` folder |
88-
| User profile | `~/.copilot/agents`, `agents` folder of the current [VS Code profile](/docs/configure/profiles.md) |
85+
| User profile | `~/.copilot/agents` or your user data (specific to your VS Code profile) |
8986

90-
You can configure additional file locations for workspace custom agent files with the `setting(chat.agentFilesLocations)` setting.
87+
To create a custom agent in user data, use the Chat Customizations editor or use the **Chat: New Custom Agent** command.
88+
89+
> [!TIP]
90+
> In a monorepo, enable `setting(chat.useCustomizationsInParentRepositories)` to discover custom agents from the parent repository root. Learn more about [parent repository discovery](/docs/copilot/customization/overview.md#parent-repository-discovery).
9191
9292
## Custom agent file structure
9393

docs/copilot/customization/custom-instructions.md

Lines changed: 7 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -130,18 +130,15 @@ Use `.instructions.md` files for:
130130

131131
### Instructions file locations
132132

133-
You can define instructions for a specific workspace or at the user level, where they are applied across all your workspaces.
134-
135-
> [!TIP]
136-
> In a monorepo, enable `setting(chat.useCustomizationsInParentRepositories)` to discover instructions from the parent repository root. Learn more about [parent repository discovery](/docs/copilot/customization/overview.md#parent-repository-discovery).
133+
You can define instructions for a specific workspace or at the user level, where they are applied across all your workspaces. The following table lists the default file locations for instructions files based on their scope. You can configure additional file locations for workspace instructions files with the `setting(chat.instructionsFilesLocations)` setting.
137134

138135
| Scope | Default file location |
139136
|-------|-----------------------|
140137
| Workspace | `.github/instructions` folder |
141138
| Workspace (Claude format) | `.claude/rules` folder |
142-
| User profile | `~/.copilot/instructions`, `~/.claude/rules`, `instructions` folder of the current [VS Code profile](/docs/configure/profiles.md) |
139+
| User profile | `~/.copilot/instructions`, `~/.claude/rules`, or your user data (specific to your VS Code profile) |
143140

144-
VS Code searches these folders recursively, so you can organize instructions files in subdirectories. For example, you can group instructions by team, language, or module:
141+
VS Code searches these folders recursively, to enable you to organize instructions files in subdirectories. For example, you can group instructions by team, language, or module:
145142

146143
```text
147144
.github/instructions/
@@ -154,11 +151,7 @@ VS Code searches these folders recursively, so you can organize instructions fil
154151
unit-tests.instructions.md
155152
```
156153

157-
You can configure additional file locations for workspace instructions files with the `setting(chat.instructionsFilesLocations)` setting. This is useful if you want to keep instructions files in a different folder or have multiple folders for better organization. Custom locations are also searched recursively.
158-
159-
For compatibility with Claude Code and other Claude-based tools, VS Code also detects instructions files in the `.claude/rules` workspace folder and the `~/.claude/rules` user folder.
160-
161-
The following code snippet shows how to configure instructions file locations, where only workspace-level instructions are enabled and user-level instructions are disabled:
154+
The following example shows how to configure the instructions file locations to only allow workspace-level instructions:
162155

163156
```json
164157
"chat.instructionsFilesLocations": {
@@ -169,6 +162,9 @@ The following code snippet shows how to configure instructions file locations, w
169162
}
170163
```
171164

165+
> [!TIP]
166+
> In a monorepo, enable `setting(chat.useCustomizationsInParentRepositories)` to discover instructions from the parent repository root. Learn more about [parent repository discovery](/docs/copilot/customization/overview.md#parent-repository-discovery).
167+
172168
### Instructions file format
173169

174170
Instructions files are Markdown files with the `.instructions.md` extension. The optional YAML frontmatter header controls when the instructions are applied:

docs/copilot/customization/prompt-files.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -30,17 +30,17 @@ Use prompt files to:
3030
3131
## Prompt file locations
3232

33-
You can define prompt files for a specific workspace or at the user level, where they are available across all your workspaces.
34-
35-
> [!TIP]
36-
> In a monorepo, enable `setting(chat.useCustomizationsInParentRepositories)` to discover prompt files from the parent repository root. Learn more about [parent repository discovery](/docs/copilot/customization/overview.md#parent-repository-discovery).
33+
You can define prompt files for a specific workspace or at the user level, where they are available across all your workspaces. The following table lists the default file locations for prompt files based on their scope. You can configure additional file locations for workspace prompt files with the `setting(chat.promptFilesLocations)` setting.
3734

3835
| Scope | Default file location |
3936
|-------|-----------------------|
4037
| Workspace | `.github/prompts` folder |
41-
| User profile | `prompts` folder of the current [VS Code profile](/docs/configure/profiles.md) |
38+
| User profile | Your user data (specific to your VS Code profile) |
4239

43-
You can configure additional file locations for workspace prompt files with the `setting(chat.promptFilesLocations)` setting.
40+
To create a prompt file in user data, use the Chat Customizations editor or use the **Chat: New Prompt File** command.
41+
42+
> [!TIP]
43+
> In a monorepo, enable `setting(chat.useCustomizationsInParentRepositories)` to discover prompt files from the parent repository root. Learn more about [parent repository discovery](/docs/copilot/customization/overview.md#parent-repository-discovery).
4444
4545
## Prompt file format
4646

0 commit comments

Comments
 (0)