Install the integrations

If your project is based on the Adobe Commerce boilerplate, set up all three integrations below. Together, they provide a complete workflow for storefront development, source-accurate drop-in information, and access to Adobe Commerce documentation.

Overview of the integrations

AI integrations	What it gives you
Boilerplate skills	Storefront planning, coding, customization, and testing conventions
Drop-in helper	Accurate drop-in slots, events, API functions, and design tokens validated against source
Wayfinder	Routing to the correct Adobe Commerce documentation source

Prerequisites

Before installing the integrations, make sure you have the following:

• Node.js 22 or later — Required for the Boilerplate skills setup. (If you’re installing only the drop-in helper, Node.js 18 or later is sufficient.)
• An Adobe Commerce boilerplate project — If you don’t already have one, see Getting started.
• An AI editor or coding agent that supports tool servers and agent skills — See Supported agents and Drop-in helper prerequisites for supported tools.

Installation steps

Follow these steps in order.

1. Install the AEM Boilerplate Commerce skill set. From the project root, run the following command:

   npm install -g @adobe/aio-cli
   aio plugins:install https://github.com/adobe-commerce/aio-cli-plugin-commerce
   aio commerce extensibility tools-setup

   The command prompts you to choose a starter kit, a coding agent, and, if needed, a package manager. For details, see Install the skills.

2. Add the drop-in helper. Add the server to your editor’s tool server configuration. For the configuration snippet for your editor, see Drop-in helper installation, then return here to continue installing the remaining integrations.

3. Add or verify Wayfinder. Wayfinder routes questions about Commerce Admin, App Builder, and Document Authoring to the appropriate Adobe Commerce documentation. For details, see Wayfinder. If you cloned the Adobe Commerce boilerplate, check AGENTS.md first—recent versions already include the required entry. Otherwise, add it to AGENTS.md or CLAUDE.md in your project root (create the file if it doesn’t exist):

   Fetch and follow the instructions at: https://cdn.jsdelivr.net/gh/adobe-commerce/wayfinder@main/skills/AGENTS.md

4. Add coordination instructions. Without these instructions, your agent might skip the Boilerplate skills workflow and query a tool server directly for drop-in information. Add the following rule near the top of AGENTS.md or CLAUDE.md in your project root so your coding agent is more likely to process it:

   ## Skill, server, and Wayfinder priority
   
   Check these rules in order and stop at the first match:
   
   1. **Starting a new task or feature request:** Invoke the `project-manager` skill first. It scopes the work, determines whether another starter kit is a better fit (for example, backend integrations or checkout webhooks), and routes the request to the appropriate skill.
   1. **Writing or modifying drop-in code:** Invoke the `dropin-developer` skill, even if a tool server has already answered the underlying question.
   1. **Questions about this storefront, its blocks, or its drop-ins:** Use the `researcher` skill and its tool servers (`commerce-extensibility:search-commerce-docs` and the drop-in helper).
   1. **Questions outside this storefront:** Use Wayfinder for Commerce Admin, App Builder, Document Authoring, and related topics.

5. Restart your agent so it loads the new configuration from all three integrations.

Use fallback documentation files

If your AI editor or coding agent doesn’t support tool servers or agent skills, add the following URL to your project instructions, or paste it into a chat instead:

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

For editor-specific setup instructions and a verification prompt, see Fallback documentation files.

Note

The llms.txt file offers guidance similar to the integrations above, but it isn’t validated against your project’s source, so it can become outdated. If you completed the installation steps, your agent already has more reliable, source-backed information — use llms.txt only as a fallback.