Safely modify `packages/extension-chat/*` without regressing the original extension in `packages/extension/*`. Use when working on chat side panel UX, background worker behavior, manifest wiring, or chat-only scripts/views.
Safely modify the classic/core extension in `packages/extension/*` without regressing chat extension behavior in `packages/extension-chat/*`. Use when working on core side panel, overlay, worker logic, manifest wiring, or extension scripts/views.
Debug and validate LWC OSS issues in this repo with a minimal, path-based command strategy (lint vs build vs e2e) and clear baseline-vs-regression classification.
Safely implement or refactor LWC OSS code in this repo (LWR + Rollup targets) while preserving cross-target behavior across core extension, chat extension, and shared runtime modules.
Select the smallest correct validation commands for this repo based on touched paths, while distinguishing lint, build/type, and runtime confidence.
Safely modify shared runtime layers (`packages/lwc/main/*`, `packages/lwc/extension/*`, `packages/lwc/shared/*`) without regressing either core extension (`packages/extension/*`) or chat extension (`packages/extension-chat/*`).
Scaffold a new manifest-driven Workbench application under `packages/lwc/applications/<id>/`. Use when the user asks to create, add, or scaffold a new app, tool, utility, or extension in the Workbench monorepo — e.g. "add a new application", "create a workbench app called X", "scaffold a utility under applications", "new SOQL-style tool". Walks the user through the manifest schema, `host-api/*` bootstrap pattern, tsconfig/rollup wiring, and `generate_application_manifest.js` validation so the first build passes.