Agent skill · software engineering · jeremylongshore
adobe-sdk-patterns
Create narrow, version-pinned Adobe SDK and REST adapters with typed contracts, redaction, bounded polling, and compatibility evidence. Use when writing or upgrading integration code. Trigger with "Adobe SDK patterns", "wrap Adobe API", or "review Adobe client".
Why this skill is useful
Adds multiple executable TypeScript patterns for Adobe SDK integration that are not available in public documentation.
What it needs
Requires @adobe/firefly-apis, @adobe/lightroom-apis, @adobe/pdfservices-node-sdk, @adobe/photoshop-apis 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 Versioned Adapter Patterns Overview Create narrow, version-pinned Adobe SDK and REST adapters with typed contracts, redaction, bounded polling, and compatibility evidence. 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 SDK package versions and REST product versions change independently. Keep auth, transport, schema validation, returned status URLs, request identifiers, storage custody, and retry classification behind service-specific interfaces. The retired Lightroom Firefly Services SDK is excluded. Recheck the dated evidence map before relying on mutable product behavior. Authentication Inject a credential provider; never let callers pass raw secrets. Bind every client to environment, organization/project, service, scopes, product profiles, and redaction policy. Instructions 1. Inventory languages, package locks, direct REST calls, generated snippets, and target operations. 2. Pin supported SDK versions and trace every operation to its current REST documentation. 3. Define typed service adapters that preserve unknown fields and structured vendor error evidence. 4. Centralize token reuse, header construction, request IDs, timeouts, retry budgets, and signed-URL redaction. 5. Implement async polling by following returned status URLs with terminal-state and cancellation guards. 6. Run offline contracts plus one approved sandbox compatibility canary and publish the matrix. 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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/adobe-sdk-patterns