When to use it

Use ProductTabs when a product detail page only needs a compact tab strip for a few parallel sections such as description, specifications, and reviews.

If the PDP body itself needs a richer long-form rhythm with downloads, shipping notes, care sections, or a clearer post-hero structure, start with ProductDetails instead.

If you need generic tabs outside a product context (account settings, category content), use the base Tabs primitive instead. ProductTabs is specifically styled and structured for PDP use.

Composition notes

ProductTabs is prop-driven, not a compound composition:

• tabs is an array of tab objects, each with an id (unique string), label (visible tab text), and content (ReactNode panel body).
• defaultTab sets which tab is active initially. If omitted, the first tab opens.
• The component renders the tab triggers and panels internally.

Behavior and theming guidance

Tab divider color responds to --enad-border-color and the active tab accent responds to --enad-button-bg, so the tabs integrate with the active theme automatically.

The tab row is horizontally scrollable on narrow screens. Keep the number of tabs between 2 and 5 for scanability. If the page starts needing more sections or mixed section types, move up to ProductDetails instead of stretching the tab pattern too far.