Use this guide when you are asking an agent to work with Enad docs, SDKs, APIs, Search, Media, Events, or theme setup.

Give the agent these files first

1. /llms.txt for the short routing index. Use it to choose the first route and avoid loading unrelated docs.
2. /llms-full.txt when the task spans multiple Enad domains or the agent cannot browse route-by-route.
3. /ai/manifest.json when the agent or tool can consume structured route data, version tracks, and copy-paste guidance.
4. The reference named by the relevant docs page when exact exports, props, operations, package versions, or API fields matter.

Use the smallest context that can answer the routing question, then add exact reference pages only for reference details.

Tell the agent the exact reference boundary

Copy these instructions into agent prompts:

• Use Enad docs for route selection.
• Do not invent exact facts from prose.
• Use the owning reference for SDK exports, props, API fields, Search schema, Media fields, event payloads, or package versions.
• Keep live playground internals inside the playground.

Choose the right agent route

Build storefront UI with React SDK agent guide, then verify exact props in React SDK.

Call APIs from server code with TypeScript SDK agent guide, then verify methods, types, and versions in TypeScript SDK.

Work with Search through API and Search agent guide, then use Search GraphQL latest. Keep app, market, store-group, and locale context explicit.

Use API and Search agent guide for HTTP APIs and OpenAPI-backed endpoint details. Verify endpoint fields and operations in API/OpenAPI reference before writing code.

Connect or use MCP through MCP server. For Codex, use the Enad App or connector OAuth flow when available; raw remote MCP config is not the complete protected-tool setup. Keep app context explicit and route writes through preview/apply.

Use Media for Media or DAM concepts. Verify asset schemas and upload contracts in the relevant API reference.

Use Events and Integrations for event or integration work. Preserve delivery boundaries and verify payload fields in Event catalog.

Restore a theme from the playground with React SDK agent guide and Prompt recipes. Use public provider/theme surfaces and keep playground internals in the playground.

Safe operating rules

• Keep docs.enad.io and production sdk.enad.io routing unchanged until launch readiness work explicitly changes them.
• Treat agent files as routing guidance, not as endpoint, schema, package, or prop truth.
• Use SDK package reference as the package boundary; do not depend on package README prose for exact facts.
• Prefer public imports from @enadhq/enad-react-sdk and @enadhq/enad-react-sdk/client/theme when React examples are needed.
• Keep live playground runtime, editor, and export behavior in the playground.
• Record compatibility needs for old /llms* URLs instead of deleting or silently replacing them.

Minimal prompt skeleton

You are working with Enad docs. Start from /llms.txt and /ai/manifest.json. Use /llms-full.txt only when the task spans domains or you need the complete docs bundle. Use Enad docs for guidance and route selection. Use SDK package reference, API/OpenAPI reference, Search reference, or the Event catalog for exact SDK exports, component props, API fields, Search schema details, event payloads, Media contracts, and package versions. Keep docs.enad.io and sdk.enad.io production routing unchanged unless the task explicitly says this is a launch-readiness phase.

Task: <describe the Enad SDK/API/Search/Media/Events/theme job>