ideogram-upgrade-migration
/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".
- Author
- jeremylongshore ↗
- Repository
- tons-of-skills-marketplace ↗
- Licence
- MIT
- Last repository change
- 26.10.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
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".
Triggers from the description
Arguments
/ideogram-upgrade-migration <current-contract> <target-contract> <traffic-slice>
Original author description
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".
How it works
- Overview
- Prerequisites
- Current Contract
- Authentication
- Instructions
- Tool Discipline
- Approval Boundaries
- Error Handling
- Output
- Examples
SKILL.md preview
--- name: ideogram-upgrade-migration description: >- 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". allowed-tools: Read,Glob,Grep,Write,Edit argument-hint: "<current-contract> <target-contract> <traffic-slice>" version: 1.11.0 license: MIT author: Jeremy Longshore <jeremy@intentsolutions.io> tags: [saas, ideogram, migration] model: inherit effort: high compatibility: "Designed for Claude Code; live cutover requires change approval and paid canaries" --- # 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; `text_prompt` and `json_prompt` 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. Use Write and Edit for approved adapter, test, and migration documentation changes. Do not change live traffic or run parallel paid generation without approval. ## Approval Boundaries Require owners for endpoint choice, compatibility exceptions, model or rendering changes, extra spend, safety differences, and production cutover. Removing a legacy route requires proof that no consumer or in-flight generation depends on it. ## Error Handling - Stop when the target schema is undocumented or response safety fields cannot be reconciled. - Do not coerce a V3 enum into V4 merely because names look similar. - On canary divergence, halt target traffic, preserve identifiers, and reconcile stored assets before rollback. ## Output Return source and target contracts, diff classes, changed files, test matrix, shadow and canary metrics, spend, unresolved drift, traffic state, and rollback receipt. Exclude content, credentials, and URLs. ## Examples - Replace a legacy `/generate` adapter with V4 multipart behind a feature flag. - Reject a migration that blindly carries `FLASH` into the current V4 request. ## Validation Re-run contract, consumer, storage, and rollback tests against immutable SHAs. Verify the deployed traffic split and confirm no duplicate objects, orphaned generations, or retained temporary URLs remain. ## Resources - [Current first-party evidence map](references/official-docs.md) — use the dated endpoint, webhook, billing, team, and training links as the contract index for this workflow. - Recheck the endpoint-specific page and current OpenAPI description before relying on an enum, limit, beta feature, or lifecycle claim. - Record live observations as environment-specific evidence, not as universal vendor guarantees.
Files in this package (2)
- SKILL.md 4 KB
- references/official-docs.md 2 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · jeremylongshore/tons-of-skills-marketplace | 100 | MIT |
| HelixDevelopment/agent | 100 | MIT |
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 8a2bd13a97a5 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100ideogram-install-auth
Install and configure Ideogram SDK/CLI authentication. Use when setting up a new Ideogram integration, configuring API keys, or initializing Ideogram in your project. Trigger with phrases like "install ideogram", "setup ideogram", "ideogram auth", "configure ideogram API key". - 100ideogram-migration-deep-dive
Execute Ideogram major re-architecture and migration strategies with strangler fig pattern. Use when migrating to or from Ideogram, performing major version upgrades, or re-platforming existing integrations to Ideogram. Trigger with phrases like "migrate ideogram", "ideogram… - 100ideogram-migration-deep-dive
Plan and execute a staged migration across Ideogram legacy, V3, V4, P-Image, and tool endpoints with semantic comparison and rollback. Use when modernizing a production image workflow. Trigger with "migrate Ideogram legacy API", "move Ideogram V3 to V4", or "redesign an Ideogram image pipeline". - 100ideogram-sdk-patterns
Design an owned Ideogram REST adapter for multipart uploads, typed responses, deadlines, and vendor isolation. Use when building or reviewing application client code without inventing an official SDK. Trigger with "wrap Ideogram API", "build an Ideogram client", or "review Ideogram adapter code".