Custom Agent Instructions for Edge Delivery Services (EDS for AEM Sites and for Adobe Commerce) Front-End Development
This repository contains custom instructions, skills, prompts, and agents designed to enhance the capabilities of AI coding agents. Specifically tailored for Edge Delivery Services (EDS) in AEM Sites and Adobe Commerce development. These resources are intended to be used with AI coding agents like GitHub Copilot, providing them with the necessary context and guidance to assist developers more effectively.
- Evaluate EDS development with AI Tooling & Skills from Helix Project
- Context Engineering for Better AI Agent Results
- See Developing with AI Coding Agents
- The recommended
llms.txtcontents are integrated in '.github/copilot-instructions.md' - Skills are located in '.github/skills/'
- Starter skills set is based on '.claude/skills' from adobe/helix-website
Each skill is a directory in '.github/skills/skill-name/':
.github/skills/
└── {skill-name}/
├── SKILL.md # Main instructions (required)
├── scripts/ # Optional supporting scripts
└── resources/ # Optional resources (examples, templates, etc.)
- Place at the root of your project or workspace. I add mine outside src/ or /app where other .github folders are located. Alternatively, add to git ignore.
- AGENTS.md is usually placed inside the app/src folder.
- Fork/Clone/Download this repository and customize to fit your project needs.
- Discover available skills by running '.github/skills/discover-skills'
- See How Copilot uses skills
- copilot-instructions.md: Repository-wide, used by both chat/plan and agent modes, specific to GitHub Copilot in VS Code.
- AGENTS.md: Workspace-scoped, used by all agents. The nearest AGENTS.md file in the directory tree takes precedence.
- Path-specific custom instructions in '.github/instructions': If no
applyTois set, file is added to global context.
Custom instructions are automatically added to session context.*
.github/agentscontains:- DevOps Sidekick agent (for VS Code with GitHub MCP server)
- Software Architect agent (for rapid implementation planning)
- dev-docs.prompt.md: Documents complex feature implementation plans and tracks work progress in persistent markdown files. This methodology employs persisten memory files in markdown as context and memory storage scoped to specific tasks/features.
- block-readme.prompt.md: Use this prompt for creating a README.md file for a block component.
Prompts are agent instructions used on-demand using /slash commands. The name of the /command is the name of the prompt file, should be the same as the "name" front-matter.
/dev-docs implement real-time notifications
/block-readme add readme file to new-block-
Break down commerce dev docs links in
.github/instructions/commerce-storefront-docs.instructions.mdinto modularxxx.prompt.mdfiles (e.g.,checkout.prompt.md,cart.prompt.md). -
Add all relevant documentation links in these prompt files, plus links to skills and related instructions.
-
This should optimize session context usage by loading data only when needed for a specific task.
-
Example usage:
/cart follow the links and read the documentation fully then suggest implementation plan for adding a custom content block on the cart page
💻 Contributions are welcome!
- CLI commands and local dev environment variables in instruction files may need adjustment for your local setup.
- Install tools/MCP servers from .vscode on your IDE (add or remove as per your needs).
- Helix MCP Server - Tools for developers and administators of sites deployed with AEM Edge Delivery Services and Document Authoring.
- Plan before you build, steer as you go!
AI-generated code can break your application if not reviewed properly.
Always review the contents of any agent instructions files downloaded from the Internet for malicious insertions.