Master Data storage strategy

When this skill applies

Use this skill before creating any new Master Data entity or when auditing existing usage. It helps you answer:

Is Master Data the right storage for this data, or would Catalog, OMS, VBase, or an external database serve better?
How should I design the JSON Schema for performance and security?
Which fields should I index (v-indexed), and which should I not?
Should I enable or disable caching (v-cache)?
Do I need triggers (v-triggers), or is an event-driven IO approach better?
How do I plan for capacity and lifecycle of schemas and documents?

Do not use this skill for:

VTEX IO app integration patterns (MasterDataClient, masterdata builder, CRUD in code) — use vtex-io-masterdata
Performance patterns for IO services (LRU, VBase caching layers) — use vtex-io-application-performance