masterdata-storage-strategy — Claude Code skill: how to install
Guides data architecture decisions in VTEX, helping configure Master Data JSON schemas with indexing, security, and caching rules before creating entities.
npx skills add vtex/skills --skill masterdata-storage-strategy -a claude-codeWhat masterdata-storage-strategy does
The skill establishes architectural rules for VTEX storage. It evaluates whether a workload belongs in Master Data or requires Catalog, OMS, VBase, or an external database. Master Data cannot sustain sub-10ms response times, so placing it in checkout or payment critical paths will hurt conversion rates.
Guidance covers VTEX-specific schema extensions, including v-indexed, v-cache, v-default-fields, and v-security. Only query filter fields belong in v-indexed. Every secondary index forces updates on every write, driving up latency and consuming storage.
Implementation code for VTEX IO clients is out of scope here; other repository skills handle client integration.
What it helps with
- select between Master Data, VBase, Catalog, and external SQL storage
- configure JSON schemas using
v-indexedandv-security - determine caching behavior via
v-cachefor high-write entities - audit existing entity schemas to remove unnecessary secondary indexes
Example prompts for the agent
- Evaluate whether Master Data or VBase is better for storing user session flags
- Design a JSON Schema with
v-indexedandv-securityfor a product wishlist entity - Check if my schema indexes too many fields for write-heavy workloads
How to install masterdata-storage-strategy
1Skills CLI (Vercel)
npx skills add vtex/skills --skill masterdata-storage-strategy -a claude-code2Manually: put the files in place
~/.claude/skills/masterdata-storage-strategy/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/masterdata-storage-strategy/
1Skills CLI (Vercel)
npx skills add vtex/skills --skill masterdata-storage-strategy -a codex2Manually: put the files in place
.agents/skills/masterdata-storage-strategy/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add vtex/skills --skill masterdata-storage-strategy -a cursor2Manually: put the files in place
.cursor/skills/masterdata-storage-strategy/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install vtex/skills masterdata-storage-strategy2Manually: put the files in place
.github/skills/masterdata-storage-strategy/SKILL.md1Skills CLI (Vercel)
npx skills add vtex/skills --skill masterdata-storage-strategy -a gemini-cli2Platform CLI
gemini skills install https://github.com/vtex/skills --path skills/masterdata-storage-strategyManually: put the files in place
.devin/skills/masterdata-storage-strategy/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add vtex/skills --skill masterdata-storage-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 masterdata-storage-strategy
How do I install masterdata-storage-strategy in Claude Code?
Run npx skills add vtex/skills --skill masterdata-storage-strategy -a claude-code. The skill file will be placed at ~/.claude/skills/masterdata-storage-strategy/SKILL.md.
What does this skill help with?
It guides schema design and storage choices in VTEX, preventing over-indexing and misuse of Master Data for checkout-critical flows.
When should you avoid VTEX Master Data?
Avoid Master Data for relational data requiring joins, high-throughput time-series records, or checkout paths where sub-10ms latency is mandatory.