Agent skill · design visual · jeremylongshore
ideogram-core-workflow-a
Select and operate the current Ideogram generation route across V4 sync, V4 async, transparency, and P-Image. Use when designing a text-to-image workflow with explicit latency and output contracts. Trigger with "generate with Ideogram V4", "choose an Ideogram model route", or "build transparent Ideogram images".
Why this skill is useful
Provides specific API commands and parameters for generating images with Ideogram that the AI wouldn't reliably generate on its own.
What it needs
Requires npm installed locally. Requires ideogram account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Ideogram Generation Route Selection Overview Choose the smallest current generation surface that satisfies latency, transparency, prompt, and model requirements. Make route choice explicit so applications do not inherit stale legacy endpoints or accidentally treat synchronous and asynchronous lifecycles as equivalent. Prerequisites An approved use case, prompt and input classification, latency target, output count, and cost ceiling. A server-side key, positive credit, durable storage, and content-review policy. Current endpoint-specific documentation; generic examples do not override route contracts. Current Contract Ideogram documents V4 synchronous /v1/ideogram-v4/generate, V4 asynchronous /v1/ideogram-v4/async/generate, transparent variants, and P-Image sync/async routes. V4 accepts either text or structured JSON prompting; JSON prompting disables magic prompt. V4 FLASH currently returns 400. Authentication Send the server-side IDEOGRAMAPIKEY only through the Api-Key header to https://api.ideogram.ai. Never expose the key or direct paid-generation authority to a browser or untrusted tenant. Instructions 1. Classify whether the workload requires V4, transparency, P-Image, structured prompting, or compatibility with an existing V3 flow. 2. Choose synchronous handling only when the request deadline safely includes generation and immediate download; otherwise choose async. 3. Build the exact endpoint-specific multipart payload and reject mutually exclusive or unsupported fields before sending. 4. Bound output count, input size, rendering option, in-flight concurrency, and total operation deadline. 5. Validate safety on every returned image and persist approved assets immediately because vendor URLs expire. 6. For async work, persist generationid, reconcile webhook and polling results idempotently, and close only on a recognized terminal state. 7. Record route, policy, spend, safety, storage, and cleanup evidence without retaining content. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/ideogram-core-workflow-a