Create new reference article for custom instructions support (#59040)

Author: hubwriter

content/copilot/concepts/prompting/response-customization.md

@@ -48,8 +48,6 @@ You can use three types of repository custom instructions in {% data variables.p
 
 {% data reusables.copilot.custom-instructions-about %}
 
-{% data reusables.copilot.repository-custom-instructions-support %}
-
 ## About organization custom instructions
 
 {% data reusables.copilot.custom-instructions-org-support %}
@@ -71,7 +69,7 @@ The following list shows the complete order of precedence, with instructions hig
 
 * **Personal** instructions
 * **Repository** custom instructions:
-  * **Path-specific** instructions in any applicable `.github/instructions/**/NAME.instructions.md` file
+  * **Path-specific** instructions in any applicable `.github/instructions/**/*.instructions.md` file
   * **Repository-wide** instructions in the `.github/copilot-instructions.md` file
   * **Agent** instructions (for example, in an `AGENTS.md` file)
 * **Organization** custom instructions
@@ -132,8 +130,6 @@ You can use three types of repository custom instructions in {% data variables.p
 
 {% data reusables.copilot.custom-instructions-about %}
 
-{% data reusables.copilot.repository-custom-instructions-support %}
-
 ## About prompt files
 
 > [!NOTE] Prompt files are {% data variables.release-phases.public_preview %} and subject to change.
@@ -225,16 +221,14 @@ You can use two types of repository custom instructions in {% data variables.pro
 
 * **Path-specific custom instructions**, which apply to requests made in the context of files that match a specified path.
 
-  These are specified in one or more `NAME.instructions.md` files within the `.github/instructions` directory in the repository.
+  These are specified in one or more `NAME.instructions.md` files within or below the `.github/instructions` directory in the repository.
 
   By using path-specific instructions you can avoid overloading your repository-wide instructions with information that only applies to files of certain types, or in certain directories.
 
-See the table below for details of support for each of these types of repository custom instructions across different {% data variables.product.prodname_copilot_short %} features.
+For details of support for each of these types of repository custom instructions across different {% data variables.product.prodname_copilot_short %} features, see [AUTOTITLE](/copilot/reference/custom-instructions-support).
 
 For a curated collection of examples, see [AUTOTITLE](/copilot/tutorials/customization-library/custom-instructions).
 
-{% data reusables.copilot.repository-custom-instructions-support %}
-
 ## About prompt files
 
 Prompt files let you build and share reusable prompt instructions with additional context. A prompt file is a Markdown file, stored in your workspace, that mimics the existing format of writing prompts in {% data variables.copilot.copilot_chat_short %} (for example, `Rewrite #file:x.ts`). This allows blending natural language instructions, additional context, and even linking to other prompt files as dependencies.
@@ -317,7 +311,9 @@ While custom instructions help to add codebase-wide context to each AI workflow,
 
 In JetBrains IDEs, repository custom instructions consist of a single file, `.github/copilot-instructions.md`, that you create in a repository. The instructions you add to the file should be short, self-contained statements that add context or relevant information to supplement a {% data variables.product.prodname_copilot_short %} prompt.
 
-{% data reusables.copilot.repository-custom-instructions-support %}
+### Support for repository custom instructions
+
+For details of which types of custom instructions are supported across various environments, see [AUTOTITLE](/copilot/reference/custom-instructions-support).
 
 ### Use cases for custom instructions
 
@@ -411,7 +407,9 @@ For a curated collection of examples, see [AUTOTITLE](/copilot/tutorials/customi
 
 In Xcode, repository custom instructions consist of a single file, `.github/copilot-instructions.md`, that you create in a repository. The instructions you add to the file should be short, self-contained statements that add context or relevant information to supplement a {% data variables.product.prodname_copilot_short %} prompt.
 
-{% data reusables.copilot.repository-custom-instructions-support %}
+### Support for repository custom instructions
+
+For details of which types of custom instructions are supported across various environments, see [AUTOTITLE](/copilot/reference/custom-instructions-support).
 
 ### Use cases for custom instructions
 

content/copilot/how-tos/configure-custom-instructions/add-repository-instructions.md

@@ -217,7 +217,7 @@ Once saved, these instructions will apply to the current project in Eclipse that
 
 * **Path-specific custom instructions**, which apply to requests made in the context of files that match a specified path.
 
-  These are specified in one or more `NAME.instructions.md` files within the `.github/instructions` directory in the repository. See [Creating path-specific custom instructions](#creating-path-specific-custom-instructions).
+  These are specified in one or more `NAME.instructions.md` files within or below the `.github/instructions` directory in the repository. See [Creating path-specific custom instructions](#creating-path-specific-custom-instructions).
 
   If the path you specify matches a file that {% data variables.product.prodname_copilot_short %} is working on, and a repository-wide custom instructions file also exists, then the instructions from both files are used. You should avoid potential conflicts between instructions as {% data variables.product.prodname_copilot_short %}'s choice between conflicting instructions is non-deterministic.
 
@@ -253,7 +253,7 @@ Once saved, these instructions will apply to the current project in Eclipse that
 
 * **Path-specific custom instructions**, which apply to requests made in the context of files that match a specified path.
 
-  These are specified in one or more `NAME.instructions.md` files within the `.github/instructions` directory in the repository. See [Creating path-specific custom instructions](#creating-path-specific-custom-instructions-1).
+  These are specified in one or more `NAME.instructions.md` files within or below the `.github/instructions` directory in the repository. See [Creating path-specific custom instructions](#creating-path-specific-custom-instructions-1).
 
   If the path you specify matches a file that {% data variables.product.prodname_copilot_short %} is working on, and a repository-wide custom instructions file also exists, then the instructions from both files are used.
 
@@ -290,7 +290,7 @@ Once saved, these instructions will apply to the current project in Eclipse that
 
 * **Path-specific custom instructions**, which apply to requests made in the context of files that match a specified path.
 
-  These are specified in one or more `NAME.instructions.md` files within the `.github/instructions` directory in the repository. See [Creating path-specific custom instructions](#creating-path-specific-custom-instructions-2).
+  These are specified in one or more `NAME.instructions.md` files within or below the `.github/instructions` directory in the repository. See [Creating path-specific custom instructions](#creating-path-specific-custom-instructions-2).
 
   If the path you specify matches a file that {% data variables.product.prodname_copilot_short %} is working on, and a repository-wide custom instructions file also exists, then the instructions from both files are used.
 
@@ -320,7 +320,7 @@ Once saved, these instructions will apply to the current project in Eclipse that
 
 * **Path-specific custom instructions** apply to requests made in the context of files that match a specified path.
 
-  These are specified in one or more `NAME.instructions.md` files within the `.github/instructions` directory in the repository. See [Creating path-specific custom instructions](#creating-path-specific-custom-instructions-2).
+  These are specified in one or more `NAME.instructions.md` files within or below the `.github/instructions` directory in the repository. See [Creating path-specific custom instructions](#creating-path-specific-custom-instructions-2).
 
   If the path you specify matches a file that {% data variables.product.prodname_copilot_short %} is working on, and a repository-wide custom instructions file also exists, then the instructions from both files are used.
 

content/copilot/how-tos/use-copilot-agents/use-copilot-cli.md

@@ -11,7 +11,7 @@ topics:
   - Copilot
   - CLI
 contentType: how-tos
-category: 
+category:
   - Author and optimize with Copilot
 ---
 
@@ -171,7 +171,7 @@ You can enhance {% data variables.product.prodname_copilot_short %}’s performa
 {% data variables.copilot.copilot_cli_short %} supports:
 
 * Repository-wide instructions in the `.github/copilot-instructions.md` file.
-* Path-specific instructions files: `.github/copilot-instructions/**/*.instructions.md`.
+* Path-specific instructions files: `.github/instructions/**/*.instructions.md`.
 * Agent files such as `AGENTS.md`.
 
 For more information, see [AUTOTITLE](/copilot/how-tos/configure-custom-instructions/add-repository-instructions).
@@ -201,11 +201,11 @@ In the case of naming conflicts, a system-level agent overrides a repository-lev
 * Calling out to {% data variables.copilot.copilot_custom_agent_short %} directly in a prompt:
 
   ```shell
-  Use the refactoring agent to refactor this code block 
+  Use the refactoring agent to refactor this code block
   ```
 
   {% data variables.product.prodname_copilot_short %} will automatically infer the agent you want to use.
-  
+
 * Specifying the {% data variables.copilot.copilot_custom_agent_short %} you want to use with the command-line option. For example:
 
   ```shell