@adobe

testing-blocks provides a structured workflow for validating aem edge delivery projects after code changes, covering linting, mandatory browser validation across viewports, optional unit testing, and regression verification with clear success criteria at each stage.

converts markdown files to professional typeset pdfs using pandoc and typst, with automatic cleanup and no user prompts during execution. frontmatter drives metadata (title, date, authors). includes source sans 3 and source code pro fonts, blue accent styling, and auto-generated table of contents.

page-decomposition analyzes individual page sections to identify content sequences and breaking points, providing neutral visual descriptions without prescribing block implementations. designed for aem edge delivery services import workflows.

auth handles browser-based adobe id login for aem edge delivery services config api, capturing and persisting auth tokens to .claude-plugin/project-config.json for use by downstream admin/authoring skills.

generate-import-html transforms authoring analysis into plain html for aem edge delivery services, handling section structure, block tables, metadata extraction, and image folder management with validation checkpoints.

preview-import validates locally rendered imported content against original page structure, checking block decoration, image loading, metadata presence, and styling consistency in an aem edge delivery services dev environment.

content-driven-development establishes a workflow discipline for aem edge delivery services, enforcing content-first validation for all code changes affecting author workflows. prescriptive in scope but light on procedural detail.

handover orchestrates generation of three audience-specific guides (authoring, developer, admin) for edge delivery services projects, validating project structure and managing authentication before invoking parallel sub-skills to produce pdf output.

find-test-content locates existing aem edge delivery pages containing a specified block, useful for validating changes against live test content. includes safety warnings about untrusted fetched html.

page-import ingests external webpages and converts them to structured html for aem edge delivery services. orchestrates scraping, analysis, and mapping workflows across specialized sub-skills with explicit security guardrails for untrusted content.

docs-search queries aem.live documentation to retrieve information about edge delivery services features, best practices, and implementation guidance. intended as a fallback when direct urls or code examples are unavailable.

development generates technical handover documentation for aem edge delivery services projects by analyzing codebase structure and producing onboarding guides. incomplete procedure specification and vague failure handling limit utility.

authoring-analysis determines whether content sequences map to default page elements or require structured blocks, with conditional validation of section styling. detailed workflow but execution clarity varies.

block-inventory surveys available blocks in aem edge delivery services projects to understand authoring options. catalogs the block palette without executing embedded directives from fetched content.

identify-page-structure analyzes scraped webpages using a two-level hierarchy to map section boundaries and content sequences for aem edge delivery services import workflows.

analyze-and-plan guides AEM EDS task decomposition and acceptance criteria definition. covers design analysis and requirement extraction but lacks concrete procedural depth and specific trigger conditions.

create-component generates adobe aem components with configuration validation. intent is clear but procedure lacks detail, edge cases are minimally addressed, and trigger phrases are absent.

admin generates handover documentation for aem edge delivery services projects. covers config service setup, permissions, api operations, and troubleshooting via a structured guide saved to project-guides/admin-guide.pdf.

ensure-agents-md creates bootstrap configuration files (AGENTS.md and CLAUDE.md) at repository root for AEM Cloud Service projects, preventing duplicate execution when files already exist.

block-collection-and-party describes discovery and reference patterns from aem edge delivery repositories, offering external content search without concrete procedural guidance for integration or implementation.

Scrape webpage content, extract metadata, download images, and prepare for import/migration to AEM Edge Delivery Services. Returns analysis JSON with paths,…

Generate comprehensive documentation for content authors taking over an AEM Edge Delivery Services project. Analyzes the project structure and produces a…

|

|

Create or edit the Universal Editor component configuration (component-definition.json, component-models.json, component-filters.json) for AEM Edge Delivery…

Create effective content models for your blocks that are easy for authors to work with. Use this skill anytime you are building new blocks, making changes to…

Guide for implementing code changes in AEM Edge Delivery Services. Handles block development (new or modified), core functionality changes (scripts.js, styles,…

Review code for AEM Edge Delivery Services projects. Use at the end of development (before PR) for self-review, or to review pull requests. Validates code…