aem-component

Locate source files, AEM pages, and dialog fields for a component across repositories.

6|3|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/easingthemes/dx-aem-flow --skill aem-component
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aem-component
Source: https://github.com/easingthemes/dx-aem-flow/tree/main/plugins/dx-aem/skills/aem-component
Command: npx skills add https://github.com/easingthemes/dx-aem-flow --skill aem-component

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Find all source files, AEM pages, and dialog fields for an AEM component. Use when a developer asks "where is component X?", "what files for hero?", or any component lookup question.

Core Features & Use Cases

  • Locate source files, AEM pages, and dialog fields for a given component across repos.
  • Support name variations and prefixes to ensure robust lookups.
  • Provide cross-reference links to ADO/SCM paths and related frontend/backend artifacts.

Quick Start

Provide the component name (e.g., hero) to retrieve all related source files, AEM pages, and dialog fields.

Frequently Asked Questions about aem-component

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find all source files for an AEM component across multiple repositories?

Locating AEM component source files across repositories is done by matching the component name against project configurations. The lookup identifies and assembles all related frontend, backend, and dialog field files, returning a structured set of file paths and cross-reference links.

What is the best way to look up AEM dialog fields and pages for a specific component?

Looking up AEM dialog fields and pages requires matching the component name while accounting for naming variations and prefixes. The process retrieves all dialog field details and AEM page URLs associated with the target component, handling any missing data gracefully.

How do I find AEM components when I only know the partial name or prefix?

Finding AEM components with partial names relies on considering naming variations, prefixes, and component paths from project configuration. This robust cross-repo lookup mechanism ensures you retrieve the correct source files and AEM pages despite naming inconsistencies.

Can I retrieve cross-reference links to SCM paths for AEM frontend and backend artifacts?

Retrieving cross-reference links to SCM paths for AEM frontend and backend artifacts is fully supported. The lookup assembles all source files and provides direct cross-reference links to ADO or SCM paths alongside the related component artifacts.

What happens if an AEM component lookup returns missing source files or pages?

When an AEM component lookup returns missing source files or pages, the missing data is handled gracefully. The process still returns a structured set of available file paths, URLs, and dialog field details without failing the entire lookup operation.

Does this AEM component lookup work for any component name I provide?

This AEM component lookup works for any component name provided, such as a hero or carousel component. It uses the provided name to search across configured repositories, matching variations to ensure all source files and AEM pages are located.