Skip to main content
skill CX Codex

vtex-io-masterdata — Claude Code skill for VTEX IO Master Data

Walks you through Master Data v2 in VTEX IO apps and pushes back when the data belongs somewhere else.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add vtex/skills --skill vtex-io-masterdata -a claude-code
Open on GitHub

What vtex-io-masterdata does

The skill fires whenever a VTEX IO app needs its own persistence: reviews, wishlists, form submissions, config records. It does not jump straight to code. First it makes you argue why Master Data is the right store, because Catalog may fit product and SKU data better, OMS already owns orders, and an external database can win on workload shape.

Then the practical side. Entities and JSON Schema through the masterdata builder, CRUD via ctx.clients.masterdata, search and scroll, triggers on data changes, schema lifecycle. Synchronous Master Data calls on the purchase path — cart, payment, order placement — get their own treatment: without a latency budget and failure analysis, the skill says keep them out. Storefront and partner access goes through a service that handles auth and rate limits, not straight into the store.

Housekeeping is covered too: auditing existing entities, counting documents with REST-Content-Range headers, bulk imports as .jsonl with checkpoints and backoff on HTTP 429, and the 60-schema ceiling. App logs belong in the logger and caches in VBase, and the skill says so.

What it helps with

  • decide whether custom data needs a Master Data entity at all
  • define JSON Schema without burning through the schema limit
  • keep synchronous Master Data calls off the checkout path
  • import tens of thousands of documents without hitting 429 and restarting
  • sort logs, caches and business data into the right stores

Example prompts for the agent

  • Check with vtex-io-masterdata whether reviews belong in Master Data or Catalog
  • Define the entity and JSON Schema for a wishlist using the masterdata builder
  • Set up scrollDocuments and pagination for an entity with a large document count

How to install vtex-io-masterdata

1Skills CLI (Vercel)

npx skills add vtex/skills --skill vtex-io-masterdata -a claude-code

2Manually: put the files in place

~/.claude/skills/vtex-io-masterdata/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/vtex-io-masterdata/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about vtex-io-masterdata

How do I install vtex-io-masterdata in Claude?

Run npx skills add vtex/skills --skill vtex-io-masterdata -a claude-code. The skill file then sits at ~/.claude/skills/vtex-io-masterdata/SKILL.md.

What does vtex-io-masterdata do?

It covers Master Data v2 work in VTEX IO apps: entities, schemas, CRUD through MasterDataClient, search, triggers. It also questions whether Master Data is the right storage for the job at hand.

How is it different from the service app and GraphQL skills?

This one is about persistence in Master Data. General backend service patterns live in vtex-io-service-apps, GraphQL schemas in vtex-io-graphql-api, and manifest and builder config in vtex-io-app-structure.

Similar skills

Everything for Backend and APIs →

From the same set8

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor