Skip to main content
skill CX Codex

vtex-io-masterdata-strategy — Claude Code skill: Master Data v2 design

vtex-io-masterdata-strategy guides decisions on when to use Master Data v2 for VTEX IO app storage and how to design schemas, indexing, and entity lifecycle.

no license 1,200 installs ★ 47 updated 2026-10-14

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

What vtex-io-masterdata-strategy does

The skill helps decide whether Master Data v2 fits a particular need — reviews, wishlists, forms — and how to structure the schema. The agent checks entity boundaries, picks fields to index, and plans schema versioning. It explains three approaches: using the masterdata builder when the app owns the model and rolls it out with releases, using only the client when the schema is shared and the app just reads or writes records, and applying a stable schema from code via a setup path when the app owns the schema but should not update it on every release.

The skill prohibits storing secrets, app configuration, or unbounded event logs in Master Data. Without a retention plan, Master Data fills up fast. The agent will flag schemas that blur entity boundaries or miss indexes for actual queries.

This skill applies after Master Data has been chosen; for comparing storage options, use vtex-io-data-access-patterns.

What it helps with

  • choose between masterdata builder and client for schema ownership
  • plan field indexing to match real query patterns
  • set up schema versioning and data retention
  • verify Master Data entity aligns with business concept boundaries

Example prompts for the agent

  • Check if I'm storing reviews in Master Data v2 correctly and whether I need indexes on productId and approved
  • Suggest a way to set up a wishlist schema without creating a new version on every app release
  • Explain why storing user action logs in Master Data is not a good fit

How to install vtex-io-masterdata-strategy

1Skills CLI (Vercel)

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

2Manually: put the files in place

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

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

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

Questions about vtex-io-masterdata-strategy

How to install vtex-io-masterdata-strategy in Claude Code?

Run npx skills add vtex/skills --skill vtex-io-masterdata-strategy -a claude-code, then open ~/.claude/skills/vtex-io-masterdata-strategy/SKILL.md.

What does vtex-io-masterdata-strategy do?

Helps decide when Master Data v2 is suitable for VTEX IO app storage and how to design schemas, indexing, and entity lifecycle. Guides schema ownership approach and prevents design mistakes.

When should I use the masterdata builder versus the client only?

Use the builder if the app owns the model and the schema evolves with the code. Use only the client if the schema is shared or centrally managed and the app just reads or writes records. A third option is keeping the schema in code and applying it through a setup path if the app owns the schema but should not update it every release.

Similar skills

All skills for Backend and APIs →

From the same set46

The whole set →
vtex-io-data-access-patterns vtex-io-data-access-patterns guides AI coding agents on picking the right storage layer across VTEX IO apps. It helps design read pipelines, caching strategies, and data boundaries. CX Codex +1 1,200installs vtex-io-auth-tokens-and-context vtex-io-auth-tokens-and-context is a Claude Code skill that selects the VTEX IO token for a backend request based on whether it comes from the app, a shopper, or an Admin user. CX Codex +1 1,200installs vtex-io-client-integration vtex-io-client-integration guides backend integrations in VTEX IO apps using @vtex/api and @vtex/clients. Helps select client classes, configure runtime options, and replace raw HTTP calls. CX Codex +1 1,200installs vtex-io-auth-and-policies The vtex-io-auth-and-policies skill guides VTEX IO permission design for integrations, protected routes, and manifest policies. Use it when access boundaries need review or change. CX Codex +1 1,200installs vtex-io-admin-react vtex-io-admin-react guides coding agents in building VTEX IO admin pages with React, enforcing official design systems, bounded tables, and predictable feedback states. CX Codex +1 1,200installs vtex-io-http-routes vtex-io-http-routes guides the design of HTTP endpoints in a VTEX IO backend service: route boundaries, middleware chains, request validation and response shape. CX Codex +1 1,200installs vtex-io-application-performance vtex-io-application-performance guides performance work on VTEX IO Node and .NET services, including cache choices, parallel client calls, and avoiding repeated work. CX Codex +1 1,200installs payment-provider-framework The payment-provider-framework skill guides VTEX IO payment connector work, from PPF wiring to Secure Proxy and build checks. Use it when implementing or maintaining a connector app. CX Codex +1 1,100installs

Project sponsors

Companies that keep this analytics open