Agent skill · software engineering · jeremylongshore
ideogram-reference-architecture
Design an Ideogram service boundary with policy gateway, queue, async state, verified webhooks, polling, moderation, storage, and audit. Use when creating or reviewing a production architecture. Trigger with "architect Ideogram", "design an Ideogram service", or "review an Ideogram system diagram".
Why this skill is useful
Provides specific prompt templates and architecture for Ideogram integrations that the AI wouldn't 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
Ideogram Reference Architecture Overview Define ownership and data flow for a production Ideogram integration. Keep user authorization, paid vendor authority, request validation, async state, event verification, content review, durable media, and audit evidence as explicit components. Prerequisites Workload, tenant and identity model, data class, SLO, budget, region, and retention policy. Expected endpoint mix, input sizes, concurrency, publication destinations, and failure modes. Owners for billing, security, moderation, storage, operations, and vendor escalation. Current Contract The API uses server-side Api-Key, endpoint-specific multipart requests, sync and async generation, item-level safety, signed async webhooks, polling, and temporary asset URLs. Default capacity is 10 in-flight requests. These contracts require stateful application orchestration even when the product experience is synchronous. Authentication Place IDEOGRAMAPIKEY only in a private vendor adapter. The policy gateway authenticates application identities and authorizes tenant, use case, spend, input, output, and destination separately. Instructions 1. Define ingress and policy gateway boundaries for identity, tenant, rights, media validation, safety, copyright settings, budget, and admission. 2. Route accepted work to a durable queue and an account-level concurrency controller. 3. Use a vendor adapter that owns endpoint schemas, multipart, deadlines, typed errors, and content-free telemetry. 4. Persist request and generationid state before async delivery, then reconcile verified webhooks with polling. 5. Pass safe outputs through a downloader that validates media and stores opaque tenant-scoped objects immediately. 6. Publish only from the application object store after required review; never authorize from a vendor URL. 7. Add outbox, audit, deletion, incident, canary, and rollback paths with explicit owners. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/ideogram-reference-architecture