diff --git a/.agents/skills/firefox-desktop-frontend/SKILL.md b/.agents/skills/firefox-desktop-frontend/SKILL.md
index c923ee9908e5..2889e4a545ce 100644
--- a/.agents/skills/firefox-desktop-frontend/SKILL.md
+++ b/.agents/skills/firefox-desktop-frontend/SKILL.md
@@ -6,6 +6,7 @@ description: You MUST use this skill when working with HTML, JS, CSS and other f
 
 ## Workflow
 - Whenever you're building, if `./mach build` was previously run and you have not made any changes to C++ or Rust code (nor rebased past incoming changes to such code), you can use `./mach build faster` to skip the compilation and linking steps and only build the front-end code. This can save a lot of time when you're only working on the browser/ or toolkit/ code.
+- For frontend-only work in an unconfigured fresh worktree, use `./mach bootstrap --application-choice browser_artifact_mode`. Preserve an existing build configuration, and do not use artifact mode when the work requires C++, Rust, or other native-code changes.
 - CSS should use reusable tokens from the design system (in `toolkit/themes/shared/design-system`) wherever possible, to ensure consistent UI and to make it easy to change styles across the board.
 - Use reusable components for common UI patterns. These components live in `toolkit/content/widgets/`. A storybook instance for these components can be accessed on https://firefoxux.github.io/firefox-desktop-components/. It is fine to use in-development components.
 - Use CSS logical properties (e.g. `margin-inline-start` instead of `margin-left`) for better localization support.
diff --git a/.claude/skills/firefox-desktop-frontend/SKILL.md b/.claude/skills/firefox-desktop-frontend/SKILL.md
index c923ee9908e5..2889e4a545ce 100644
--- a/.claude/skills/firefox-desktop-frontend/SKILL.md
+++ b/.claude/skills/firefox-desktop-frontend/SKILL.md
@@ -6,6 +6,7 @@ description: You MUST use this skill when working with HTML, JS, CSS and other f
 
 ## Workflow
 - Whenever you're building, if `./mach build` was previously run and you have not made any changes to C++ or Rust code (nor rebased past incoming changes to such code), you can use `./mach build faster` to skip the compilation and linking steps and only build the front-end code. This can save a lot of time when you're only working on the browser/ or toolkit/ code.
+- For frontend-only work in an unconfigured fresh worktree, use `./mach bootstrap --application-choice browser_artifact_mode`. Preserve an existing build configuration, and do not use artifact mode when the work requires C++, Rust, or other native-code changes.
 - CSS should use reusable tokens from the design system (in `toolkit/themes/shared/design-system`) wherever possible, to ensure consistent UI and to make it easy to change styles across the board.
 - Use reusable components for common UI patterns. These components live in `toolkit/content/widgets/`. A storybook instance for these components can be accessed on https://firefoxux.github.io/firefox-desktop-components/. It is fine to use in-development components.
 - Use CSS logical properties (e.g. `margin-inline-start` instead of `margin-left`) for better localization support.