Agent skill · software engineering · jeremylongshore
ideogram-upgrade-migration
Upgrade an Ideogram adapter against current OpenAPI and endpoint contracts while preserving rollback. Use when moving versions, fields, or transport behavior without redesigning the product workflow. Trigger with "upgrade Ideogram API", "check Ideogram schema drift", or "migrate an Ideogram endpoint".
Why this skill is useful
Provides specific migration scripts and commands for transitioning between Ideogram API versions that the AI wouldn't reliably generate on its own.
What it needs
Requires npm 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 Contract Upgrade Overview Move a bounded adapter contract to a current Ideogram route without mixing the change with a broad product migration. Diff OpenAPI and endpoint documentation, update owned types and fixtures, run shadow comparisons, and preserve an explicit traffic rollback. Prerequisites Current adapter SHA, endpoint inventory, target contract, consumers, and accountable owner. Captured sanitized fixtures and compatibility requirements. Canary budget, traffic control, storage parity, and rollback deadline. Current Contract The current surface spans V4, P-Image, V3, outcome-focused tools, custom training, and routes labeled Legacy Endpoints. V4 generation uses endpoint-specific multipart forms; textprompt and jsonprompt are mutually exclusive, and current V4 FLASH support must not be inferred from V3 examples. Authentication Keep the same server-side Api-Key boundary unless a documented first-party auth change is part of the reviewed diff. Never copy production credentials or payloads into migration fixtures. Instructions 1. Inventory current routes, methods, fields, enums, errors, async states, safety fields, and downstream storage assumptions. 2. Retrieve current OpenAPI and endpoint docs, then classify additive, changed, deprecated, legacy, and undocumented differences. 3. Update owned types and route adapters while preserving unknown fields needed for drift detection. 4. Build sanitized before-and-after fixtures for success, unsafe output, validation, throttling, capacity, webhook, polling, and URL expiry. 5. Run offline contract tests and a staging shadow that does not double-publish or overwrite assets. 6. Canary a bounded live slice within an approved credit ceiling and compare status, latency, safety, output count, and storage outcomes. 7. Promote only after convergence; retain the prior route and state reconciliation until the rollback window closes. Tool Discipline Use Read, Glob, and Grep for routes, schemas, consumers, and fixtures. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/ideogram-upgrade-migration