skills.rest
easingthemes
easingthemesCOMMUNITY
Explore all skills by this author →
Website𝕏@draganfillGitHub

aem-snapshot

Snapshot AEM component dialog fields, properties, and page usage into aem-before.md.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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.

Core Features & Use Cases

  • Snapshot the current AEM component dialog, properties, and usage across pages for baseline comparisons.
  • Save aem-before.md baseline to the specs directory for later verification and diffing.
  • Integrate with .ai/config.yaml to locate component path and author URL, and handle cross-page searches.

Quick Start

Run the aem-snapshot with the component name to capture a baseline of the dialog, properties, and usage pages and save it under the most recent .ai/specs directory as aem-before.md.

Frequently Asked Questions about aem-snapshot

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

FAQPage Schema
How do I capture a baseline of AEM component dialog fields and properties before refactoring?▼

To capture an AEM component baseline, you can snapshot the current dialog fields, properties, and page usage. This saves an aem-before.md file in your specs directory to establish a reference point before implementing changes.

What is the best way to track AEM component usage across pages before making updates?▼

Tracking AEM component usage across pages involves resolving page references through multiple queries based on the component path. This captures where the component is currently applied, saving the results into a baseline markdown file for later comparison.

Do I need a specific configuration file to snapshot AEM component state?▼

Yes, snapshotting AEM component state requires a .ai/config.yaml file. This configuration must define the component path and the aem.author-url to locate definitions and resolve pages across the AEM instance correctly.

How does an AEM component baseline help with future development verification?▼

An AEM component baseline helps verification by providing a snapshot of the initial dialog and properties saved as aem-before.md. You can diff this baseline against the post-development state to verify changes and prevent regressions.

Can I use this snapshot tool for AEM components deployed across multiple projects?▼

Yes, this approach applies when preparing to implement or refactor a component across AEM projects. It captures current definitions and usage across pages, saving the baseline to the most relevant .ai/specs directory for cross-project comparison.

Related Skills

Explore More Software Engineering Skills→
easingthemeseasingthemes
6

aem-page-search

Find AEM pages using a component and return paths with author URLs.

Community
Intermediate
easingthemeseasingthemes
6

aem-verify

Verify deployed AEM components by walking dialog fields and saving verification docs.

Community
Advanced
easingthemeseasingthemes
6

aem-doctor

Validate AEM components, OSGi configurations, dispatcher rules, and content structure.

Community
Advanced
easingthemeseasingthemes
6

aem-qa

Validate AEM stories with end-to-end QA checks across backend content and frontend rendering.

Community
Advanced