Experience Production Agentic Capabilities experience-production-agentic-capabilites

Use Case

Description

Skill(s)

Application

Sample Prompts

Update AEM pages

Perform actions such as updating, removing, replacing, or adding content elements to keep experiences accurate and current. Inputs can be natural language or visual annotations like PDFs or screenshots.

Adobe Experience Manager (AEM)

On <URL> update the headline to Hello World

on <URL> change “Take our Coffee Quiz” button to a more engaging version

Update <URL> based on the attached

on <URL> I want to a add a new teaser section to the bottom of the page about a promotion we are running in the month of august that is buy a coffee machine and get 2 bags of coffee free. Also find image of friends drinking coffee and use that in the teaser

Update AEM in bulk

Perform bulk actions across multiple pages at the same time such as removing, replacing, or adding content elements to keep experiences accurate and current.

Adobe Experience Manager (AEM)

on <aem path> update all pages that contain copy “MyBarista” to “BrewPass”

Edit Content Fragments

Use natural language to manage a single Content Fragment or hundreds at once. AI handles search, creation, updates, publishing, tagging, and other content operations while automatically enforcing the appropriate governance workflow.

Adobe Experience Manager (AEM)

find Content Fragments under <CF_path> whose calories field is set to 150 and update to 200 also update the ‘Serving Style’ field on the same fragments to ‘Iced’

Create 3 fragments ones under <CF_path> name them 'Cortado Freddo Summer’, 'Turkish Coffee Summer’, 'Café de Olla Summer’ and ‘Calories’ 150 each. Tag the 3 fragments with the ‘Frescopa : Coffee’ tag

Discovery Content Fragments

Find content fragments using natural language. Supports both semantic (intent) based or keyword based search.

Adobe Experience Manager (AEM)

find Content Fragments under <CF_path> whose calories field is set to 150

Go from Figma to Visual Content Fragment

Import designs directly from Figma into Adobe Experience Manager using natural language. The skill automatically creates the required content model, content fragment, assets, and visualization template, enabling business users to move from design to web-ready content in minutes without manual setup.

Adobe Experience Manager (AEM)

Import from <Figma_URL>

Inspect Content Fragments for dependencies, semantic readiness, and publish readiness

Optimize and manage Content Fragments for AI-powered experiences through readiness checks that include semantic analysis and impact assessment. Evaluates content quality, metadata, structure, schema compliance, and references to surface issues affecting search, publishing, translation, or headless delivery. Analyzes dependencies across Content Fragments, collections, assets, models, and pages to identify risks and recommend safe actions. Finally it provides assessments with guided, human-reviewed remediation steps.

Adobe Experience Manager (AEM)

Run a health check on the folder <CF_path>

Is content fragment <CF_path> ready to publish?

is folder <CF_path> ready for semantic search?

Is this Content Fragment <CF_path> being referenced by other fragments? What will happen if I delete it?

Show me the dependency tree for <CF_path>

Use Case

Description

Skill(s)

Application

Sample Prompts

Create form using natural language intent

Generate a new Adaptive Form from a plain-language description of the fields and purpose

Adobe Experience Manager (AEM)

“Create an employee onboarding adaptive form”

“Create a <form type> adaptive form”

Create form using attached brief

Generate a form from an uploaded requirements brief describing fields and flow

Adobe Experience Manager (AEM)

“Create a form using the attached brief”

Create form using attached image/screenshot

Generate a form by interpreting a screenshot or image of a reference form or mockup

Adobe Experience Manager (AEM)

“Create a form as per the attached image”

Create form using attached PDF

Generate a form by importing an existing PDF form

Adobe Experience Manager (AEM)

“Create a form from this attached PDF”

Update form — add/edit fields

Add, edit, or remove fields on an existing form

Adobe Experience Manager (AEM)

“Add Middle Name field below First Name field”

“Mark all fields in <panel> as required”

“Remove the Fax Number field”

“Rename the Comments field to Additional Notes”

Configure field properties

Set field-level properties such as placeholder text, format validation, dropdown options, and file-type/size restrictions

Adobe Experience Manager (AEM)

“Add a text input field for Company Name with placeholder ‘Enter your company name’”

“Configure the Phone Number field with format (XXX) XXX-XXXX and validation”

“Add a file upload field for Resume with PDF and DOC restrictions, max 5MB”

“Add a <field type> field for <field name> with placeholder ‘<placeholder text>’”

Add smart/knowledge-based fields

Add dropdown or selection fields pre-populated using the AI’s built-in knowledge base, without manually specifying every option — for example, country/state lists, industry codes, currency codes, or job titles

Adobe Experience Manager (AEM)

“Add a dropdown for departure airports with all major international airports”

“Add a complete list of US states with abbreviations”

“Add a field for industry classification with NAICS codes”

Update form layout

Adjust the layout of an existing form — field order, column span, panel structure

Adobe Experience Manager (AEM)

“Put First Name and Last Name fields in a 2 column layout, 50/50”

“Put <field 1> and <field 2> fields in a <N> column layout”

Update form using attached guidelines

Revise an existing form to align with an uploaded guidelines document

Adobe Experience Manager (AEM)

“Update this form to match the attached guidelines document”

Add business logic

Create conditional logic, show/hide rules, field dependencies, and define validation rules

Adobe Experience Manager (AEM)

“Show the Company field only when Employee Type is Contractor”

“Make the Email field required and validate it as an email address”

“Hide the Shipping Address section when Same as Billing Address is checked”

“Show the <field> field only when <other field> is <value>”

Configure form submit action

Set up how a form submits — cloud storage (Azure Blob, OneDrive, SharePoint doc library, SharePoint list), CRM/marketing platforms (Marketo), Adobe Experience Platform, generic web protocols (REST via FDM, OData, SOAP, REST endpoint/webhook), email, or a custom submit action bundle. Supported on both Cloud Service and Edge Delivery Services. The connector must already be configured in AEM before the skill can select and set it.

Adobe Experience Manager (AEM)

“Configure the form to send data to a REST endpoint”

“Submit to Azure Blob”

“Submit to SharePoint doc library”

“Submit to Adobe Experience Platform”

“Send email on submit”

“Use my custom submit action”

“Submit to REST endpoint <url>”

Embed form onto a site’s page

Place an existing or newly created form onto a designated AEM Sites page (supported on Edge Delivery Services pages only)

Adobe Experience Manager (AEM)

“Embed this form on the homepage of our site”

“Embed this form on <page path>”