メニュー
Preview and verify imported content in local AEM Edge Delivery Services dev server. Validates rendering, compares with original page, and troubleshoots common issues.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Generate comprehensive admin documentation for AEM Edge Delivery Services project handover. Creates admin guide covering Config Service setup, permissions, access control, Admin API operations, cache management, and code sync. Use for "admin guide", "admin documentation", "admin handover".
Analyze development requirements and define acceptance criteria for AEM Edge Delivery Services tasks. Handles new blocks, variants, modifications, bug fixes, and styling changes with task-specific guidance.
Authenticate with AEM Edge Delivery Services Config Service API. Opens a browser window for Adobe ID login and captures the auth token when browser is closed. Use when generating guides/documentation that require API access.
Generate comprehensive documentation for content authors taking over an AEM Edge Delivery Services project. Analyzes the project structure and produces a complete authoring guide with blocks, templates, configurations, and publishing workflows.
The Block Collection and Block Party are repositories for existing AEM blocks, build tools, code snippets, integration patterns, plugins, and more. Use this skill anytime you are developing something and want to find a reference to use as a starting point.
Survey available blocks from local AEM Edge Delivery Services project and Block Collection to understand the block palette available for authoring. Returns block inventory with purposes to inform content modeling decisions.
| name | preview-import |
| description | Preview and verify imported content in local AEM Edge Delivery Services dev server. Validates rendering, compares with original page, and troubleshoots common issues. |
Open and verify imported content in local development server.
Use this skill when:
Invoked by: page-import skill (Step 5)
From previous skills, you need:
Determine the folder from metadata.json:
paths.dirPath from metadata.json (e.g., /us)Command:
aem up --html-folder {dirPath}
Examples based on imported content location:
| HTML File Location | Command | Preview URL |
|---|---|---|
us/en.plain.html | aem up --html-folder us | http://localhost:3000/us/en |
products/widget.plain.html | aem up --html-folder products | http://localhost:3000/products/widget |
blog/2024/post.plain.html | aem up --html-folder blog | http://localhost:3000/blog/2024/post |
Why this is required:
--html-folder, AEM CLI proxies requests to the remote serverFor most files, use the document path directly:
http://localhost:3000${documentPath}
Example:
us/en/about.plain.htmlhttp://localhost:3000/us/en/aboutIMPORTANT: For index files, use / instead of /index:
If file is: index.plain.html
Preview at: http://localhost:3000/
NOT: http://localhost:3000/index
Note: If you used --html-folder flag (e.g., aem up --html-folder drafts), prepend that folder to the URL:
File: drafts/test.plain.html
URL: http://localhost:3000/drafts/test
Use paths.documentPath from metadata.json, but for index files ensure the path is / not /index
Check the following:
<meta> tags)Side-by-side comparison:
./import-work/screenshot.png alongside browser previewBlocks don't render correctly:
../page-import/resources/html-structure.md for format guidanceImages not loading:
./images/... format./import-work/images/Raw HTML visible:
blocks/ directoryMetadata not in page source:
<meta> tags in <head>Dev server not running:
aem upPage not found (404):
--html-folder flag - restart server with aem up --html-folder {dirPath}/index not /This skill provides:
Import complete when all verification points pass.