◆ Adobe Creative Cloud

Perform maintenance on AEM services

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskRun the weekly health check on the AEM author and publish instances. Check for any replication…+
Run the weekly health check on the AEM author and publish instances. Check for any replication queues backing up and ensure all caches are clear. Send the summary report to Mark by end of day.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore I perform the monthly AEM maintenance, identify any content fragments or experience…+
Before I perform the monthly AEM maintenance, identify any content fragments or experience fragments that are rarely used or have broken references. Make it easy to see what can be safely archived or removed to improve performance.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentA critical content update published by the marketing team isn't showing on the live AEM site,…+
A critical content update isn't showing on the live site.
A critical content update published by the marketing team isn't showing on the live AEM site, but it appears fine in the author instance. I've checked the replication logs, and they show success, but clearly something is wrong. I'm afraid of a full site outage if I try to restart things without knowing the root cause. What's the likely diagnosis, and what's the best next move to get this content live safely?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternAEM performance issues often catch us by surprise, leading to last-minute fire drills and…+
AEM performance issues often catch us by surprise.
AEM performance issues often catch us by surprise, leading to last-minute fire drills and frustrated content editors. We're always reacting instead of preventing. It feels like we're missing early warning signs. What habit should I change to proactively monitor and maintain AEM services, catching potential problems before they impact the live site or content teams?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from Adobe Creative Cloud's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.