Index of every page on this site: llms.txt
All skills
jeremylongshore avatar

/adobe-reference-architecture

@820dfc8
Run it yourself

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".

Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/adobe-reference-architecture

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈90 tokens for metadata: the name and description. ≈902 when used: this file. ≈853 more on demand in 1 file.

Description uses 4.5% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈361 characters, or 4.5%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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.

Tool Discipline

Use Read, Glob, and Grep to inspect current documentation, configuration, code, fixtures, and evidence. Use Write and Edit only for approved repository artifacts. Skill invocation alone does not authorize network access, credentials, Adobe content, consent, uploads, generation, spend, deployment, registration changes, replay, cancellation, or deletion.

Approval Boundaries

Architecture, security, data, budget, product, and operations owners approve production. New services, scopes, storage destinations, event providers, writes, or destructive actions require explicit approval.

Error Handling

  • Reject shared unbound credentials and generic one-client-for-everything designs.
  • Reject synchronous waiting without cancellation/reconciliation.
  • Reject architectures containing JWT, Photoshop v1, or retired Lightroom Firefly Services.

Output

Return decision record, topology, trust boundaries, identity matrix, service contracts, data flows, failure modes, rollout, and rollback. Mark assumptions, observed environment behavior, owners, evidence dates, and unresolved gaps explicitly.

Examples

  • Trace one Firefly job from approval to verified artifact deletion.
  • Trace one forged event to rejection before enqueue.

Validation

Exercise and record expected and observed results for:

  • auth boundary
  • async job
  • asset custody
  • duplicate event
  • vendor outage
  • rollback

Resources

  • Current first-party evidence map — recheck dated Adobe sources before execution.
  • Treat observed tenant or product behavior as environment-specific evidence, never a universal Adobe guarantee.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    This skill provides a reference architecture and boilerplate code for building production integrations with Adobe services like Firefly and PDF Services. It follows security best practices, such as loading credentials from environment variables instead of hardcoding them, and it utilizes official Adobe API endpoints. No security issues were detected.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at 820dfc8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 months ago
What it can do
Reads files Edits files
Modelinherit
argument-hint
<workloads> <services> <recovery-objectives>
version
1.8.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
All 5 allowed tools
ReadGlobGrepWriteEdit
Other metadata
tags
[
  "saas",
  "adobe",
  "architecture"
]
model
inherit
effort
high
compatibility
Designed for Claude Code; live Adobe actions require network access, appropriate entitlement and authentication, and explicit approval

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/adobe-reference-architecture