Agent skill · writing content · jeremylongshore
adobe-known-pitfalls
Detect current high-risk Adobe integration traps before they become production incidents. Use when the task requires adobe integration pitfall review. Trigger with "Adobe pitfalls", "review Adobe integration", or "find obsolete Adobe code".
Why this skill is useful
Provides specific Adobe API anti-patterns and solutions that the AI wouldn't reliably generate on its own.
What it needs
About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Adobe Integration Pitfall Review Overview Detect current high-risk Adobe integration traps before they become production incidents. 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 High-risk traps include Service Account JWT, confusing S2S with user auth, missing entitlements/profiles, secrets in clients, retired Photoshop v1 and Lightroom Firefly Services, reconstructed async URLs, leaked signed URLs, fixed limits, unverified events, and wrong App Builder workspace. Recheck the dated evidence map before relying on mutable product behavior. Authentication Review effective authority and secret flow before code style. A valid token, installed SDK, or successful deploy does not prove product entitlement or correct data ownership. Instructions 1. Read manifests, locks, config, adapters, routes, workflows, logs, dashboards, tests, and runbooks. 2. Glob and Grep for JWT, /sensei/cutout, Lightroom Firefly Services, client-side secrets, fixed quotas, and hardcoded job routes. 3. Trace auth ownership, product profiles, versions, signed URLs, async states, retries, events, workspaces, and cleanup. 4. Classify each finding as obsolete, unsafe, brittle, undocumented, environment-specific, or stale evidence. 5. Propose the smallest compatible correction with tests, canary, rollback, and named owner. 6. Edit only approved repository artifacts, rerun gates, and record unresolved external dependencies. 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-known-pitfalls