faststore-overrides

Override FastStore sections via getOverriddenSection within src/components/overrides.

39|9|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/vtexdocs/ai-skills --skill faststore-overrides
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: faststore-overrides
Source: https://github.com/vtexdocs/ai-skills/tree/main/tracks/faststore/skills/faststore-overrides
Command: npx skills add https://github.com/vtexdocs/ai-skills --skill faststore-overrides

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Customizing FastStore storefront behavior often requires altering core code or resorting to brittle wrappers. This Skill provides a safe, standard approach to modify native sections via the public override API, avoiding edits to node_modules and preserving upgrade compatibility.

Core Features & Use Cases

  • Use getOverriddenSection to replace a native component entirely or modify its props within a target section.
  • Organize overrides under src/components/overrides/ and reference only public APIs from @faststore/core.
  • Apply overrides to specific sections while ensuring only documented overridable components are touched.

Quick Start

Create an override file under src/components/overrides named after the target section and configure getOverriddenSection to replace a native component.

Frequently Asked Questions about faststore-overrides

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

FAQPage Schema
How do I override native FastStore sections without editing node_modules?

To override FastStore sections safely, use the getOverriddenSection API to customize components or props within src/components/overrides, avoiding direct edits to node_modules and preserving upgrade compatibility.

When should I use getOverriddenSection instead of design tokens in FastStore?

Use getOverriddenSection when design tokens and theming are insufficient, such as when you need full component replacement or prop modification within FastStore sections that styling alone cannot achieve.

Can I replace an entire FastStore component or just modify its props?

FastStore overrides support both full component replacement and prop modification via getOverriddenSection, allowing you to customize native sections by either swapping components entirely or adjusting their props.

What are the limitations of customizing FastStore components through overrides?

FastStore overrides are constrained to only documented overridable components, must be placed under src/components/overrides, and can only import public APIs from @faststore/core, preventing edits to internal or undocumented modules.

How do I set up a FastStore override file for a specific section?

Create an override file under src/components/overrides named after the target FastStore section, then configure getOverriddenSection to replace or modify the native component using public APIs from @faststore/core.