diff --git a/doc/user/gitlab_duo/customize_duo.md b/doc/user/gitlab_duo/customize_duo.md
new file mode 100644
index 0000000000000000000000000000000000000000..190f3f0af96b86ebcb89b70929398d81580067df
--- /dev/null
+++ b/doc/user/gitlab_duo/customize_duo.md
@@ -0,0 +1,29 @@
+---
+stage: AI-powered
+group: Duo Chat
+info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
+title: Customize GitLab Duo
+---
+
+You can customize GitLab Duo to match your workflow, coding standards, or project requirements.
+
+## Customization options
+
+| Method | Use cases |
+|-----------|--------------|
+| [Use custom rules](../gitlab_duo_chat/agentic_chat.md#create-custom-rules) to provide instructions for GitLab Duo Chat. Applies to GitLab tools only. | - Apply personal preferences.
- Enforce team standards. |
+| [Create an AGENTS.md file](../gitlab_duo_chat/agentic_chat.md#create-agentsmd-instruction-files) to provide instructions to GitLab Duo Chat and other AI coding tools. Applies to GitLab and non-GitLab tools. | - Account for project-specific context
- Organize a monorepo.
- Enforce directory-specific conventions. |
+| [Customize instructions for GitLab Duo Code Review](../project/merge_requests/duo_in_merge_requests.md#customize-instructions-for-gitlab-duo-code-review) to ensure consistent and specific code review standards in your project.| Apply:
- Language-specific review rules.
- Security standards.
- Code quality requirements.
- File-specific guidelines. |
+
+## Best practices
+
+When customizing GitLab Duo, apply the following best practices:
+
+- Start with minimal clear and simple instructions, and add more as needed.
+ Keep the instruction file as short as possible.
+- Make sure the instructions are specific and actionable. Provide examples as
+ needed.
+- Choose the method that matches your use case.
+- Combine multiple methods to tailor and control how GitLab Duo behaves.
+- Document your choices in comments to explain why certain instructions exist.
+- Protect customization files with [Code Owners](../project/codeowners/_index.md) to manage changes.