vtex
44 skills with substantive source documentation and an official publisher or observed installation demand. Read each skill’s original documentation through its card.
vtexpayment-async-flow
Apply when implementing asynchronous payment methods (Boleto, Pix, bank redirects) or working with callback URLs in payment connector code. Covers undefined status response, callbackUrl notification, X-VTEX-signature validation, sync vs async handling, correct delayToCancel configuration for each async method, and redirect-based flows where inboundRequestsUrl does not support browser GET redirects (requires custom public routes).
- installs
- 1
- GitHub stars
- 46
- Updated
- Oct 14
vtexpayment-pci-security
Apply when handling credit card data, implementing secureProxyUrl flows, or working with payment security and proxy code. Covers PCI DSS compliance, Secure Proxy card tokenization, sensitive data handling rules, X-PROVIDER-Forward-To header usage, custom token creation, and the constraint that Secure Proxy applies only to card authorization (not post-auth operations like cancel, capture, or refund). Use for any payment connector that processes credit, debit, or co-branded card payments to preven
- installs
- 1
- GitHub stars
- 46
- Updated
- Oct 14
vtexpayment-provider-framework
Apply when designing or implementing a Payment Connector in VTEX IO. Covers PPF implementation, TypeScript 3.9.7 builder-hub constraints and safe dependency resolutions, configuration.json schema validation, PaymentProviderService clients wiring, Secure Proxy scope (authorize-only), ExternalClient vs SecureExternalClient patterns, IOContext access, PPF response helpers, PSP integration checklist, and vtex link debugging. Use for any implementation of a Payment Connector hosted in VTEX IO.
- installs
- 1
- GitHub stars
- 46
- Updated
- Oct 14
vtexpayment-provider-protocol
Apply when implementing a VTEX Payment Provider Protocol (PPP) connector or working with payment/connector endpoint files. Covers all nine required endpoints: Manifest, Create Payment, Cancel, Capture/Settle, Refund, Inbound Request, Create Auth Token, Provider Auth Redirect, and Get Credentials. Use for building or debugging any payment connector that integrates with the VTEX Payment Gateway.
- installs
- 1
- GitHub stars
- 46
- Updated
- Oct 14
vtexsales-app-extensibility
Apply when building, customizing, or deploying extensions for VTEX Sales App. Covers the complete 7-step workflow from prerequisite checks through code generation to deployment, including extension points (cart, PDP, menu), React hooks (useCart, usePDP, useCartItem, useCurrentUser, useExtension), TypeScript types, secure API integration patterns, and API documentation ingestion (OpenAPI, URLs, or inline specs) to generate typed integrations.
- installs
- 1
- GitHub stars
- 46
- Updated
- Oct 14
vtexvtex-io-app-settings
Apply when defining, validating, or consuming VTEX IO app settings. Covers settingsSchema, app-level configuration boundaries, and how backend or frontend code should depend on settings safely. Use for merchant-configurable behavior, settings forms, or reviewing whether settings belong in app configuration rather than hardcoded logic or custom data entities.
- installs
- 1
- GitHub stars
- 46
- Updated
- Oct 14
vtexvtex-io-application-performance
Apply when improving VTEX IO Node or .NET services for latency, throughput, and resilience: in-process LRU, VBase, stale-while-revalidate, AppSettings loading, request context, parallel client calls, and avoiding duplicate work. Covers application-level performance patterns that complement edge/CDN caching. Use when optimizing backends beyond route-level Cache-Control.
- installs
- 1
- GitHub stars
- 46
- Updated
- Oct 14
vtexvtex-io-client-integration
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 choosing the correct client type, registering clients in IOClients, configuring InstanceOptions, and consuming integrations through ctx.clients. Use for custom client design, VTEX Core Commerce integrations, or reviewing backend code that should use VTEX IO client patterns instead of raw HTTP libraries.
- installs
- 1
- GitHub stars
- 46
- Updated
- Oct 14
vtexvtex-io-data-access-patterns
Apply when deciding where and how a VTEX IO app should store and read data. Covers when to use app settings, configuration apps, Master Data, VBase, VTEX core APIs, or external stores, and how to avoid duplicating sources of truth or abusing configuration stores for operational data. Use for new data flows, caching decisions, refactors, or reviewing suspicious storage and access patterns in VTEX IO apps.
- installs
- 1
- GitHub stars
- 46
- Updated
- Oct 14
vtexvtex-io-http-routes
Apply when designing or implementing HTTP endpoints exposed by a VTEX IO backend service. Covers route boundaries, handler structure, middleware composition, request validation, and response modeling for service.json routes. Use for webhook endpoints, partner integrations, callback APIs, or reviewing VTEX IO handlers that should expose explicit HTTP contracts.
- installs
- 1
- GitHub stars
- 46
- Updated
- Oct 14
vtexvtex-io-masterdata-strategy
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 when Master Data is the right storage mechanism versus another data approach. Use for reviews, wishlists, forms, or other custom data modeling decisions in VTEX IO apps.
- installs
- 1
- GitHub stars
- 46
- Updated
- Oct 14
vtexvtex-io-rbac
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.
- installs
- 1
- GitHub stars
- 46
- Updated
- Oct 14
vtexvtex-io-react-apps
Apply when building React components under react/ or configuring store blocks in store/ for VTEX IO apps. Covers interfaces.json, contentSchemas.json for Site Editor, VTEX Styleguide for admin apps, and css-handles for storefront styling. Use for creating custom storefront components, admin panels, pixel apps, or any frontend development within the VTEX IO react builder ecosystem.
- installs
- 1
- GitHub stars
- 45
- Updated
- Oct 5
vtexvtex-io-render-runtime-and-blocks
Apply when connecting React components to Store Framework blocks and render-runtime behavior in VTEX IO. Covers interfaces.json, block registration, block composition, and how storefront components become configurable theme blocks. Use for block mapping, theme integration, or reviewing whether a React component is correctly exposed to Store Framework.
- installs
- 1
- GitHub stars
- 46
- Updated
- Oct 14
vtexvtex-io-service-apps
Apply when building backend service apps under node/ in a VTEX IO project or configuring service.json routes. Covers the Service class, middleware functions, ctx.clients pattern, JanusClient, ExternalClient, MasterDataClient, and IOClients registration. Use for implementing backend APIs, event handlers, or integrations that must use @vtex/api clients instead of raw HTTP libraries.
- installs
- 1
- GitHub stars
- 46
- Updated
- Oct 14
vtexvtex-io-service-paths-and-cdn
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 with the VTEX edge and CDN. Covers path patterns, cookie visibility, edge caching behavior, and aligning Cache-Control with data sensitivity. Use for Node or .NET IO backends where request path and response headers determine CDN safety.
- installs
- 1
- GitHub stars
- 46
- Updated
- Oct 14
vtexvtex-io-service-runtime
Apply when designing or implementing the runtime structure of a VTEX IO backend app under node/. Covers the Service entrypoint, typed context and state, service.json runtime configuration, and how routes, events, and GraphQL handlers are registered and executed. Use for structuring backend apps, defining runtime boundaries, or fixing execution-model issues in VTEX IO services.
- installs
- 1
- GitHub stars
- 46
- Updated
- Oct 14
vtexvtex-io-session-apps
Apply when building or debugging a VTEX IO session transform app (vtex.session integration). Covers namespace ownership, input-vs-output fields, transform ordering (DAG), public-as-input vs private-as-read model, cross-namespace propagation, configuration.json contracts, caching inside transforms, and frontend session consumption. Use when designing session-derived state for B2B, pricing, regionalization, or custom storefront context.
- installs
- 1
- GitHub stars
- 46
- Updated
- Oct 14
vtexvtex-io-storefront-theme-app
Apply when designing or modifying a VTEX IO storefront theme app — the app that owns store/blocks.json, store/routes.json, store/templates/, store/contentSchemas.json, and the storefront page tree assembled from store.home, store.product, store.search, store.custom, and other native page templates. Covers how a theme app extends a base theme, declares routes, composes blocks across pages, and how its store/ files relate to merchant Site Editor content. Use for theme scaffolding, custom page rout
- installs
- 1
- GitHub stars
- 46
- Updated
- Oct 14
vtexvtex-io-storefront-theme-versioning
Apply when installing, publishing, upgrading, or rolling back a VTEX IO storefront theme app (vendor.store-theme or any app that owns store/blocks.json, store/routes.json, and store/contentSchemas.json). Covers how Site Editor and theme content are scoped by the app's MAJOR version, why a major version bump leaves the new major with no merchant content and silently falls back to default theme content, the safe install-in-workspace, migrate- content with the updateThemeIds mutation, smoke-test, t
- installs
- 1
- GitHub stars
- 46
- Updated
- Oct 14