What problem does it solve? Adding an enterprise configuration policy to VS Code touches many layers: the configuration schema, the PolicyCategory enum, account-level policy data, and generated ADMX/plist/JSON artifacts. This Skill walks you through the full lifecycle so nothing is missed and the auto-generated policy catalog stays in sync. ## Core Features & Use Cases - Policy Registration: Add a policy field to any configuration property with the correct name, category, minimumVersion, and localization keys. - Account-Based Policies: Wire policies to Copilot account policy data via IPolicyData value functions. - Artifact Export: Regenerate policyData.jsonc with npm run export-policy-data so Windows Group Policy, macOS plist, and Linux JSON artifacts stay current. - Extension Policies: Define policies for extension settings through the vscode-distro product.json and keep test fixtures in sync. - Use Case: You need to let enterprise admins lock a new chat setting via Group Policy. This Skill guides you from adding the policy: field, through compilation checks, to exporting the updated policy catalog. ## Quick Start Add a new configuration policy named MyPolicyName to the setting I just created and regenerate the exported policy data.
