What problem does it solve? Setting up and running the Adobe AEM CLI (@adobe/aem-cli) involves installation conflicts with the legacy helix-cli package, port collisions, TLS certificate errors behind corporate proxies, and silent failures when pushing content to da.live. This Skill provides verified commands, configuration references, and troubleshooting steps for these exact failure modes. ## Core Features & Use Cases - Local Dev Server: Start aem up with the right flags for headless agent workflows, local HTML serving via --html-folder, TLS via mkcert, and .env-based AEM_* configuration. - Import Server & Content Sync: Run aem import for the helix-importer-ui and use git-style aem content subcommands to clone, diff, and push content to da.live. - Troubleshooting: Resolve EADDRINUSE port conflicts, corporate proxy certificate errors, pipeline 404s, and the known binary-file and HTML-normalization limitations of aem content push by falling back to the DA Source API. - Use Case: An agent needs to preview locally generated import HTML. It runs aem up --html-folder drafts --no-open --forward-browser-logs, verifies the server responds on port 3000, and serves the drafts at /drafts/<name>. ## Quick Start Install the CLI globally with npm and start the local dev server using aem up with the no-open and forward-browser-logs flags, then verify it responds on localhost port 3000.