What problem does it solve? Localized content in Weegloo behaves differently on the management plane (CMA/ACMA) versus the delivery plane (CDA/ACDA), causing the common bug where fields.x[locale] returns undefined on delivery reads. This Skill clarifies default-locale requirements on create, fallbackCode chains on read, and the locale URL parameter shapes so you stop guessing which response shape to expect. ## Core Features & Use Cases - Write rules for localized fields: Explains that required localized fields need values under every non-optional locale, and that localized: false fields live only in the default-locale bucket. - Read shape by API plane: Documents that CMA/ACMA always return per-locale buckets while CDA/ACDA flatten to scalars unless locale=* is passed, for both list and detail endpoints. - Fallback and include expansion: Covers per-locale fallbackCode chains (no automatic fallback to default) and how expanded Media under the include object follows the same flattening rules. - Use Case: When a CDA detail fetch returns fields.prompt as a plain string and your code does fields.prompt["en-US"], use this Skill to diagnose the undefined result and fix the accessor for the correct plane. ## Quick Start Ask the agent to explain why a Weegloo CDA content read returns undefined when indexing fields by locale code and how to fix the field access.
