Skip to content
Resources

Building storefronts with AI tools

AI-powered editors and agentic coding tools start from solid general knowledge of the web, Adobe Commerce, and documentation conventions. They still fall behind on the newest storefront APIs, drop-in versions, and Edge Delivery Services-specific guidance until training data or tools update. You can narrow the gap with the static bundles this site publishes for machine consumption. The table below lists the main ones.

The bundles below are plain-text exports from the same source as the in-browser pages. They are Markdown-oriented and built for AI tools and scripts, not a replacement for reading the site.

FilePurpose
llms.txtIndex file: overview and links to all documentation sets (full, abridged, and topic bundles under _llms-txt).
llms-full.txtComplete documentation in one file.
llms-small.txtAbridged bundle (same content as the full export except the long-form release changelog page).
_llms-txt/*.txtSmaller topical exports (for example, drop-ins reference, tutorials, blocks). All bundle URLs are listed from llms.txt.

These files are large. Loading a whole file uses many tokens in a model context. They are rebuilt every time the site is published, so treat them as a fallback when an AI tool cannot search or fetch the live docs. Whenever possible, browse or search this site on Experience League for the latest edits, navigation, and diagrams.

Add this documentation site as a docs source in Cursor Settings → Features → Docs. Cursor will index and refer to the docs when answering questions about this codebase. You can also paste a topical bundle (for example, llms-small.txt or a specific _llms-txt/*.txt file) directly into chat when you need targeted context.

Reference the documentation URL in a prompt or in your project’s CLAUDE.md file:

See https://experienceleague.adobe.com/developer/commerce/storefront/llms.txt for Adobe Commerce Storefront documentation.

Claude Code will fetch the index and linked bundles when the documentation is relevant.

For tools that support custom context URLs or “docs” sources (GitHub Copilot Chat, Windsurf, and similar): provide the full URL below. Tools that implement the llms.txt spec will follow the index to the relevant bundles automatically.

https://experienceleague.adobe.com/developer/commerce/storefront/llms.txt

For tools that do not support URL-based context, paste the content of llms-small.txt (or a relevant _llms-txt/*.txt topic bundle) directly into the chat or system prompt.

  • Start from the Commerce boilerplate and this site’s Get started topics when scoping AI-assisted changes
  • Ask tools to verify APIs and version-specific behavior against the live docs or your target Commerce environment, not only against a pasted export
  • Use topic bundles under _llms-txt/ when you need a smaller slice (for example, drop-ins or tutorials only) instead of pasting the full llms-full.txt file