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

/adobe-architecture-variants

@820dfc8
Run it yourself

Choose among direct service integration, Adobe App Builder, and a dedicated queued worker using evidence about ownership, latency, scale, storage, events, and operations. Use when the task requires adobe architecture variant decision. Trigger with "choose Adobe architecture", "App Builder or microservice", or "Adobe design options".

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

Nothing lands on disk. Nothing to clean up.

Fork this Skill

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

SKILL.md

≈91 tokens for metadata: the name and description. ≈864 when used: this file. ≈815 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 ≈364 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 Architecture Variant Decision

Overview

Choose among direct service integration, Adobe App Builder, and a dedicated queued worker using evidence about ownership, latency, scale, storage, events, and operations. 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

Direct integration minimizes platform layers, App Builder offers Adobe-native Runtime/workspaces/events, and dedicated workers maximize queue/storage portability. None removes the need for auth, entitlement, async lifecycle, data custody, observability, and rollback. Recheck the dated evidence map before relying on mutable product behavior.

Authentication

Score how each variant binds S2S/user credentials, organization/project/workspace, product profiles, secret storage, and deployment authority.

Instructions

  1. Capture workload operations, data owners, latency/throughput, budgets, team skills, compliance, RTO/RPO, and portability needs.
  2. Model direct server-side adapters, App Builder Runtime, and dedicated queued workers against the same service contracts.
  3. Compare auth/entitlement, async jobs, storage custody, events, limits, observability, failure isolation, deployment, and lock-in.
  4. Prototype the riskiest seam with synthetic data and measure rather than inventing latency or scale claims.
  5. Threat-model each variant and name compensating controls, operational owners, exit cost, and rollback.
  6. Issue a dated decision with rejected options, evidence, conditions, review triggers, and migration seam.

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, and operations owners approve the decision. A prototype does not authorize production data, spend, deploy, or destructive actions.

Error Handling

  • Reject browser-side client-secret designs.
  • Reject App Builder claims that assume Runtime namespace auth for current deploys.
  • Reject direct synchronous handlers for unbounded async work.

Output

Return decision drivers, comparison matrix, prototype evidence, threats, selected variant, conditions, exit plan, and review date. Mark assumptions, observed environment behavior, owners, evidence dates, and unresolved gaps explicitly.

Examples

  • Compare a Firefly async worker in all three variants.
  • Show how each variant handles credential revocation and unknown jobs.

Validation

Exercise and record expected and observed results for:

  • auth
  • async workload
  • storage
  • event ingress
  • vendor outage
  • exit

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

    The skill provides architectural blueprints and code examples for integrating Adobe services. It follows security best practices for secret management and uses official Adobe resources.

  • 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> <constraints> <decision-date>
version
1.8.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
All 5 allowed tools
ReadGlobGrepWriteEdit
Other metadata
tags
[
  "saas",
  "adobe",
  "architecture-decision"
]
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-architecture-variants