Agent skill · software engineering · jeremylongshore
adobe-local-dev-loop
Build a repeatable local loop for Adobe adapters using synthetic contracts before any remote Runtime or product call. Use when implementing or debugging locally. Trigger with "develop Adobe integration locally", "mock Adobe API", or "aio app dev".
Why this skill is useful
Adds executable scripts for setting up Adobe local development environments and mocking APIs that aren't in public documentation.
What it needs
Requires @adobe/aio-cli, node 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 Isolated Development Loop Overview Build a repeatable local loop for Adobe adapters using synthetic contracts before any remote Runtime or product call. 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 App Builder local modes differ: aio app dev runs actions locally and lacks activation records and some Runtime-only storage capabilities; aio app run uses remote Runtime actions with local UI. Offline fixtures must cover both product responses and those environment differences. Recheck the dated evidence map before relying on mutable product behavior. Authentication Use synthetic data and non-production aliases. Keep .env and .aio out of version control; pass configured values to actions rather than assuming local environment variables exist in deployed Runtime. Instructions 1. Inventory the adapter, SDK locks, App Builder configuration, fixtures, and current local-mode assumptions. 2. Define typed request, response, async-status, error, throttling, and redaction contracts from current docs. 3. Create synthetic fixtures for success, additive fields, malformed data, 401/403, 429, 5xx, and ambiguous completion. 4. Run unit and contract tests with network access disabled and secret canaries enabled. 5. If App Builder is used, exercise aio app dev and a separately approved aio app run path where Runtime fidelity matters. 6. Record mode differences, cleanup remote test artifacts, and keep only sanitized deterministic fixtures. 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-local-dev-loop