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
npx skills add vtex/skills --skill vtex-io-masterdata-strategy -a claude-codeWhat 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
masterdatabuilder 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
productIdandapproved - 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-code2Manually: put the files in place
~/.claude/skills/vtex-io-masterdata-strategy/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/vtex-io-masterdata-strategy/
1Skills CLI (Vercel)
npx skills add vtex/skills --skill vtex-io-masterdata-strategy -a codex2Manually: put the files in place
.agents/skills/vtex-io-masterdata-strategy/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add vtex/skills --skill vtex-io-masterdata-strategy -a cursor2Manually: put the files in place
.cursor/skills/vtex-io-masterdata-strategy/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install vtex/skills skills/vtex-io-masterdata-strategy2Manually: put the files in place
.github/skills/vtex-io-masterdata-strategy/SKILL.md1Skills CLI (Vercel)
npx skills add vtex/skills --skill vtex-io-masterdata-strategy -a gemini-cli2Platform CLI
gemini skills install https://github.com/vtex/skills --path skills/vtex-io-masterdata-strategyManually: put the files in place
.devin/skills/vtex-io-masterdata-strategy/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add vtex/skills --skill vtex-io-masterdata-strategy -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
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.