Agent skill · software engineering · jeremylongshore
ideogram-deploy-integration
Deploy an Ideogram server boundary with queues, storage, safety enforcement, observability, canaries, and rollback. Use when shipping a new runtime or changing production topology. Trigger with "deploy Ideogram", "ship an Ideogram worker", or "review Ideogram production architecture".
Why this skill is useful
Adds deployment scripts and configurations for Vercel, Cloud Run, and Docker that are not commonly found in public documentation.
What it needs
Requires docker, gcloud, vercel installed locally. Requires ideogram account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Ideogram Deployment Boundary Overview Deploy Ideogram behind an application-owned server, queue, safety policy, and durable object store. Match runtime deadlines to sync or async behavior, keep paid authority out of clients, and preserve a reversible traffic path. Prerequisites Frozen release SHA, platform owner, environment, traffic slice, SLO, and rollback target. Secret manager, queue or concurrency control, object storage, monitoring, and incident response. Positive credit, billing owner, approved synthetic canary, and retention policy. Current Contract Ideogram calls use https://api.ideogram.ai; default capacity is 10 in-flight requests. Async routes return generationid and support webhook delivery with polling fallback. Image URLs expire, so deployment must download validated outputs into application storage before acknowledging durable completion. Authentication Inject IDEOGRAMAPIKEY into the server or worker identity and send it only as Api-Key. A public browser receives application-scoped authorization, never the vendor credential or direct vendor URL. Instructions 1. Map request ingress, tenant auth, validation, queue, Ideogram route, webhook, polling, download, safety, storage, and publishing boundaries. 2. Choose sync only when platform and request deadlines safely cover generation plus download; otherwise persist async state. 3. Configure account-level concurrency below verified capacity, bounded queues, retry deadlines, and graceful drain. 4. Inject secrets by runtime reference, restrict egress to the approved host, and prevent request or response body logging. 5. Validate safety and media type before writing an opaque tenant-scoped object; discard temporary URLs. 6. Deploy a synthetic canary, compare status, latency, storage, safety, and cost signals, then increase traffic gradually. 7. Roll back traffic and reconcile in-flight generations and objects before terminating the prior version. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/ideogram-deploy-integration