adobe-reference-architecture
Define a production Adobe architecture spanning identity, service adapters, async workers, asset custody, I/O Events, App Builder, evidence, and recovery
Install / Use
npx skills add jeremylongshore/tons-of-skills-marketplace --skill adobe-reference-architectureInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
MarketingSupported Platforms
Our assessment of adobe-reference-architecture
adobe-reference-architecture scores 83/100 on our quality scale, 517th of 642 Marketing skills we index.
Its SKILL.md is 4.3 KB long, well organised into 13 sections and no code examples: a solid amount of guidance for an agent.
With 2,785 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so adobe-reference-architecture is actively maintained.
- Our last check on 2026-11-06 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-30. Automated pattern scan on 2026-09-30. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
adobe-reference-architecture compared with similar skills
All 4 of these similar skills score higher than adobe-reference-architecture; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| adobe-reference-architecture (this skill)by jeremylongshore | 83 | 2.8k | 53d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.7k | 7d ago | CLAUDE.md |
| x402by browser-use | 100 | 121.0k | 3d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
Frequently asked questions
- How do I install adobe-reference-architecture?
- Run
npx skills add jeremylongshore/tons-of-skills-marketplace --skill adobe-reference-architecture. The install tabs above show the steps for each supported agent. - Which AI agents does adobe-reference-architecture work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is adobe-reference-architecture safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is adobe-reference-architecture still maintained?
- The repository was last updated about 2 months ago, so adobe-reference-architecture is actively maintained.
Skill content
View source on GitHubname: adobe-reference-architecture description: >- 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". allowed-tools: Read,Glob,Grep,Write,Edit argument-hint: "<workloads> <services> <recovery-objectives>" version: 1.8.0 license: MIT author: Jeremy Longshore jeremy@intentsolutions.io 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"
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
- State business workflows, sources of truth, services, data classifications, consistency, budget, RTO, and RPO.
- Map clients, auth broker, service adapters, queues, workers, asset storage, event ingress, evidence store, and destinations.
- Define request, async-status, idempotency, retry, cancellation, signed-URL, output-verification, and cleanup contracts per service.
- Define I/O Events authenticity/deduplication and App Builder workspace/deploy/log boundaries.
- Threat-model credential theft, cross-environment access, forged events, URL leakage, replay, duplicate spend, and retired API use.
- 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.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Claude-Code-Game-Studios
39.7kTurn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
