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.
85%
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
Use this catalog when generating AGENTS.md. Only include entries whose directories actually exist in the project.
| Module | Description |
|---|---|
core | OSGi bundle. Contains the Java code for backend services, models, and business logic. Uses OSGi for dependency injection, Sling models for exposing content to Sling scripts and JUnit for unit testing. |
dispatcher | Contains the cloud-optimized Dispatcher configuration, including caching and security settings. Uses immutable files that are validated by the Dispatcher SDK. |
ui.apps | FileVault content package. Contains the application code, including components, templates, client libraries, and content structure. Uses HTL as the scripting engine. |
ui.apps.structure | FileVault content package. Empty module that defines the structure of the repository content. |
ui.config | FileVault content package. Contains OSGi configurations for the application. |
ui.content | FileVault content package. Contains the mutable content for the application, such as the initial site structure, templates, sample assets. |
it.tests | Integration tests module. Uses the AEM Testing clients to run tests against running AEM instances. Executed by Cloud Manager during the Custom Functional Testing step of a full stack pipeline. |
ui.tests | UI tests module. Uses Cypress to run end-to-end tests against running AEM instances. Executed by Cloud Manager during the Custom UI Testing step of a full stack pipeline. |
all | FileVault content package. Includes all other FileVault packages for easy deployment. |
Only ONE of these applies per project. Match by detected frontend type.
| Variant | Module name | Description |
|---|---|---|
| General (Webpack) | ui.frontend | Frontend module built with Webpack. Compiles TypeScript/JavaScript and Sass/SCSS. During the build it's copied to the ui.apps module as client libraries. Uses Node.js, npm, and webpack. |
| React SPA | ui.frontend | React-based SPA module built with Create React App. Uses @adobe/aem-react-editable-components for SPA Editor integration. During the build it's copied to the ui.apps module as client libraries. Run npm start to develop locally with a proxy to AEM (port 3000). Uses Node.js, npm, and webpack. |
| Angular SPA | ui.frontend | Angular-based SPA module built with Angular CLI. Uses @adobe/aem-angular-editable-components for SPA Editor integration. During the build it's copied to the ui.apps module as client libraries. Run npm start to develop locally with a proxy to AEM (port 4200). Uses Node.js, npm, and webpack. |
| Decoupled | ui.frontend | Decoupled frontend module (headless). Consumes AEM content via JSON model APIs. Deployed via the AEM as a Cloud Service Frontend Pipeline separately from backend code. No client libraries are generated in ui.apps. |
| Add-on | Section text for AGENTS.md |
|---|---|
| CIF (Commerce) | Commerce Integration Framework (CIF): The commerce backend endpoint is configured in ui.config OSGi configurations. CIF Core Components are included for building commerce experiences (product pages, catalog, search, cart, checkout). |
| AEM Forms | AEM Forms: Forms Core Components are provided OOTB in AEM as a Cloud Service. The project contains Adaptive Forms components, templates, themes, and configurations for building form experiences. |
| Headless Forms | Headless Adaptive Forms: The ui.frontend.react.forms.af module provides a React-based rendering layer for forms consumed via the form model JSON. Forms can be rendered in external applications while leveraging AEM Forms capabilities for form logic and data handling. |
| Precompiled Scripts | Precompiled Scripts: HTL scripts from ui.apps are precompiled into a bundle during the build and attached as a secondary bundle artifact for improved performance. |
When an add-on is detected, add a ## Add-ons and extensions section between the intro paragraph and ## Modules, listing each detected add-on as a bullet.
If CIF is detected, append to the core module description: , including commerce-specific models and servlets.
If Headless Forms is detected, add this module to the Modules list:
ui.frontend.react.forms.af: React-based headless Adaptive Forms rendering module. Consumes form models and renders forms in a headless manner. Uses Node.js, npm, and webpack.These are already in the AGENTS.md template. Always keep them.
Add after the base resources:
If React:
If Angular:
.tessl-plugin
skills
aem-rde
aem-workflow
code-assessment
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
references
dispatcher
legacy-ui
template-modernization
validation
scripts
dispatcher-tool
validate-migration