dx-aem
By easingthemes
AEM component verification, dialog inspection, demo capture, QA automation, and multi-platform project knowledge for Adobe Experience Manager projects
npx claudepluginhub easingthemes/dx-aem-flow --plugin dx-aemComponent Overview
Component Details
Agents (6)
Executes AEM-specific bug verification steps — navigates to AEM pages, reproduces bugs visually via Chrome DevTools, captures screenshots, and returns verification evidence. Used by dx-bug-verify skill when the bug involves AEM components.
Captures AEM component editorial guide via Chrome DevTools — opens editor, triggers dialog, screenshots, and writes editor-friendly docs. Use for post-development documentation.
Verifies AEM component frontend rendering — creates/reuses demo pages, screenshots components in wcmmode=disabled via Chrome DevTools, compares against Figma reference or requirements using multimodal vision. Used by aem-fe-verify skill.
Resolves all source files for a component across project repos. Reads file-patterns.yaml for path conventions. Returns file paths with clickable ADO URLs. Used by aem-component and dx-ticket-analyze skills.
Inspects AEM components via MCP — captures dialog fields, finds pages, creates test pages, configures demo data. Use for pre/post development component verification.
Finds all AEM pages that use a given component. Returns page paths with clickable author URLs. Used by aem-component and aem-page-search skills.
Skills (12)
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.
Generate AEM demo documentation — find or create docs page with configured component, capture dialog and website screenshots on QA, write authoring guide. Extends /aem-editorial-guide for automated pipeline use. Invoked by /dx-agent-all Phase 7 and /dx-req-dod.
Check health of AEM project infrastructure — verifies component definitions, OSGi configs, dispatcher rules, and content structure against expected state. Use to diagnose configuration drift or after making infrastructure changes.
Capture editorial guide for a component dialog in AEM — open editor, screenshot dialog, and write editor-friendly authoring guide. Use after /aem-verify or deploying changes to create editorial documentation.
Visually verify a component's frontend rendering on local AEM — screenshots the component in wcmmode=disabled, compares against Figma reference or requirements using multimodal vision, and fixes gaps in a loop. Use after build deploys to local AEM. Trigger on "verify frontend", "visual verify", "fe verify", "check component rendering", "compare AEM with figma".
Configure AEM-specific settings for the dx workflow. Detects AEM project structure, component paths, and brands. Appends aem section to .ai/config.yaml. Run after /dx-init.
Find AEM pages that use a specific component. Returns page paths with clickable author URLs. Use when you need to find where a component is used on the AEM instance.
Post QA handoff comment to ADO with QA page URLs, prerequisites, and wiki link. Reuses test page from /aem-doc-gen if available, otherwise creates its own on QA AEM. Use after /aem-doc-gen and /dx-doc-gen.
Verify a story's implementation on AEM as the QA Agent — navigate pages, check component rendering and dialogs, capture screenshots, and create Bug tickets for issues found. Requires AEM running locally. Use after deploying code.
Refresh .ai/project/ seed data files from a local path or remote ADO docs repo. Use when project knowledge files need updating.
Snapshot a component's AEM state before development — dialog fields, properties, and pages where it's used. Saves baseline to specs for later comparison. Use before starting implementation on a component.
Verify a component on AEM after deployment — walk dialog fields, create a test page with the component configured, and save verification docs. Compares against baseline if /aem-snapshot was run. Use after deploying changes.
Hooks (1)
MCP Servers (2)
README
Similar Plugins
Uses power tools
Uses Bash, Write, or Edit tools
Help us improve
Share bugs, ideas, or general feedback.