What problem does it solve? Adding an enterprise configuration policy to VS Code involves many coordinated steps—registering the policy field, choosing a category, setting the minimum version, handling account-level overrides, and regenerating platform artifacts—and missing any step breaks the export pipeline or produces invalid ADMX/plist files. ## Core Features & Use Cases - Full Policy Lifecycle Guidance: Walks through adding a policy field to a configuration property, importing PolicyCategory, validating with npm run typecheck-client, and regenerating policyData.jsonc via npm run export-policy-data. - Account and Preview Feature Policies: Explains how to wire value functions against IPolicyData, including the chat_preview_features_enabled pattern for GitHub organization-controlled preview features. - Extension Policy Support: Covers defining policies for extension-contributed settings through extensionConfigurationPolicy in vscode-distro product.json files and keeping test fixtures in sync. - Use Case: When a PR adds a policy: field to a chat setting, use this Skill to verify the minimumVersion matches the current package.json version, enumDescriptions align with the enum array, and the export script regenerates the catalog without manual edits. ## Quick Start Ask the assistant to add a new configuration policy for a VS Code setting and have it follow the registration, validation, and export steps end to end.
