What problem does it solve? When you add a new kind of JSON file to the Universe Editor (e.g. *.entity.json), Monaco gives no completion, validation, or hover hints unless a schema is registered. This Skill guides you through wiring a schema association into the editor's existing JSONContributionRegistry pipeline without writing new plumbing. ## Core Features & Use Cases - Three source paths: choose between extension contributes.jsonValidation (path A, the default), user json.schemas settings (path B), or a built-in declaration table (path C) depending on where the schema should live. - Local and remote schemas: inline schema objects, local schema files read and inlined by the extension host, or remote http(s) schemas downloaded in the main process with caching, ETag revalidation, and a trusted-domain whitelist. - Testing and verification guidance: exact test files to extend for each path plus manual end-to-end checks in the dev editor. - Use Case: You create a declaration-only extension with a package.json containing a jsonValidation contribution and a schemas/entity.json file, and every **/*.entity.json opened in the editor immediately gets completion, warning-level validation, and hover descriptions. ## Quick Start Ask the AI to add schema completion and validation for a new JSON file type such as *.entity.json using this skill.
