What problem does it solve?
This Skill prevents unsafe or fragile use of VTEX IO App Settings by guiding how to define, validate, and consume merchant-configurable configuration without leaking secrets or turning settings into operational storage.
Core Features & Use Cases
- Schema-first app configuration: Model merchant-editable behavior with explicit
settingsSchema using clear JSON Schema properties, required, defaults, enums, and constraints.
- Safe backend consumption: Read settings through
ctx.clients.apps.getAppSettings(ctx.vtex.appId ?? process.env.VTEX_APP_ID), normalize at the consumption boundary, and apply resilient defaults when values are missing.
- Secret and frontend exposure guardrails: Keep API keys/tokens/passwords backend-only (no raw settings returned in HTTP/GraphQL/HTML/browser props) and ensure any
access: "public" settings contain only intentionally frontend-safe values.
Use case: You’re implementing a VTEX IO app that lets merchants configure moderation mode and an external service key—this Skill helps ensure the schema is correct, the secret never leaves the backend, and the UI only receives safe non-sensitive fields.
Quick Start
Apply this skill’s rules to your VTEX IO app by reviewing your proposed settingsSchema and the way your code reads and exposes settings, then tell me what to change to make it safe and schema-validated.