vtex-io-masterdata

Evaluate Master Data v2 for persistence and implement JSON Schemas and CRUD in VTEX IO apps.

39|9|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/vtex/ai-skills --skill vtex-io-masterdata-vtex
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vtex-io-masterdata
Source: https://github.com/vtex/ai-skills/tree/main/tracks/vtex-io/skills/vtex-io-masterdata
Command: npx skills add https://github.com/vtex/ai-skills --skill vtex-io-masterdata-vtex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

VTEX IO apps often need a structured persistence layer for custom data. This skill provides governance-minded guidance to decide when Master Data v2 is appropriate, and to implement schemas, CRUD, and lifecycle practices that prevent misuses such as data duplication or unsafe patterns.

Core Features & Use Cases

  • Guides architects and developers to evaluate Master Data v2 as the right storage solution for custom business data in VTEX IO.
  • Covers JSON Schema creation, CRUD operations via MasterDataClient, triggers, and schema lifecycle, including handling the 60-schema limit.
  • Provides decision rules and governance patterns to avoid using Master Data as a log, cache, or parallel source of truth.

Quick Start

Use the Master Data v2 builder to safely implement schemas, CRUD, and governance in your VTEX IO app.

Frequently Asked Questions about vtex-io-masterdata

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement a persistence layer for custom data in VTEX IO apps?

To implement a persistence layer for custom data in VTEX IO apps, use Master Data v2 to define JSON Schemas, execute CRUD operations via MasterDataClient, and apply governance patterns to prevent data duplication.

When should I use Master Data v2 for custom business data instead of other storage?

Use Master Data v2 for custom business data when you need structured persistence with JSON Schemas and triggers, but avoid using it as a log, cache, or parallel source of truth to prevent unsafe architectural patterns.

What is the best way to manage JSON Schema lifecycle and limits in VTEX IO Master Data?

The best way to manage JSON Schema lifecycle in VTEX IO Master Data is to apply decision rules for schema creation and handle the 60-schema limit by safely governing data entities across your projects.

How do I execute CRUD operations safely using MasterDataClient in VTEX IO?

To execute CRUD operations safely using MasterDataClient in VTEX IO, follow the MasterDataClient usage pattern provided by the builder to enforce schema governance and avoid misuse on critical paths.

What are the limitations of using Master Data as a persistence layer in VTEX IO?

Limitations of using Master Data as a persistence layer in VTEX IO include a strict 60-schema limit per project and architectural constraints preventing its use as a log, cache, or parallel source of truth.