# Adobe Aem Engineering Profile

> Apply focused Adobe Experience Manager engineering judgment after repository gate discovery. Use for AEM as a Cloud Service or AEM 6.5 code, Sling and OSGi, content packages, Dispatcher, caching, tests, compatibility, and builds; preserve separate Cloud Manager authority.

- Skill: `jovanipink/adobe-aem-engineering-profile` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add jovanipink/adobe-aem-engineering-profile`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jovanipink/adobe-aem-engineering-profile/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- License: MIT
- Author: JovaniPink (https://skillmd.com/u/jovanipink)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/jovanipink/adobe-aem-engineering-profile

---


# Adobe Experience Manager Engineering Profile

Use this profile only after repository discovery identifies the stack. Read [focused checks](references/checks.md) when AEM-specific gates or hazards determine the result.

## Workflow

1. Determine the exact AEM product generation and discover Maven modules, content packages, FileVault filters, OSGi configurations, Sling models or servlets, HTL, Dispatcher or web-tier configuration, frontend builds, and repository scripts.
2. Follow repository-defined commands, SDK versions, dependency management, and Cloud Manager contracts before suggesting defaults.
3. Review material hazards, especially service-user permissions, repository paths, request and resource resolution, OSGi lifecycle and configuration, HTL display context, untrusted input, serialization, background jobs, and author-publish assumptions.
4. Review content-package ownership and filters, mutable content versus code or configuration, run-mode behavior, Dispatcher filters, caching and invalidation, CDN interactions, redirects, and security headers.
5. Select proportionate repository gates for Java, frontend, unit and integration tests, bundle metadata, FileVault packages, content validation, Dispatcher configuration, and builds.
6. Review compatibility across AEM product generation, SDK and API baselines, Java version, Core Components, content-package dependencies, Dispatcher tools, browser targets, and Cloud Manager pipeline rules.
7. Report every missing tool, skipped command, unavailable SDK, or unobserved pipeline as incomplete rather than passing.

## Boundaries

- Do not copy proprietary project content, read Cloud Manager credentials, start a shared author or publish service, upload a package, activate content, run a pipeline, deploy, or mutate an environment without separate authority.
- A local Maven build or Dispatcher validation does not prove Cloud Manager acceptance, deployment, caching behavior, or production readiness.
- Keep source review, local validation, SDK behavior, pipeline validation, deployment, activation, and live delivery as separate evidence states.

## Output

Return Product generation, Discovery, Hazards, Commands selected, Results, Compatibility, Cloud evidence boundary, Missing evidence, and Next safe gate.