dx-aem

Plugin dx-aem from marketplace dx-aem-flow in easingthemes/dx-aem-flow. Commands read from the repo's manifest — 3 days ago.

Skills (12)

• aem-component

  Find all source files, AEM pages and dialog fields for an AEM component. Use for 'where is component X?', 'what files for hero?', 'find component'.

• aem-doc-gen

  Generate AEM authoring docs for a finished story — find or create a demo page with the component, screenshot dialog and site on QA, write the authoring guide. Used by /dx-agent-all Phase 7 and /dx-req-dod.

• aem-doctor

  Check AEM project infrastructure health — component definitions, OSGi configs, dispatcher rules, content structure. Use when AEM config seems broken or after infrastructure changes.

• aem-editorial-guide

  Capture an editorial guide for a component dialog in AEM — open the editor, screenshot the dialog, write an author-friendly guide. Use for 'document the dialog', 'create authoring guide'.

• aem-fe-verify

  Visually verify a component's rendering on local AEM (wcmmode=disabled) against Figma or requirements, fixing gaps in a loop. Use for 'verify frontend', 'visual verify', 'compare AEM with figma'. Not for dialog checks (aem-verify) or full story QA (aem-qa).

• aem-init

  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.

• aem-page-search

  Find AEM pages that use a given component, with clickable author URLs. Use for 'where is this component used?', 'which pages use the hero?'.

• aem-qa-handoff

  Post the QA handoff comment to ADO — QA page URLs, prerequisites, wiki link. Use after /aem-doc-gen and /dx-doc-gen, or for 'handoff to QA'.

• aem-qa

  QA a story on AEM — check component rendering and dialogs on pages, capture screenshots, create Bug tickets for issues. Use after deploying, for 'qa this', 'verify on AEM'. Not for one component's dialog (aem-verify) or visual-only checks (aem-fe-verify).

• aem-refresh

  Refresh .ai/project/ seed data from a local path or the remote ADO docs repo. Use when project knowledge is outdated, for 'update seed data'.

• aem-snapshot

  Snapshot a component's AEM state before development — dialog fields, properties, pages using it — as a baseline in specs. Use before starting a component story.

• aem-verify

  Verify a component on AEM after deployment — walk dialog fields, create a configured test page, compare with the /aem-snapshot baseline. Not for pre-PR code checks (dx-step-verify), visual frontend checks (aem-fe-verify) or full story QA (aem-qa).

Subagents (6)

• aem-bug-executor

  Executes AEM-specific bug verification steps — navigates to AEM pages, reproduces bugs visually via Playwright, captures screenshots, and returns verification evidence. Used by dx-bug-verify skill when the bug involves AEM components.

• aem-editorial-guide-capture

  Captures AEM component editorial guide via Playwright — opens editor, triggers dialog, screenshots, and writes editor-friendly docs. Use for post-development documentation.

• aem-fe-verifier

  Verifies AEM component frontend rendering — creates/reuses demo pages, screenshots components in wcmmode=disabled via Playwright, compares against Figma reference or requirements using multimodal vision. Used by aem-fe-verify skill.

• aem-file-resolver

  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.

• aem-inspector

  Inspects AEM components via MCP — captures dialog fields, finds pages, creates test pages, configures demo data. Use for pre/post development component verification.

• aem-page-finder

  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.

MCP servers (2)

• AEM

  runs: npx -y aem-mcp-server -t stdio -I ${AEM_INSTANCES}

• playwright

  runs: npx @playwright/[email protected] --headless --isolated --viewport-size=1440,900 --caps=storage --no-webmcp --output-dir=.ai/playwright/screenshots

Hooks (2)

• PostToolUse

  bash "${CLAUDE_PLUGIN_ROOT}/hooks/scripts/screenshot-log.sh"

• PostToolUse

  bash "${CLAUDE_PLUGIN_ROOT}/hooks/scripts/screenshot-log.sh"

Similar plugins