# vtex-io-masterdata-strategy

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.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 1200 installs · ★ 47 repo stars
- Author: vtex
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/vtex/skills/tree/HEAD/skills/vtex-io-masterdata-strategy/SKILL.md
- Updated: 2026-10-14
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/vtex-io-masterdata-strategy

## What it 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`.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add vtex/skills --skill vtex-io-masterdata-strategy -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/vtex-io-masterdata-strategy/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/vtex-io-masterdata-strategy/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add vtex/skills --skill vtex-io-masterdata-strategy -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/vtex-io-masterdata-strategy/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add vtex/skills --skill vtex-io-masterdata-strategy -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/vtex-io-masterdata-strategy/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install vtex/skills skills/vtex-io-masterdata-strategy
```

2. **Manually: put the files in place**
- File: `.github/skills/vtex-io-masterdata-strategy/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add vtex/skills --skill vtex-io-masterdata-strategy -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/vtex/skills --path skills/vtex-io-masterdata-strategy
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/vtex-io-masterdata-strategy/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add vtex/skills --skill vtex-io-masterdata-strategy -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/vtex/skills/tree/HEAD/skills/vtex-io-masterdata-strategy/SKILL.md

## When to use it
- 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
- 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

## Similar
- [data-schema-knowledge-modeling](https://affpapa.org/en/nevibecode/skills/data-schema-knowledge-modeling.md) — skill · 159 installs
- [postgresql-table-design](https://affpapa.org/en/nevibecode/skills/postgresql-table-design.md) — skill · 27780 installs
- [Database Design Expert](https://affpapa.org/en/nevibecode/skills/database-design-expert.md) — skill · 278 installs
- [mcp-vtex](https://affpapa.org/en/nevibecode/mcp/mcp-vtex.md) — MCP server · ★ 279 repo stars
- [database-indexing-strategy](https://affpapa.org/en/nevibecode/skills/database-indexing-strategy.md) — skill · 492 installs
- [sap-btp-master-data-integration](https://affpapa.org/en/nevibecode/skills/sap-btp-master-data-integration.md) — skill · 838 installs

From the same set: [vtex/skills](https://affpapa.org/en/nevibecode/by/vtex/skills.md) — 46 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
