AI Docs

# AI Docs Docs is the canonical home for Enad AI-facing documentation. Use this section when you are giving an AI agent enough context to choose SDK surfaces, compose storefront UI, call APIs, use Search, work with Media or Events, or restore a playground theme safely. ## Static AI entrypoints - /llms.txt: short AI index with the safest starting points. Use this first for route choice. - /llms-full.txt: full AI docs bundle generated from docs AI pages. Use this when a task spans domains or the agent cannot browse route-by-route. - /ai/manifest.json: machine-readable manifest with route, package, version, source path, and copy-paste safety metadata. ## Choose one route first Start with the narrowest authored AI route that matches the job. Use broader artifacts only when the task spans multiple domains. | Job | Start route | Exact facts live in | | --- | --- | --- | | Give an agent safe Enad context fast | [Agent quickstart](/ai/agent-quickstart) | linked docs routes and generated/package truth sources | | Explain what the AI artifacts are for | [AI artifacts and manifest](/ai/artifacts) | generated `/llms.txt`, `/llms-full.txt`, and `/ai/manifest.json` outputs | | Copy a prompt skeleton without widening scope | [Prompt recipes](/ai/prompts) | the destination route and its owning generated/source artifacts | | Build React storefront or theme work | [React SDK AI guide](/ai/react-sdk/latest) | package artifacts and public React docs routes | | Choose React imports or component family before coding | [React SDK AI discovery and imports](/ai/react-sdk/latest/discovery) | generated package artifacts and package source | | Restore a playground theme or reason about component sets/icons | [React SDK AI theme and icons](/ai/react-sdk/latest/theme-and-icons) | package artifacts and playground export flow | | Split shopper UI work from Search or purchase-side truth | [React SDK AI commerce and Search handoff](/ai/react-sdk/latest/commerce-search-handoff) | React docs routes, Search docs, and owning commerce/API sources | | Use the TypeScript SDK or package Search helpers | [TypeScript SDK AI guide](/ai/ts-sdk/latest) | package artifacts, package source, and generated API truth | | Reason about APIs, OpenAPI, or Search GraphQL | [API and Search AI guide](/ai/apis/latest) | generated reference, OpenAPI specs, and generated Search artifacts | If a task crosses several areas, start with /llms.txt for route choice or /llms-full.txt for the generated multi-domain bundle, then hand off to the narrowest authored route before writing code. ## Source-of-truth boundary AI docs can explain how to use Enad, but they must not become the hand-maintained source of SDK or API facts. - SDK exports, component props, hooks, Search client helpers, generated Search documents, and runtime behavior stay authoritative in `enad-packages`. - docs-v3 should consume `docs-artifacts/enad-packages-manifest.json` for package truth instead of scraping package README prose. - API endpoint truth stays generated from API/OpenAPI sources. - Media contracts, event payloads, integration details, and delivery semantics stay in their owning source or generated artifacts. - Theme-playground stays the runtime sandbox and export lab. - Docs owns human docs, AI docs, manifests, and static llms entrypoints. ## Current stable docs-v3 routes Package docs and AI agents should prefer these public routes: - [React SDK](/react-sdk/latest) - [React SDK setup](/react-sdk/latest/setup) - [React product listing and search](/react-sdk/latest/guides/product-listing-search) - [TypeScript SDK](/ts-sdk/latest) - [Search GraphQL latest](/search/latest) - [Search GraphQL reference latest](/reference/search-graphql/latest) - [APIs](/apis) - [Media](/media) - [Events](/events) - [Integrations](/integrations) - [AI Docs](/ai) `/reference/search-graphql/latest` is now a public route, but it is reference-compatible source-pending guidance rather than a generated schema reference. ## Theme and playground boundary Agents should use public consumer surfaces only: ```tsx import { EnadProvider } from "@enadhq/enad-react-sdk"; import { EnadThemeProvider } from "@enadhq/enad-react-sdk/client/theme"; ``` Do not copy theme-playground internals or route code into applications. Use providers, theme helpers, generated CSS, documented component-set names, and the public playground export flow.