Browse AI recipes submitted by Adobe community members: copy-and-paste prompts and workflows, with and without Adobe tools.
Recently active
[OVERVIEW] I built a repeatable process for creating AEM code base AI skills (Bootstrap, Execute, Refine, Retrofit) which a tech lead follows to not only create AI skills for their own code base, but also helps them to make their code base more AI-ready. I covered this process in my recent Skill Exchange talk, Beyond the Prompt, and can provide examples for some of the initial AEM skills that every AEM code base will need. [TRYABLE] Bootstrap: draft the initial skill Execute: test the skill Refine: perfect the skill Retrofit: align the codebase [SETUP] Just their AEM code base and AI coding companion. [IMPACT] Help AEM skills be purpose-built for every single unique AEM code base out there, since a set of generic skills provides nowhere near the same benefit. The result is better enablement of developers to work in AEM both efficiently and correctly, with fewer mistakes and omissions, resulting in less code review/refactoring burden on architects and technical leads. [LESSONS] AI
[OVERVIEW]I made a reusable moodboard template powered by AI that turns a creative brief into several visual directions and ready-to-use prompts for image generation. It helps with the problem of starting creative ideas from nothing and gives a clear structure for exploring different visual concepts before you begin production.The workflow accepts inputs like the campaign goal, audience, product, brand personality, wanted mood, required elements, and channel. The AI then creates several different creative directions, covering visual style, mood, color direction, composition, lighting, background, and an image-generation prompt. You can then refine the chosen direction and use it in whichever AI image-generation tool you prefer.[IMPACT]Goals:- Make it faster to go from a written brief to visual ideas.- Quickly produce several creative directions rather than working on just one idea.- Build a steady format for showing moodboards to stakeholders.- Make AI image prompts simpler to write an
[OVERVIEW]This guide explains how to add repository-level agent hooks that run Semgrep after GitHub Copilot Agent performs a tool action. It gives AEM development teams a repeatable way to scan source modules quickly, review findings in advisory mode, and align local feedback with pull-request enforcement after the rules are tuned.[IMPACT]This should help to enforce and catch the security vulnerabilities and any other anti patterns that we would want to avoid in the AEM implementation. Which should definitely help in the overall quality of the code being delivered.[LESSONS]The Semgrep rules included here are intended as a starter pack and should be reviewed, refined, and expanded to align with your project's requirements and security standards. This exercise also highlights the power of GitHub Copilot Hooks and how they can be used alongside GitHub Copilot Skills to automate project-specific validation, security checks, and development workflows.[TRYABLE]1. Copilot Agent creates or edi
[OVERVIEW]Offline Python tool that replays 23 known attack requests against your Dispatcher /filter rules and shows which ones get through, and which rule to fix.It reads dispatcher.any, a farm file or filters.any (including $include) and replays 20 well-known dangerous requests (CRXDE, Package Manager, OSGi console, QueryBuilder, .infinity.json, .tidy.infinity.json, numeric selectors, .query.json, sysview/docview, /libs, /apps, /etc/packages, /home, /var, unrestricted POST, and the "* *.css *" query-string bypass) plus 3 that must keep working (a page, a DAM image, /etc.clientlibs) so over-blocking is noticed.For every probe it shows ALLOWED/BLOCKED, the deciding rule with file and line, why it matters, and a fix. Evaluation follows Adobe's documented semantics: last matching rule wins, /glob matches the whole request line, /query rules only match requests that have a query string. Most Dispatcher leaks are rule-ORDER problems (a broad allow placed after a deny backstop) or selector g
[OVERVIEW] I used Copilot enabled with Work IQ to output list of my work priorities in excel. This was hugely helpful in getting my current, ongoing tasks, identifying time-saving opportunities. I then discussed this with my manager who assigned priority labels and increased my efficiency & time management. [TRYABLE] Role You are my Chief of Staff. You are rigorous, sceptical of noise, and allergic to invented detail. Your job is to give me an honest picture of what I am actually accountable for right now — not a flattering one, and not a list of everything that has touched my inbox. Step 1 - Retrieve Search my emails, chat messages, calendar meetings and documents from the last [30] days. Search all four sources before drawing any conclusions. Prefer recent and high-signal items: threads where I am a named owner, meetings where I hold an action, and documents I have authored or been assigned in. Step 2 - Consolidate Where the same piece of work appears across multiple sources,
[OVERVIEW] Build a customizable, shareable multi-project or multi-account status dashboard Artifact — letting the user define their own accounts/projects, role-based section visibility, MCP connector data sources, and custom keywords/non-MCP inputs. [TRYABLE] 1. Describe the scope up front Tell Claude: "I want a single-page HTML dashboard tracking [account name] across these projects: [list them]. It needs to work for these roles: [list roles], each seeing different sections." 2. Name your data sources Say what's connected (Slack, Jira, Google Calendar, Zoom, etc.) and give Claude the specifics it needs to search correctly — channel names, ticket prefixes, project codenames. Without this, Claude can't tag anything to the right project. 3. Specify what "sections" you want List the actual tiles: task list, today's meetings, health scorecard, stakeholder pulse, hidden patterns, whatever matters to you. Otherwise Claude guesses generically. 4. Say explicitly you want it built as a shar
[OVERVIEW] Agent created in Copilot Studio that connects to Adobe Analytics and Adobe Target via MCP. Give it a URL, a date range and the page's goal, it pulls performance data, benchmarks every metric against the site average and prior period, and returns an executive summary, ranked insights with confidence levels, an optimisation backlog, and an AI Content Retrieval Score (a 0–100 heuristic for how cleanly an AI assistant could parse and cite the page). It then designs the right Target activity for the problem it found - hypothesis, success and guardrail metrics, audience, runtime and creates it in draft state only for human review. It never activates anything. [TRYABLE] Role: You are my digital experience strategist, with read access to Adobe Analytics and read/write access to Adobe Target. Every claim traces to a metric you actually pulled. Distinguish what the data shows from what you infer. Input: Page: [URL] · Window: last [30] days vs. preceding period · Goal: [conversion /
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.