React SDK discovery and imports

Route agents to the right React SDK family and public import surface without inventing exports or props.

Start here when an agent needs to choose the right React SDK route, component family, or public import surface before writing code.

Contract scope

Use React SDK guides for route selection, component-family framing, and safe setup order.
Use SDK package reference for exact exports, props, hooks, child parts, and helper signatures.
Do not invent deep import paths from prose.
Do not copy playground route internals into an app just because a playground example exists.

Start with the documented public import surfaces

Use these confirmed setup imports directly:

import "@enadhq/enad-react-sdk/styles.css";
import { EnadProvider } from "@enadhq/enad-react-sdk";
import { EnadThemeProvider } from "@enadhq/enad-react-sdk/client/theme";

For grouped public barrels, documented storefront refinements, and the few retained deep exceptions, start with Import surfaces before guessing a path.

Treat everything beyond these setup imports as package-reference truth. When an agent needs a component, hook, helper, or child-part import, it should inspect package reference before writing code.

Route by job

Job	Start here	Why
Root setup and provider order	React SDK setup	Confirms stylesheet, `EnadProvider`, and `EnadThemeProvider` placement.
Choose a grouped public entry point or documented exception	Import surfaces	Keeps root setup imports, grouped barrels, and retained deep seams clear.
Build login, signup, password-reset, sign-out, or current-user UI	Account and auth UI	Keeps the public `client/user` surface aligned with runtime-adapter and Auth API boundaries.
Find the right component family	React SDK components	Groups the public docs by Base UI, Layout, Storefront, and Commerce.
Build shell chrome	Storefront page guide and Layout components	Keeps header, footer, navigation, and app-owned routing boundaries clear.
Build shopper-facing listing or search UI	Product listing and search	Separates Search GraphQL truth from React composition.
Build PDP or purchase-adjacent UI	Product detail page	Keeps display composition separate from cart and checkout side effects.
Apply theme hashes or component sets	React SDK theming and Theme from playground	Explains provider nesting, precedence, and playground handoff.
Feed an agent workflow	React SDK agent guide	Gives route selection plus package-boundary rules.

Discovery workflow for agents

Name the job first: setup, imports, auth/account, layout, storefront, commerce, Search, or theming.
Open the matching guide before guessing an import.
If the question is import-path selection, check Import surfaces before inventing a deeper path.
Verify the exact component or helper export in package reference.
Write the smallest example that stays on documented public package imports.
If the example depends on live Search, cart, client, or auth/session wiring, keep that integration at the app boundary rather than burying it inside presentational components.

Red flags

Stop and re-route before memory replaces package reference.