Agent guides

Enad entry points for agent-guided implementation.

Use this section when an agent needs the right Enad starting point. It covers SDK work, storefront UI, APIs, Search, Media, Events, and version tracks.

Give agents the right context

  • /llms.txt: short agent index with the safest starting points. Use this first for route choice.
  • /llms-full.txt: broader agent bundle. Use this when a task spans several Enad areas.
  • /ai/manifest.json: structured route, package-track, version, and copy guidance.
  • Agent files manifest: route and version browser for people reviewing agent inputs.

Choose one route first

Start with the narrowest agent route that matches the job. Use broader context only when the task spans multiple domains.

For safe context loading, start with Agent quickstart. It explains which files to give an agent first and which references own exact facts.

For MCP setup, use MCP server. It covers the hosted endpoint, Codex connector expectations, OAuth discovery, scopes, app context, and preview/apply workflow.

For app registration metadata, use Enad app auth.md. For file selection, use Agent files or Agent files manifest.

For prompt shape, use Prompt recipes. For React storefront work, start with React SDK agent guide, then narrow to discovery, theming, icons, or commerce handoff routes.

For server-side SDK work, use TypeScript SDK agent guide. For API, OpenAPI, Search GraphQL, Media, or Events routing, use API and Search agent guide.

If a task crosses several areas, start with /llms.txt for route choice.

Use /llms-full.txt only when broader context is needed. Then move to the narrowest route.

Public docs routes

Use these public routes when connecting packages, prompts, or tooling:

Theme and playground usage

Agents should use public consumer surfaces only:

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

Do not copy playground internals into applications. Use providers, theme helpers, generated CSS, documented component-set names, and the public playground export flow.

Agent guides

# Agent guides Use this section when an agent needs the right Enad starting point. It covers SDK work, storefront UI, APIs, Search, Media, Events, and version tracks. ## Give agents the right context - /llms.txt: short agent index with the safest starting points. Use this first for route choice. - /llms-full.txt: broader agent bundle. Use this when a task spans several Enad areas. - /ai/manifest.json: structured route, package-track, version, and copy guidance. - [Agent files manifest](/ai/manifest): route and version browser for people reviewing agent inputs. ## Choose one route first Start with the narrowest agent route that matches the job. Use broader context only when the task spans multiple domains. For safe context loading, start with [Agent quickstart](/ai/agent-quickstart). It explains which files to give an agent first and which references own exact facts. For MCP setup, use [MCP server](/ai/mcp-server). It covers the hosted endpoint, Codex connector expectations, OAuth discovery, scopes, app context, and preview/apply workflow. For app registration metadata, use [Enad app auth.md](/ai/enad-app-authmd). For file selection, use [Agent files](/ai/artifacts) or [Agent files manifest](/ai/manifest). For prompt shape, use [Prompt recipes](/ai/prompts). For React storefront work, start with [React SDK agent guide](/ai/react-sdk/latest), then narrow to discovery, theming, icons, or commerce handoff routes. For server-side SDK work, use [TypeScript SDK agent guide](/ai/ts-sdk/latest). For API, OpenAPI, Search GraphQL, Media, or Events routing, use [API and Search agent guide](/ai/apis/latest). If a task crosses several areas, start with /llms.txt for route choice. Use /llms-full.txt only when broader context is needed. Then move to the narrowest route. ## Public docs routes Use these public routes when connecting packages, prompts, or tooling: - [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). - [MCP server](/ai/mcp-server). - [Media](/media). - [Events](/events). - [Integrations](/integrations). - [Agent guides](/ai). ## Theme and playground usage 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 playground internals into applications. Use providers, theme helpers, generated CSS, documented component-set names, and the public playground export flow.