Agent skill · software engineering · jeremylongshore
adobe-architecture-variants
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".
Why this skill is useful
Provides specific architectural blueprints and implementation details for Adobe integrations that the AI wouldn't reliably generate on its own.
What it needs
Requires @adobe/firefly-apis, @adobe/pdfservices-node-sdk installed locally. Requires adobe account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/adobe-architecture-variants