From dx-aem
Refresh .ai/project/ seed data files from a local path or remote ADO docs repo. Use when project knowledge files need updating.
npx claudepluginhub easingthemes/dx-aem-flow --plugin dx-aemThis skill is limited to using the following tools:
You refresh `.ai/project/` data files from an external source. This updates the project knowledge that agents use for component lookups, file resolution, and market-scoped searches.
Generates developer guide for AEM Edge Delivery Services projects by analyzing codebase structure, custom implementations, and design tokens. Use for onboarding or technical handovers.
Refreshes Composure config, hooks, reference docs, or stack in initialized projects without full re-initialization. Targets only changes or specified components via [config] [docs] [hooks] [stack] [all].
Detects drift in .arkhe/roadmap/ context files via git commits and days old, regenerates project.md, architecture.md, documents.md from README, CLAUDE.md, docs. Scaffolds if missing.
Share bugs, ideas, or general feedback.
You refresh .ai/project/ data files from an external source. This updates the project knowledge that agents use for component lookups, file resolution, and market-scoped searches.
If the user passes a local path as argument:
.ai/project/If no argument provided:
.ai/config.yaml → aem.docs-repo for the ADO repo URLmcp__ado__search_code or ADO MCP file content tools to fetch each file by pathaem.docs-repo-paths in config.yaml):| Source Path (in docs repo) | Destination | Mandatory |
|---|---|---|
docs/components/component-index.md | .ai/project/component-index-project.md | yes |
docs/project.yaml | .ai/project/project.yaml | yes |
docs/file-patterns.yaml | .ai/project/file-patterns.yaml | yes |
docs/content-paths.yaml | .ai/project/content-paths.yaml | no |
docs/architecture.md | .ai/project/architecture.md | yes |
docs/features.md | .ai/project/features.md | yes |
If aem.docs-repo-paths is set in config.yaml, use those paths instead.
If neither a local path nor aem.docs-repo is configured:
aem.docs-repo in .ai/config.yaml via /aem-init."For each file in the table:
.ai/project/ destinationCreate .ai/project/ directory if it doesn't exist.
Never overwrite component-index.md (the aem-init auto-generated local index). Only write to component-index-project.md (the enriched cross-repo index).
After copying, report:
## Seed Data Refreshed
| File | Lines | Status |
|------|-------|--------|
| component-index-project.md | <N> | Updated (<M> components) |
| project.yaml | <N> | Updated |
| file-patterns.yaml | <N> | Updated |
| content-paths.yaml | <N> | Updated |
| architecture.md | <N> | Updated |
| features.md | <N> | Updated |
**Source:** <local path or ADO repo URL>
For component-index-project.md, count table rows to report component count (grep for ^| lines excluding header).
/aem-init).component-index-project.mdToolSearch("select:mcp__ado__search_code") first/aem-refresh — Detects local seed data path from plugin config. Copies updated project.yaml (45 lines), file-patterns.yaml (32 lines), content-paths.yaml (18 lines), architecture.md (120 lines), and features.md (85 lines) to .ai/project/. Reports line counts for each file.
/aem-refresh --source /path/to/docs-repo — Uses the specified local path instead of the default. Finds all 6 seed files, copies them, and reports that component-index-project.md was updated with 52 components.
/aem-refresh (source not found locally, falls back to ADO) — Local path doesn't exist. Falls back to ADO docs repo via MCP, fetches seed files from the remote repository. Downloads and saves each file to .ai/project/ with line counts reported.
"Source path not found and ADO repo not configured"
Cause: Neither a local seed data path nor an ADO docs repo is configured.
Fix: Run /aem-init to configure the seed data source in .ai/config.yaml, or provide a path explicitly with --source.
Mandatory files missing from source
Cause: The source directory or repo doesn't contain all expected seed files.
Fix: Check the source for project.yaml, file-patterns.yaml, content-paths.yaml, architecture.md, and features.md. If files are missing from the docs repo, they need to be added there first.
Component index not updated
Cause: /aem-refresh only copies component-index-project.md — it does not regenerate it from AEM.
Fix: To regenerate the component index from a live AEM instance, run /aem-init with the component scan option. /aem-refresh only syncs pre-built seed data files.