Agent skill · software engineering · jeremylongshore
adobe-reference-architecture
Define a production Adobe architecture spanning identity, service adapters, async workers, asset custody, I/O Events, App Builder, evidence, and recovery. Use when the task requires adobe integration reference architecture. Trigger with "design Adobe architecture", "Adobe reference architecture", or "standardize Adobe services".
Why this skill is useful
Adds a complete, executable project structure and architecture patterns for integrating multiple Adobe APIs that aren't available in public documentation.
What it needs
Requires typescript installed locally. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Adobe Integration Reference Architecture Overview Define a production Adobe architecture spanning identity, service adapters, async workers, asset custody, I/O Events, App Builder, evidence, and recovery. This workflow produces a reviewable artifact and evidence before any live side effect. Prerequisites Current first-party Adobe documentation for every selected service, API version, auth flow, limit, and lifecycle. Named product, identity, security, data, budget, release, and operations owners appropriate to the scope. Synthetic or approved non-production fixtures with secret and content canaries. Current Contract The architecture separates control plane from data plane: identity/entitlement/configuration/deploy/approvals are control; prompts/documents/images/events/jobs are data. Each Adobe product has its own version, storage, error, limit, and lifecycle adapter. Recheck the dated evidence map before relying on mutable product behavior. Authentication Bind credential broker output to organization, project/workspace, service, scopes, product profiles, environment, and owner. User-owned data uses explicit user auth rather than silent S2S substitution. Instructions 1. State business workflows, sources of truth, services, data classifications, consistency, budget, RTO, and RPO. 2. Map clients, auth broker, service adapters, queues, workers, asset storage, event ingress, evidence store, and destinations. 3. Define request, async-status, idempotency, retry, cancellation, signed-URL, output-verification, and cleanup contracts per service. 4. Define I/O Events authenticity/deduplication and App Builder workspace/deploy/log boundaries. 5. Threat-model credential theft, cross-environment access, forged events, URL leakage, replay, duplicate spend, and retired API use. 6. Choose canary stages, capacity envelope, observability, incident controls, reconciliation, and tested rollback. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/adobe-reference-architecture