Agent skill · software engineering · jeremylongshore
ideogram-local-dev-loop
Build a fixture-first local loop for Ideogram multipart requests, async states, safety outcomes, and expiring assets. Use when developing or testing without uncontrolled API spend. Trigger with "mock Ideogram locally", "test Ideogram fixtures", or "debug an Ideogram adapter".
Why this skill is useful
Adds a mock server and typed client wrapper for Ideogram that enables offline development and testing workflows.
What it needs
Requires node 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 Fixture-First Development Loop Overview Develop the Ideogram boundary against owned request and response contracts before spending credit. Model multipart fields, asynchronous lifecycle states, unsafe outputs, transient errors, and expiring URLs as fixtures so the fast loop remains deterministic and privacy-safe. Prerequisites The repository's adapter seam, test runner, fixture policy, and data classification. Sanitized synthetic examples for success, unsafe output, validation failure, throttling, and terminal failure. An opt-in live-smoke flag that is disabled by default and on untrusted forks. Current Contract Current generation surfaces include V4 synchronous and asynchronous routes, transparent variants, P-Image, and V3 compatibility routes. Async work returns a generationid; status is reconciled by appending that returned value to GET /v1/generations/ or by receiving a webhook. Returned asset URLs are temporary. Authentication Fixtures must not contain credentials. When a separately approved live lane runs, inject IDEOGRAMAPIKEY server-side and send it only in the Api-Key header to the configured first-party host. Instructions 1. Read the adapter and enumerate request fields, response variants, error classes, and storage side effects. 2. Create sanitized fixtures for sync success, async submission, in-progress polling, safe and unsafe completion, 400, 401, 422, 429, and 503. 3. Test multipart construction by field name and file metadata without snapshotting secrets or customer content. 4. Verify idempotent status reconciliation, duplicate webhook handling, bounded polling, URL download, and durable object persistence. 5. Keep the paid live smoke behind an explicit environment flag, trusted context, credit ceiling, and synthetic prompt. 6. Compare live response shape to fixtures, update only reviewed schema drift, and record cleanup. Tool Discipline Use Read, Glob, and Grep to locate adapters, fixtures, and test commands. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/ideogram-local-dev-loop