@vtex

vtex-io-events-and-workers covers async processing in vtex io through events and background handlers, with emphasis on idempotency, explicit state management, and failure visibility across retry-prone workflows.

vtex-io-app-settings covers defining, validating, and consuming app configuration through settingsSchema, with explicit guidance on schema structure, secret handling, backend-only patterns, and validation boundaries.

vtex-io-http-routes covers route declaration, handler structure, middleware composition, and HTTP contract enforcement for VTEX IO backend services. emphasizes explicit validation at boundaries, middleware reuse, and separation of synchronous HTTP concerns from async work.

vtex-io-storefront-react covers building shopper-facing react components for VTEX IO storefronts, emphasizing css-handles for styling, browser safety, localization patterns, and props-driven presentational design over ad hoc data fetching.

vtex-io-auth-and-policies covers manifest policy declarations, outbound-access scoping, and resource-based access control for vtex io apps. use when adding external integrations, consuming protected platform resources, or exposing access-controlled routes.

vtex-io-service-configuration-apps addresses structured config distribution across vtex io services via the configuration builder, covering entrypoint exposure, contract sharing, and lifecycle separation from runtime app management.

vtex-io-data-access-patterns guides decisions about where vtex io apps should persist and retrieve data across app settings, master data, vbase, and core apis, but lacks specific procedural steps or failure-mode coverage.

vtex-io-session-apps covers namespace ownership, input-output field declaration, and session state propagation for custom transforms. addresses debugging race conditions and b2b session flows but lacks concrete procedures.

vtex-io-react-apps covers frontside react component creation for store framework blocks, interfaces.json configuration, and site editor content schemas, but lacks procedural depth and failure recovery guidance.

framework guidance for evaluating vtex commerce architecture across storefront, headless, io, and marketplace systems, but lacks actionable procedure and decision logic needed to apply the model.

Apply when choosing which VTEX IO authentication token should back a request from a backend app. Covers `ctx.authToken`, `ctx.storeUserAuthToken`,…

Apply when implementing localization and translated copy in VTEX IO apps. Covers the `messages` builder, `/messages/*.json`, `context.json`, frontend message…

Apply when deciding whether and how VTEX IO apps should use Master Data v2 for custom data. Covers entity boundaries, schema lifecycle, indexing strategy, and…

Apply when working with GraphQL schema files in graphql/ or implementing resolvers in node/resolvers/ for VTEX IO apps. Covers schema.graphql definitions,…

Apply when building VTEX IO admin-facing React interfaces under the admin builder. Covers VTEX Styleguide and Shoreline usage, admin page composition,…

Apply when making VTEX IO services easier to observe, troubleshoot, and operate in production. Covers metrics, structured logging, failure visibility,…

Apply when reviewing or designing security-sensitive boundaries in VTEX IO apps. Covers public versus private exposure, trust assumptions at route and…

Apply when connecting React components to Store Framework blocks and render-runtime behavior in VTEX IO. Covers interfaces.json, block registration, block…

Apply when defining service.json routes, choosing public vs segment vs private URL prefixes for VTEX IO services, or setting HTTP cache headers that interact…

Apply when defining or changing the contract of a VTEX IO app through manifest.json, builder declarations, dependencies, peerDependencies, billingOptions, and…

Apply when designing or implementing the runtime structure of a VTEX IO backend app under node/. Covers the Service entrypoint, typed context and state,…

Apply when designing or implementing how a VTEX IO backend app integrates with VTEX services or external APIs through @vtex/api and @vtex/clients. Covers…

Apply when building backend service apps under node/ in a VTEX IO project or configuring service.json routes. Covers the Service class, middleware functions,…

Apply when improving VTEX IO Node or .NET services for latency, throughput, and resilience: in-process LRU, VBase, stale-while-revalidate, AppSettings loading,…

Apply when working with MasterData v2 entities, schemas, or MasterDataClient in VTEX IO apps, or when anyone designing or implementing a solution must…