Skip to main content
affpapa.org
RU EN
skill CX Codex

vtex-io-app-contract — Claude Code skill

Checks the VTEX IO app contract in manifest.json, including builders and dependency links. Use it when creating, splitting, or publishing apps.

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

What vtex-io-app-contract does

This skill reviews the parts that define a VTEX IO app: vendor, name, version, builder declarations, dependencies, peerDependencies, and billingOptions. It connects the manifest with the capabilities the app actually owns.

It helps choose builders for node, graphql, react, admin, store, messages, pixel, and masterdata, and flags cases where a separate app should own a capability. It also targets link and publish failures caused by manifest-level contract decisions.

An app that ships backend or GraphQL code without the matching builder in manifest.json has an incomplete contract, so the platform ignores that capability.

What it helps with

  • define a VTEX IO app contract in manifest.json
  • match builders to the app’s shipped capabilities
  • choose between dependencies and peerDependencies
  • trace link or publish failures to the manifest
  • check app identity and version before publishing

Example prompts for the agent

  • Review manifest.json for this VTEX IO app and recommend the builders it should declare.
  • Find capabilities that should move into a separate app because the manifest mixes unrelated responsibilities.
  • Investigate this publish failure by checking dependencies, peerDependencies, billingOptions, and the app version.

How to install vtex-io-app-contract

1Skills CLI (Vercel)

npx skills add vtex/skills --skill vtex-io-app-contract -a claude-code

2Manually: put the files in place

~/.claude/skills/vtex-io-app-contract/SKILL.md

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

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

Questions about vtex-io-app-contract

How do I install vtex-io-app-contract in Claude Code?

Run npx skills add vtex/skills --skill vtex-io-app-contract -a claude-code, then check ~/.claude/skills/vtex-io-app-contract/SKILL.md.

What does vtex-io-app-contract do?

It helps define and review a VTEX IO app contract through manifest.json, builders, dependency relationships, identity, and billing settings.

When should I use dependencies instead of peerDependencies?

Use dependencies for apps that can be installed automatically with the current app. Use peerDependencies for externally managed apps and apps that declare billingOptions.

Similar skills

All skills for Agent setup: memory, context, orchestration →
setup-matt-pocock-skills Matt Pocock This skill configures a repository for Matt Pocock's engineering skills by setting its issue tracker, triage labels, and domain docs layout. Run it before using the other skills. 1,052,851installs ask-matt Matt Pocock Routes you to the right Matt Pocock skill or flow for the task at hand. Use it when you need a starting point for a feature, prototype, incoming issue, or hard bug. 766,587installs to-tickets Matt Pocock Turns a plan, spec, or conversation into small end-to-end tickets with explicit blockers. Use it to agree on the work breakdown before tickets go to a tracker. 711,230installs writing-plans Jesse Vincent This skill turns requirements for a multi-step task into an implementation plan before code changes begin. It helps when another engineer needs exact files, interfaces, and checks. CX Codex 282,859installs caveman-review JuliusBrussee Turns code review comments into one line per finding: location, problem, fix. Useful when a diff or PR needs a fast pass without the filler. CX Codex +1 411,800installs caveman-compress JuliusBrussee Compresses CLAUDE.md, todo lists, and other prose files into a shorter format while retaining a readable backup. CX Codex +1 411,500installs

From the same set38

vtex-io-messages-and-i18n Keeps user-facing copy in the VTEX IO messages infrastructure instead of hardcoded strings in JSX and resolvers. CX Codex +1 1,100installs vtex-io-security-boundaries Guides coding assistants when auditing route exposure and data boundaries in VTEX IO apps. Prevents tenant leaks and enforces payload validation. CX Codex +1 1,100installs vtex-io-events-and-workers Guides the agent in writing VTEX IO event handlers and workers that survive duplicate delivery. Useful when slow work should leave your HTTP routes. CX Codex +1 1,100installs vtex-io-service-configuration-apps Guides the agent through building VTEX IO configuration apps using the configuration builder. Helps inject decoupled workspace settings into service runtimes. CX Codex +1 1,100installs vtex-io-service-runtime Guides the runtime layout of a VTEX IO backend app: the Service entrypoint, typed context, and service.json execution settings. CX Codex +1 1,100installs 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,100installs vtex-io-auth-tokens-and-context Decides which VTEX IO token should back a backend request: the app itself, a shopper, or an Admin user. CX Codex +1 1,100installs vtex-io-render-runtime-and-blocks Teaches the agent to expose React components as Store Framework blocks in VTEX IO: store/interfaces.json entries, composition and theme wiring. CX Codex +1 1,100installs

Project sponsors

Companies that keep this analytics open
Gold sponsor
Nutra.Club

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