Vtex Io Service Configuration Apps
Apply when designing VTEX IO configuration apps with the configuration builder or when a service app must receive structured configuration through runtime context. Covers the separation between service apps and configuration apps, schema.json and configuration.json, settingsType, and reading injected configuration through ctx.vtex.settings. Use for shared service configuration, decoupled configuration lifecycle, or reviewing whether app settings should be replaced by a configuration app.
Install
/plugin marketplace add vtex/skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add vtex/skills --skill vtex-io-service-configuration-appsgit clone --depth 1 https://github.com/vtex/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/exports/opencode/vtex-io-service-configuration-apps ~/.claude/skills/vtex-io-service-configuration-appsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Service Configuration Apps ## When this skill applies Use this skill when a VTEX IO service should receive structured configuration from another app through the `configuration` builder instead of relying only on local app settings. - Creating a configuration app with the `configuration` builder - Exposing configuration entrypoints from a service app - Sharing one configuration contract across multiple services or apps - Separating configuration lifecycle from runtime app lifecycle - Reading injected configuration through `ctx.vtex.settings` Do not use this skill for: - simple app-local configuration managed only through `settingsSchema` - Store Framework block settings through `contentSchemas.json` - generic service runtime wiring unrelated to configuration - policy design beyond the configuration-specific permissions required ## Decision rules - Treat the service app and the configuration app as separate responsibilities. - The service app owns runtime (`node`, `graphql`, etc.), declares the `configuration` builder in `manifest.json`, defines `configuration/schema.json`, and reads injected values through `ctx.vtex.settings`. - The configuration app does not own the service runtime. It should not declare `node` or `graphql` builders and usually has only the `configuration` builder. - The configuration app points to the target service in the `configuration` field and provides concrete values in `<service-app>/configuration.json`.
Details
- Skill name
vtex-io-service-configuration-apps- Repository
- vtex/skills
- Path
exports/opencode/vtex-io-service-configuration-apps/SKILL.md- Repo updated
- 14 October 2026
FAQ
What does the Vtex Io Service Configuration Apps skill do?
Apply when designing VTEX IO configuration apps with the configuration builder or when a service app must receive structured configuration through runtime context. Covers the separation between service apps and configuration apps, schema.json and configuration.json, settingsType, and reading injected configuration through ctx.vtex.settings. Use for shared service configuration, decoupled configuration lifecycle, or reviewing whether app settings should be replaced by a configuration app.
How do I install the Vtex Io Service Configuration Apps skill?
Claude Code plugin: /plugin marketplace add vtex/skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Vtex Io Service Configuration Apps popular?
It lives in vtex/skills, which has 47 GitHub stars and 9 forks.
Related skills
Architecture Well Architected Commerce
47vtex/skills
Apply when scoping, reviewing, or documenting cross-cutting VTEX commerce architecture across storefront, IO, headless, marketplace, payments, or any other VTEX module. Grounds work in the Well-Architected Commerce framework—Technical Foundation (reliability, trust, integrity; security, infrastructure, compliance), Future-proof (innovation, simplicity, efficiency; scalable and adaptable solutions), and Operational Excellence (accuracy, accountability, data-driven improvement; process and customer experience). Routes implementation detail to product tracks (IO caching and paths, Master Data str
Faststore Storefront
47vtex/skills
Core coding rules and workflow for developing VTEX FastStore storefronts. Use when starting any FastStore development task, writing TypeScript/React components, creating section overrides, extending the BFF, or styling. Covers all primary conventions, safety rules, and the development workflow used across every FastStore project.
Headless Bff Architecture
47vtex/skills
Apply when designing or modifying a BFF (Backend-for-Frontend) layer, middleware, or API proxy for a headless VTEX storefront. Covers BFF middleware architecture, public vs private API classification, VtexIdclientAutCookie management, API key protection, and secure request proxying. Use for any headless commerce project that must never expose VTEX_APP_KEY or call private VTEX APIs from the browser.
App Project Kickoff
44SamueleBassoli/hermes-fleet-apps
Use when the owner wants an app built or an old tool rewritten.
Vtex Io Rbac
47vtex/skills
Apply when controlling access to VTEX IO app resources using role-based or resource-based policies. Covers policies.json for role-based access control, service.json policies for resource-based access, VRN syntax for principals, the difference between app-to-app and user/integration access, and GraphQL @auth directives. Use when deciding how to secure routes and restrict which apps, users, or integrations can access your endpoints.
Context Acquisition
44SamueleBassoli/hermes-fleet-apps
Use when a session starts from a handoff brief. Read once.
Browse the most popular Claude skills, all other skills, or write your own with the skills generator.