aem-fe-verify

Yes, you can automate QA for AEM components by triggering this Skill to capture screenshots in wcmmode=disabled and compare them against design requirements. It runs an automated iteration loop to identify visual gaps, apply fixes, rebuild, and re-verify rendering up to three times.

Yes, you need both AEM MCP and Chrome DevTools MCP to check component rendering. These dependencies are required to capture screenshots from your local AEM instance, compare the visual output against references, and report visual differences automatically.

The best way to compare AEM components with Figma requirements is using multimodal vision to evaluate screenshots taken in wcmmode=disabled. This approach visually verifies the frontend rendering directly against the Figma reference during your local development cycle.

The visual verification loop applies up to three iterations to fix frontend gaps. During each iteration, it identifies visual differences, applies the necessary fixes, rebuilds the local AEM instance, and re-verifies the component rendering against the reference.

Yes, you can use this visual verification for build validation and regression checks across iterations. It is specifically designed for component-level QA during local development, ensuring that frontend rendering remains consistent after deploying builds to your local AEM instance.