vtex-io-app-settings

Enforce schema-driven VTEX IO app settings with safe backend consumption.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/exilonX/ap2 --skill vtex-io-app-settings-exilonx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vtex-io-app-settings
Source: https://github.com/exilonX/ap2/tree/main/.agents/skills/vtex-io-app-settings
Command: npx skills add https://github.com/exilonX/ap2 --skill vtex-io-app-settings-exilonx

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about vtex-io-app-settings

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent VTEX IO app settings from leaking secrets to the frontend?

To prevent leaking secrets in VTEX IO app settings, keep API keys and tokens backend-only by avoiding raw settings in HTTP, GraphQL, or HTML responses, and ensure only safe values use public access.

How do I define a JSON Schema for VTEX IO app settings?

Define VTEX IO app settings using a settingsSchema with explicit JSON Schema properties, required fields, defaults, enums, and constraints to model merchant-editable behavior safely.

What is the best way to read VTEX IO app settings securely in the backend?

The best way to read VTEX IO app settings securely is via ctx.clients.apps.getAppSettings, normalizing values at the consumption boundary and applying resilient defaults when values are missing.

Can I expose VTEX IO app configuration to the storefront frontend?

You can expose VTEX IO app configuration to the frontend using publicSettingsForApp, but only if the access is set to public and the fields contain exclusively frontend-safe, non-sensitive values.

Why does my VTEX IO app settings validation fail when merchants input invalid configurations?

VTEX IO app settings validation fails without explicit JSON Schema constraints and runtime normalization, which enforce configuration boundaries and apply defaults at the consumption boundary.

When should I restrict VTEX IO app settings to backend-only access?

Restrict VTEX IO app settings to backend-only access whenever they contain secrets like API keys, tokens, or passwords, ensuring sensitive settings are never leaked in responses, logs, or browser props.