What problem does it solve? Documenting an existing Umbraco 17 capability that has no spec, plan, or tests requires manually hunting through serialized schema files, generated models, and Razor views — and the two serialization formats (Deploy .uda JSON and uSync .config XML) express the same schema asymmetrically, so naive reads silently produce empty or wrong inventories. ## Core Features & Use Cases - Schema artifact parsing: Locates and parses Deploy document-type__*.uda files or uSync ContentTypes/*.config files, extracting property groups, compositions, tabs, and the element-type flag with format-specific branching rules. - Block palette resolution: Reads block editor palettes from data-type configuration payloads, resolving contentElementTypeKey and settingsElementTypeKey GUIDs to documentable blocks. - Field type mapping: Maps data-type UDIs and editor aliases to readable field types, falling back to generated C# model property types when available. - Use Case: You inherit an Umbraco 17 site with 174 content types and no documentation. Use this Skill to resolve a document-type alias to its schema, model, and view, then backfill a behavioral feature doc with one scenario per Razor conditional branch. ## Quick Start Document the 'alertBanner' element type by reading its serialized schema, generated model, and Razor view from this Umbraco 17 repository.
