All AEM as a Cloud Service skills: component development, Workflow model design, development, triggering, launchers, debugging, and triaging, Dispatcher config authoring, advisory, incident response, performance tuning, and security hardening, Rapid Development Environment (RDE) deployment, log inspection, snapshots, and troubleshooting via `aio aem rde`, Jackrabbit Oak query/index tuning (property, Lucene index definitions), and extracting/inventorying JCR queries (XPath, SQL2, QueryBuilder) across a codebase.
86%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Beta: This branch is in beta and under active development. Results should be reviewed carefully before use in production. Report issues at https://github.com/adobe/skills/issues
A legacy AEM Maven project to the package layout of AEM as a Cloud Service: ui.apps for code, ui.apps.structure, ui.config for OSGi configuration, ui.content for content, and the all container that embeds them and the bundles. No Java BPA pattern in this session.
Paths that start with scripts/ are relative to the migration skill directory, the folder of SKILL.md.
If the user asks to restructure the project for AEM as a Cloud Service, to split a content package into code and content, to create ui.config or all, or mentions the Repository Modernizer, follow the five steps. Adobe's Repository Modernizer (@adobe/aem-cs-source-migration-repository-modernizer 1.2.3, installed on first run) makes the change. The skill prepares its configuration, runs it, checks its output and guides the review; it adds no transformation of its own. Skip Branch B.
Run this branch before the per-pattern branches: A expects ui.config, and the others expect the code in ui.apps. It needs Node.js and git; the build in step 5 needs Maven and JDK 11 or newer.
node scripts/repo-modernizer-run.js plan <project>. Read-only: it writes <project>/target/repository-modernizer/plan.json, a folder that ignores itself. The file holds the tool's configuration (repositoryModernizer) and what the script found for you to decide (review). If it prints Layout: cloud, the project already has the layout: STOP, unless the user says otherwise.appId, and every run-mode folder Cloud Service ignores. Then end your turn and wait for the answer. Do not run step 3 in the turn in which you show the plan, also when the plan looks right to you and when nobody is there to answer: a run-mode mapping and the list of deployed packages are the user's to decide. With the answers, edit plan.json. The tool restructures exactly the content packages and bundles the plan names, and nothing else.node scripts/repo-modernizer-run.js run <plan.json>. The tool writes a restructured copy below the plan's folder; the project is not changed. Exit 0 = the tool finished and the findings are printed; 1 = the tool failed, and its output is not to be used; 2 = the plan is not ready, nothing ran. Never present a failed run as done.plan.json and by running again. A finding about the output is fixed in the output, under target/repository-modernizer/target/project/src/. Do not hide a finding: what the user decides to leave goes into the final report.git checkout -b repo-modernize/<YYYY-MM-DD>-<short-sha>.node scripts/repo-modernizer-run.js adopt <plan.json> copies the output over the project. It needs a clean working tree, and it refuses (exit 2) after a failed run and when plan.json changed since the run: run again first. It prints how to review the change and the undo line. Modules the tool did not handle stay as they are, and so do files git ignores.mvn clean install. What a failure means: a problem of the restructuring is fixed here; a problem in legacy code goes to the branch or skill that owns it, as its own session..tessl-plugin
skills
aem-rde
aem-workflow
code-assessment
asset-manager
evals
event-migration
references
replication
request-controlled-security-bypass
resource-change-listener
scripts
tuning-oak-query-indexes
content-distribution
create-component
assets
references
dispatcher
incident-response
references
dispatcher-foundation
performance-tuning
references
dispatcher-foundation
security-hardening
references
dispatcher-foundation
technical-advisory
references
dispatcher-foundation
workflow-orchestrator
references
dispatcher-foundation
ensure-agents-md
references
migration
evals
files
legacy-project
ui.apps
src
main
content
jcr_root
apps
example
components
page
references
asset-workflow
dispatcher
integrations
legacy-ui
template-modernization
validation
scripts
dispatcher-tool
repo-modernizer-tool
validate-migration