adobe

Convert per-page styled HTML prototypes (stardust under stardust/prototypes/**, or claude-design / Mobirise / Relume / Lovable / v0 / Figma-derived pages, or JSX prototypes pre-rendered to HTML, often under samples/) into Edge Delivery Services (EDS / AEM)…

Crawl an existing website (capped, multi-page) and seed stardust/current/ with PRODUCT.md, DESIGN.md, DESIGN.json, a per-page inventory, and the consolidated brand surface — the captured design system, palette, typography, motifs, and voice of the live site.…

Same-design migration — re-platform a site to AEM Edge Delivery (or any clean front end) keeping its current design near pixel-perfect. Recreates key pages (one archetype per page type) as clean re-authored HTML/CSS (never DOM copies), verifies each against…

Guided multi-page redesign of an existing website through a four-phase pipeline — extract (crawl and capture the current site), direct (set a visual direction), prototype (generate redesigned HTML), and migrate (emit a deployable static site). Tracks progress…

Find, classify, triage, re-implement and verify a source site's dynamic surface (APIs, search, forms, modals, media, tags, client-rendered and sheet-backed content) during a migration to a platform. Migration-bound — invoked by prepare-migration, replica,…

Read-only automated QA sweep of a deployed stardust site on AEM Edge Delivery Services — validates routing, content fidelity vs the source capture, template conformance, rendered integrity (geometry, JS errors, broken images), visual regression vs baselines,…

Deploy a WHOLE redesigned site to AEM Edge Delivery Services — the full-site, bulk sibling of `deploy` (which ships one page). Use to roll out, bulk-deploy, or publish an entire migrated stardust site at once ("deploy all pages", "full site deployment",…

Apply DESIGN, canon, and modules to every page in the inventory, producing a deployable static HTML site. Use to migrate or render the whole captured site into the redesigned static tree ("migrate the pages", "render the migrated site", "apply the design to…

Build a feature's ecs/actions layer — the operations the app performs.

Build an application's src/app/ composition root.

Build a feature's ecs/computed layer. Optional.

Build a feature's ECS schema (ecs/core) and its conformance wiring. The first ecs layer.

Build a feature's data/ layer — values, components, resources, entities. The first, foundational phase.

Build a complete feature step by step

Build a game — an application whose features model game state, rules, and rendering.

Build a feature's ecs/indexes layer. Optional.

Create accessibility migration analysis docs for gen2 component migration. Use when on the "analyze accessibility" step for one or more components.

Suggests the preferred branch name format for Spectrum Web Components contributions (lowercase, dash-separated, a conventional commit type, and an optional issue number). Use when creating, renaming, or checking a git branch name.

Review gen2 component files against project style guides, run linters, and surface guideline gaps. Apply whenever reviewing or auditing gen2 component code for style conformance.

Create conventional commit messages following best conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits specification.

Generates GitHub pull request and issue descriptions — title, labels, and body — following Spectrum Web Components conventions and the repository's pull request template. Prompts for a linked ticket if none is provided. Use when asked to write or draft a PR…

Drafts and formats Spectrum Web Components Jira tickets (title, labels, severity, issue type, and required sections, using Jira markup) for bugs, features, research, and RFCs. Use when asked to create, draft, format, or review a Jira ticket.

Document lessons learned after completing work, especially when the user corrected planning documents or implementation. Creates and maintains topic lessons files in .ai/memory/ that load as path-scoped instructions. Use when the user says "remember this",…

Clarify requirements before implementing. Use when serious doubts arise.

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 quality, performance, accessibility, and adherence to EDS best practices.

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

Analyze content sequences and determine authoring approach (default content vs blocks). Validates block selection and section styling for import/migration to AEM Edge Delivery Services.

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.

Searches the aem.live documentation for information on AEM Edge Delivery Services features. Use this skill when you need more information about a feature, want guidance on how to implement a feature, and using existing tools you have to search the web isn't…

Generate structured HTML from authoring analysis for AEM Edge Delivery Services. Creates section structure, applies block tables, handles metadata, and manages images folder.

Identify section boundaries and content sequences within a scraped webpage for AEM Edge Delivery Services import. Performs two-level analysis (sections, then sequences per section) and surveys available blocks.

Analyze content sequences within a section and provide neutral descriptions for AEM Edge Delivery Services. Invoked per section during page import to identify breaking points between default content and blocks.

Single entry point for all AEM as a Cloud Service Workflow skills. Covers workflow model design, custom process step and participant chooser development, launcher configuration, workflow triggering, and production support including debugging stuck/failed…

Debug AEM Workflow issues on AEM as a Cloud Service including stuck workflows, failed steps, missing Inbox tasks, launcher failures, stale instances, thread pool exhaustion, queue backlogs, purge failures, and permissions errors. Use when the user reports…

Design and create AEM Workflow models on AEM as a Cloud Service. Use when creating workflow models via the Workflow Model Editor or content package XML, defining step types (PROCESS, PARTICIPANT, DYNAMIC_PARTICIPANT, OR_SPLIT, AND_SPLIT), configuring step…

AEM as a Cloud Service Java/OSGi best practices, guardrails, and legacy-to-cloud pattern transformations. Use for Cloud Service–correct bundles, deprecated APIs, schedulers, ResourceChangeListener, replication, Replicator, JCR observation…

Create, modify, review, and harden configuration for the Adobe Dispatcher Apache HTTP Server module and Apache HTTPD in AEM as a Cloud Service environments only. Use for `.any`, vhost, rewrite, cache, and filter changes.

Investigate and triage runtime incidents involving the Adobe Dispatcher Apache HTTP Server module and related HTTPD configuration in AEM as a Cloud Service environments only, using runtime-backed MCP evidence.

Optimize performance of the Adobe Dispatcher Apache HTTP Server module and related HTTPD configuration for AEMaaCS cloud workflows only, with cloud-specific baseline and runtime verification.

Perform security audits for the Adobe Dispatcher Apache HTTP Server module and Apache HTTPD in AEMaaCS cloud workflows only, with cloud-specific hardening verification.

Donut-chart-specific design tokens (colors, sizes, typography, spacing, hover/emphasize behavior, and validation rules), sourced from the Figma "S2 – Charts" file. Use when generating, styling, or reviewing a Donut chart to get exact values instead of…

Feature guidance for Donut chart advanced labels (swatch + segment name + value/% + optional detail row, connected to the slice by a leader line). Use when generating a Donut with advanced labels enabled. Token values referenced here are defined in…

Feature guidance for the Benchmark Donut variant (2-segment donut with a reference line/target marker). Use when generating a Donut with a benchmark comparison line. Token values referenced here are defined in donut-chart-tokens.

Feature guidance for the 2-segment (binary) Donut chart variant. Use when generating a Donut with exactly 2 segments and no separate swatch legend. Token values referenced here are defined in donut-chart-tokens.

Feature guidance for Donut chart direct labels (segment name + value text placed directly around the ring, no connector line). Use when generating a Donut with direct labels enabled. Token values referenced here are defined in donut-chart-tokens.

Shared collision-avoidance algorithm for donut chart labels (Direct or Advanced) that stack vertically within the same hemisphere. Use whenever multiple small/adjacent segments produce overlapping label positions.

Feature guidance for the Donut chart's center-hole metric total/label (the summary number shown in the middle of the ring). Use when generating a Donut with Metric value/Metric label enabled. Token values referenced here are defined in donut-chart-tokens.

Feature guidance for the regular (multi-segment, non-binary) Donut chart variant. Use when generating a standard Donut with 2-6 segments and no benchmark. Token values referenced here are defined in donut-chart-tokens.

Analyze the partner's existing codebase across all detected surfaces and write service cards into service-cards/ — one per-surface card set (backend/, plus a UI set in mobile/, web/, ios/, or android/), always the shared context in shared/, and a…

Produce a fully branded, runnable partner app from partner-supplied mocks by reproducing the partner's UI on top of a reference app that already contains all the Adobe integration capabilities (claim, find-subscription, cancel, notify). Every partner's UI is…

Generate production-ready Adobe backend clients in the partner's existing backend stack: Phase 0 — a reviewable design approved before any code is written; Phase 1 — the IMS OAuth token service; Phase 2 — the typed Adobe Integration API client (Workflow, Get…

Generate a complete .env.example with all required Adobe integration variables, add .env to .gitignore, and add startup config validation to the backend.

Scan the entire codebase and produce a definitive integration checklist — what's done, what's partial, and what's missing. Share this with Adobe partner engineering when requesting stage access review.

Generate reviewable backend and UI Low-Level Designs (LLDs) for one feature, before any code is written — Phase A (backend LLD, the DG-3 gate) then Phase B (UI LLD, the DG-4 gate). See ../../manual/methodology/card-model.md#lld-section-contract and…

Generate comprehensive unit and integration tests for all Adobe integration code, using the partner's existing test framework and patterns.

Implement one Adobe integration feature end-to-end across all detected surfaces (backend route, mobile/native screen(s), web component(s)), from the feature's approved LLD, following the target repo's own conventions.

Query AEM Edge Delivery Services Real User Monitoring (RUM) data via the Operational Telemetry (OpTel) bundler API. Covers page views, web vitals, traffic breakdowns, and domain key management. Use when investigating site performance, checking page view…

Interact with Adobe On-Call (ServiceNow-based pagerduty replacement) — list active on-call incidents, acknowledge, check who is on-call, view your upcoming shifts, and manage incident state. Use when the user mentions on-call, pagerduty, OCINC, incidents,…

Use this when investigating CDN incidents, checking error rates, or drilling into AEM Edge Delivery Services logs via ClickHouse. Covers error breakdowns, time series, log inspection, and automated incident investigation. Triggers on requests like "check CDN…

Turn measured historical monthly cost series into a probabilistic forward projection by Monte Carlo — fit growth and volatility per component, detect regime breaks that invalidate naive growth fits, simulate p05-p95 percentile bands for an annual total,…

Wrap any command in an Adobe ServiceNow Change Management Request (CMR) so the exact command line, working directory, exit code and output become the ticket's paper trail. `change [root params] run <command> [args...]` files the change, drives it New → Assess…

Use this when investigating New Relic alerts, synthetic monitor failures, or when you need NRQL against AEM Edge Delivery Services telemetry. Covers open alert issues, synthetic monitor health, scripted monitor source, per-request breakdowns of what a monitor…

Use this when writing postmortems, incident reports, RCA, root cause analysis, post-incident review, or incident documentation for AEM Edge Delivery Services. Covers the aem-status repo workflow: creating postmortem files, frontmatter spec, impact…

Migrate an Adobe Commerce App Builder project from the Integration Starter Kit or Checkout Starter Kit to the new App Management approach. Run from the root of the App Builder project to be migrated. Pass --auto to skip confirmation prompts (suitable for CI…

Integrate App Builder Database Storage (@adobe/aio-lib-db) into an Adobe Commerce app and scaffold a runtime action that reads and writes documents. Use when the user wants persistent, queryable storage backing a Commerce app — either from a web action…

Add or modify Adobe Commerce Admin UI extensions on the commerce/backend-ui/2 extension point: custom grid columns, mass actions, order view buttons, a custom Admin menu entry, and custom ACL resources. Use whenever the user wants to extend the Commerce Admin…

Scaffold or update an Adobe API Mesh configuration (mesh.json) in front of a Commerce app: add GraphQL/OpenAPI sources, extend an existing Commerce GraphQL type with a new field, and wire a cross-source resolver for it. Use when the user mentions API Mesh,…

Add or modify Commerce and external event subscriptions, configure event field extraction and filter rules in an Adobe Commerce app. Use when the user wants to set up event-driven workflows triggered by Commerce operations (such as order placement or catalog…

Add or modify webhook interceptors in an Adobe Commerce app. Use when the user wants to intercept Commerce operations to validate input, append data, or modify behavior — before or after execution. Requires a base app initialized with commerce-app-init.

Scaffold a new Adobe Commerce app using the aio-commerce-sdk. Creates the base project structure and app.commerce.config file with metadata. Use when the user wants to create a new Commerce app from scratch or initialize a bare Commerce app project. After…

Implement WCAG 2.2 compliant interfaces with mobile accessibility, inclusive design patterns, and assistive technology support. Use when auditing accessibility, implementing ARIA patterns, building for screen readers, or ensuring inclusive user experiences.

Generates GitHub pull request title and body following Adobe Labs website conventions.

Scaffold and implement a new EDS block for the Adobe Labs website. Use when adding a new block — covers file structure, the decorate(block) function contract, autoblocking, CSS conventions, and when to use per-page authoring vs fragments vs an autoblock.

Review a diff for performance cost and lifecycle fragility — before opening a PR, when a change touches scripts.js, aem.js, head.html, images, fonts or dependencies, or when a block wants to hook into core page load for "speed". Analyses the change against…

Follow Adobe content writing standards when writing documentation for the Adobe Labs website.

Guidelines for drafting and formatting Jira tickets and GitHub issues

Write Jest unit tests for Edge Delivery Services (EDS) blocks using jsdom HTML fixtures and decorate assertions. Use when adding or updating block tests, co-locating *.test.js files, mocking /scripts/ imports, or documenting the project's block testing…

Generate and update S3Mock project documentation. Use when asked to document code, update CHANGELOG.md, update README.md, update AGENTS.md files, or fix formatting, wording, or style in any existing documentation file. Also invoked at the end of the implement…

Implement features, fix bugs, and modify production source code in S3Mock. Use when asked to add functionality, change behavior, or modify source files in server/, integration-tests/, or testsupport/. Not for documentation-only or test-only changes.…

Fix code style issues and ensure linting CI gates pass in S3Mock. Use when ktlint or Checkstyle violations are reported, when asked to fix formatting, or as a required final step after any code change. Runs ktlint for Kotlin source files and Checkstyle for…

Improve code readability, enforce idiomatic Kotlin conventions, and enhance documentation quality in S3Mock without changing behavior. Use when asked to clean up code, improve naming, add KDoc, or align with Kotlin/project idioms. Also invoked by the…

Review code changes in pull requests or local diffs for S3Mock. Use when asked to review a PR, inspect changes, or provide structured feedback on correctness, conventions, test quality, and documentation. Outputs findings structured as Must fix / Should fix /…

Write, update, and fix tests in S3Mock. Use when asked to add test coverage, create test cases, fix failing tests, or verify test correctness. Covers unit tests (*Test.kt in server/), controller slice tests (@WebMvcTest), and integration tests (*IT.kt in…

Validates that "Create profile base" completed successfully. Checks that expected schemas, datasets, merge policies, and segment definitions (audiences) exist in the sandbox. Owns cleanup of those four artifact types only — flows, connections, mapping sets,…

Validates that the "Load profile data" menu option completed successfully. Runs three layers: (1) all dep: flows are enabled via the list endpoint, (2) base connection exists, (3) profile and lookup records are present in the Profile store via…

Handles all GitHub workflow steps for DEP CLI changes: PR creation with a mandatory versioning and changelog gate, checkpoint evidence, CI monitoring, reviewer comment triage and response, and merge readiness check. Use whenever the user says "create PR",…

Scaffolds the three files needed for a new DEP CLI menu action: the menu.js entry, the action.js file pre-wired to the standard pattern, and the lib function stub. Use whenever the user says "scaffold a new action", "add a menu item", "create a new CLI…

Runs the full quality gate for DEP CLI changes: simplify → code review → security review → DEP-specific compliance checks → regression checkpoint. Loops until all phases are clean and all acceptance criteria still pass. Use whenever the user says "start…

Verifies the current state of the DEP CLI project against acceptance criteria. When a plan file with acceptance criteria is in context, verifies its numbered criteria. When invoked standalone (no plan), traces changed files from git, groups affected actions…