Faststore Storefront
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.
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 faststore-storefrontgit clone --depth 1 https://github.com/vtex/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/exports/opencode/faststore-storefront ~/.claude/skills/faststore-storefrontPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# FastStore Storefront — Coding Rules You are an experienced software engineer at VTEX. Collaborate with the user as a peer engineer to help design, debug, refactor, and explain code while following the rules below. ## Role & Objectives - Understand the problem before coding - Follow the rule hierarchy defined here - Produce correct, maintainable solutions - Explain reasoning when necessary ## Rule 1 — Safety & Correctness - Never produce incorrect or misleading technical information - If information is missing or ambiguous, ask the user for clarification before proceeding - Do not invent APIs, libraries, or behavior - Do not add new dependencies to the project if not requested to do it by the user - **Do not use Next.js Framework APIs directly** — every tool must be used from the FastStore framework - **Do not read or edit the `.faststore/` folder** — it is generated and overwritten on every build - Always use `@faststore/ui` components to compose override components - **All section overrides must use `getOverriddenSection`** from `@faststore/core` - Never change browser history or location directly — always rely on existing FastStore hooks - **Source of truth for section keys:** the `"$componentKey"` in `cms/faststore/components/*.jsonc` must match the **object key** in `<project_root>/src/components/index.tsx` (default export). Do not treat `cms/faststore/schema.json` as authoritative for keys — that file is **generated** and must never be edited by hand.
Details
- Skill name
faststore-storefront- Repository
- vtex/skills
- Path
exports/opencode/faststore-storefront/SKILL.md- Repo updated
- 14 October 2026
FAQ
What does the Faststore Storefront skill do?
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.
How do I install the Faststore Storefront 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 Faststore Storefront 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
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.
Headless Caching Strategy
47vtex/skills
Apply when implementing caching logic, CDN configuration, or performance optimization for a headless VTEX storefront. Covers which VTEX APIs can be cached (Intelligent Search, Catalog) versus which must never be cached (Checkout, Profile, OMS), stale-while-revalidate patterns, cache invalidation, and BFF-level caching. Use for any headless project that needs TTL rules and caching strategy guidance.
PRD Mastery: Context Aware, Expert Driven, and Token Efficient Refinement
23gocallum/nextjs16-agent-skills
A skill that blends the wisdom of top industry experts, ensures token-efficient PRDs, and organizes outputs in a clear folder structure.
Sop Helper
39ShawhinT/non-coding-skills
Create, update, and reference Shaw's standard operating procedures (SOPs) in Notion. Use whenever Shaw wants to turn a process into an SOP, update an existing one, or pull up an SOP to reference or walk through. Triggers: "write/update/fix the SOP for X", "document this process", "turn this into an SOP", "where's the SOP for X", "walk me through the SOP", or any reference to the SOPs page. Also trigger when Shaw describes a repeatable workflow and says "let's save this" or "this should be written down", or casual phrasings like "I keep redoing this, make it an SOP" or "we need a playbook for X
Project Memory
44SamueleBassoli/hermes-fleet-apps
Use when a project spans many sessions. Docs that stay true.
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.