Detect AEM project structure and append an aem section to .ai/config.yaml.
npx skills add https://github.com/easingthemes/dx-aem-flow --skill aem-init
Please help me install this Agent Skill. Skill: aem-init Source: https://github.com/easingthemes/dx-aem-flow/tree/main/plugins/dx-aem/skills/aem-init Command: npx skills add https://github.com/easingthemes/dx-aem-flow --skill aem-init
Automates the setup of AEM-related configuration for the dx workflow by detecting project structure and appending an aem section to the base configuration.
Run /aem-init after /dx-init to configure AEM settings and append the aem section to your .ai/config.yaml.
High-intent search queries and answers about installing and using this skill.
To auto-configure AEM settings, run the aem-init skill after dx-init. It detects your AEM project structure and automatically appends an aem section to your base .ai/config.yaml file to standardize DX governance.
Setting up the DX workflow for multi-repo AEM projects requires appending an aem block to .ai/config.yaml. This skill detects component paths, frontend layouts, and brands to provide consistent context for downstream operations.
Yes, you can re-run AEM component discovery safely. The skill validates re-run behavior to ensure all steps execute correctly, including component index updates, shared rule extensions, and Copilot integration notes.
The skill works with existing .ai/config.yaml files by appending the aem section to the base configuration. It requires access to the local project structure and this configuration file to perform accurate detection and modification.
You need to run dx-init first because aem-init appends an aem section to the base .ai/config.yaml created during initialization. This ensures the DX workflow has the foundational configuration before AEM-specific settings are applied.
Detection of AEM project structure requires direct access to the local project directory and the .ai/config.yaml file. Without proper local project structure access, the skill cannot accurately detect component paths, frontend layouts, or brands.
easingthemesDiscover codebase conventions and generate project-specific rule templates and seed data.
easingthemesSnapshot AEM component dialog fields, properties, and page usage into aem-before.md.
easingthemesCopy plugin assets into the consumer project and archive originals.
easingthemesFind AEM pages using a component and return paths with author URLs.
