Sales 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.
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 sales-app-extensibilitygit clone --depth 1 https://github.com/vtex/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/exports/opencode/sales-app-extensibility ~/.claude/skills/sales-app-extensibilityPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Sales App Extensibility ## When this skill applies Use this skill when building, customizing, or deploying extensions for VTEX Sales App. - Adding features to the cart page (promotions, loyalty, services) - Adding features to the Product Detail Page (badges, recommendations, warranties) - Adding features to the menu (user profile, navigation, metrics) - Integrating external APIs into Sales App extensions - Generating, scaffolding, or validating extension code for Sales App Do not use this skill for: - Regular FastStore storefront customization (use `faststore-storefront`) - Building VTEX IO apps (use `vtex-io-*` skills) - Sales App core development or framework modifications ### Prerequisite: FastStore project The project root must contain: `biome.json`, `faststore.json`, `package.json`, `tsconfig.json`, `turbo.json`. If any are missing, **STOP**. The user must install FastStore first: ```bash npx @vtex/fsp-cli init # Prompt: "What is the application name?" → enter name or press Enter for default cd <application-name> && yarn ``` Documentation: https://beta.fast.store/getting-started ### Prerequisite: Sales App module Inside the FastStore project, a Sales App workspace must exist (typically at `packages/sales-app`) with `src/`, `package.json`, and `tsconfig.json`. Check root `package.json` `"workspaces"` for a path containing `sales-app`. If missing, **STOP**:
Details
- Skill name
sales-app-extensibility- Repository
- vtex/skills
- Path
exports/opencode/sales-app-extensibility/SKILL.md- Repo updated
- 14 October 2026
FAQ
What does the Sales App Extensibility skill do?
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.
How do I install the Sales App Extensibility 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 Sales App Extensibility 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.
Vtex Io App Contract
47vtex/skills
Apply when defining or changing the contract of a VTEX IO app through manifest.json, builder declarations, dependencies, peerDependencies, billingOptions, and app identity. Covers how the app declares capabilities and integration boundaries. Use for scaffolding apps, splitting responsibilities across apps, or fixing contract-level link and publish issues.
Upwork
39ShawhinT/non-coding-skills
Source and qualify inbound-style leads for AI Builder Academy from Upwork job postings, then draft the proposal for one worth applying to. Sourcing: scrape search results, filter against ABA's ideal customer profile, infer the posting company and research its headcount, and return a ranked shortlist with buyer-quality signals. Proposals: extract every question the posting asks, collect Shaw's dictated answers, and render them in his voice with proof pulled from past clients. Use whenever Shaw mentions Upwork at all — "check Upwork for leads", "any good Upwork postings", "is there demand on Upw
Vtex Io Http Routes
47vtex/skills
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.
Browse the most popular Claude skills, all marketing, sales & business skills, or write your own with the skills generator.