Install the AI tools
Connect your AI editor or coding agent to your storefront’s project guidance, drop-in information, and Adobe Commerce documentation. Then verify those connections before asking the agent to change code.
Open your storefront project in your AI editor or coding agent. If your team already configured these integrations, verify the existing connections before changing the setup.
Skills give your agent project instructions for repeatable tasks. Tool servers complement those instructions with functions the agent can call, such as looking up a drop-in API. The servers connect these functions to your editor through the Model Context Protocol (MCP). Since instructions and tool access are separate, you’ll verify both during setup.
Overview of the integrations
Section titled “Overview of the integrations”| AI integrations | What it gives you |
|---|---|
| Boilerplate skills | Storefront planning, coding, customization, and testing conventions |
| Dropins AI tools | Lookups for drop-in slots, events, API functions, and design tokens |
| Wayfinder | Routing to the correct Adobe Commerce documentation source |
| LLM files | AI tools use these static, regenerated llms.txt files as context for the storefront documentation. |
Prerequisites
Section titled “Prerequisites”Before installing the integrations, make sure you have the following:
- Node.js 22 or later for the skills installer. Keep the version your storefront requires. The current template uses Node.js 24 LTS for local development. If you install only the drop-in tools, their minimum is Node.js 18.
- A local storefront project based on the Adobe Commerce boilerplate. Open its directory in your editor. For help cloning the repository, see Run your storefront locally.
- An AI editor or coding agent that supports tool servers and agent skills. See Supported agents and the AI tools prerequisites for supported tools.
Installation steps
Section titled “Installation steps”Follow these steps in order.
-
Install the Adobe I/O command-line interface in your terminal.
Terminal window npm install -g @adobe/aio-cliThis command installs the
aioCLI, which is separate from theaemCLI used to run the local storefront. If your team already installed it, use that installation instead. -
Install the Commerce plugin.
Terminal window aio plugins:install https://github.com/adobe-commerce/aio-cli-plugin-commerce -
Run the skills setup from your storefront project root.
Terminal window aio commerce extensibility tools-setupChoose AEM Boilerplate Commerce when prompted for a starter kit, then select your coding agent. The command also selects a package manager, using the project’s lockfile when it recognizes one. For details, see Install the skills.
-
Check the generated tool-server configuration.
The current setup for AEM Boilerplate Commerce registers both
commerce-extensibilityanddropinsfor supported agents. Confirm that each server appears once. Do not add a duplicate drop-in server.If you selected Other, the installer prints configuration for you to add manually. If an older setup did not register
dropins, add only the missing entry using AI tools installation. -
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. Check
AGENTS.mdfirst because recent versions already include the required entry. If it is absent, add the following instruction toAGENTS.mdorCLAUDE.mdin your project root:Fetch and follow the instructions at: https://cdn.jsdelivr.net/gh/adobe-commerce/wayfinder@main/skills/AGENTS.md -
Add coordination instructions.
Add the following rule near the top of
AGENTS.mdorCLAUDE.mdin your project root, unless equivalent guidance is already present. This tells your agent when to use a skill, a tool server, or Wayfinder.## Skill, server, and Wayfinder priorityCheck 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 AI tools for drop-ins).1. **Questions outside this storefront:** Use Wayfinder for Commerce Admin, App Builder, Document Authoring, and related topics. -
Restart your agent so it loads the new instructions and tool configuration.
Enable remote documentation search (optional)
Section titled “Enable remote documentation search (optional)”Installing a server does not sign you in to Adobe’s remote documentation search. The search-commerce-docs tool on commerce-extensibility and the search_commerce_docs tool on dropins require Adobe I/O authentication.
To enable those searches, run the following command in your own terminal:
# Sign in for the tools that search documentation on Adobe's servers.aio auth loginComplete the browser sign-in yourself rather than asking an agent to retrieve or copy your sign-in token. If that token expires, sign in again. An access-denied response, however, can require help from your organization’s administrator rather than another installation.
The dropins server also provides search_docs, which searches local reference material without Adobe I/O sign-in. Use it for the verification and styling exercises below if you do not enable remote search. See Enable documentation search for the distinction.
Verify your development tools
Section titled “Verify your development tools”Use a real request to check your editor’s configuration, rather than relying on the agent’s claim that it has access.
-
Confirm that your editor or agent detects the installed skills in your storefront project.
Use the editor’s skills view or its documented configuration checks. See Supported agents for the expected skill locations.
-
Confirm that the configured tool servers are enabled.
Look for both
commerce-extensibilityanddropinsin your editor’s tool-server status and logs to confirm a connection, not just a saved configuration entry. If a server fails to start, resolve its reported error before continuing. -
Send this read-only request in your storefront project.
Read the project instructions and identify the guidance for a storefrontstyling task. Find --color-brand-500 in this project's styles and explainwhich content-link styles use it. Include the actual local file and linereferences. Use the dropins server's search_docs tool to find relevantstyling guidance and cite its result. Do not edit files.If a required skill or tool is unavailable, report that instead of guessing. -
Inspect the result and the tool activity.
Confirm that the file references match your local
styles/styles.cssand its active link rule. Check the tool activity for a successfulsearch_docscall and a relevant result. An answer from memory or web search does not verify this connection. -
Test a remote documentation lookup if you enabled authentication.
Ask the agent to use
commerce-extensibility’ssearch-commerce-docstool for storefront styling guidance. Check the actual tool result. A sign-in, access, or connection error is a failed check, not a successful citation. Report that limitation rather than claiming all tools work.
If the request cannot read the project, confirm the workspace directory. If the skills do not appear, check their location and restart the agent. For drop-in server connection errors, see the AI tools FAQ.
A successful lookup proves that the connection works, but not that a proposed code change is correct. To judge the change, check the reference information against your project’s installed package versions.
For a hands-on example of planning and reviewing an agent’s edit, try Make a change with AI.
Use LLM documentation files
Section titled “Use LLM documentation files”If your AI editor or coding agent doesn’t support tool servers or agent skills, add the following LLM documentation URL to your project instructions, or paste it into a chat instead:
https://experienceleague.adobe.com/en/tools/commerce-storefront/llms.txtFor editor-specific setup instructions and a verification prompt, see LLM files.