Execute Ideogram production deployment checklist and rollback procedures. Use when deploying Ideogram integrations to production, preparing for launch, or implementing go-live procedures. Trigger with phrases like "ideogram production", "deploy ideogram", "ideogram go-live", "ideogram launch checklist".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill ideogram-prod-checklist94
Quality
95%
Does it follow best practices?
Impact
95%
1.90xAverage score across 3 eval scenarios
Complete checklist for deploying Ideogram integrations to production.
npm test)# Pre-flight checks
curl -f https://staging.example.com/health
curl -s https://status.ideogram.com
# Gradual rollout - start with canary (10%)
kubectl apply -f k8s/production.yaml
kubectl set image deployment/ideogram-integration app=image:new --record
kubectl rollout pause deployment/ideogram-integration
# Monitor canary traffic for 10 minutes
sleep 600
# Check error rates and latency before continuing
# If healthy, continue rollout to 50%
kubectl rollout resume deployment/ideogram-integration
kubectl rollout pause deployment/ideogram-integration
sleep 300
# Complete rollout to 100%
kubectl rollout resume deployment/ideogram-integration
kubectl rollout status deployment/ideogram-integration| Alert | Condition | Severity |
|---|---|---|
| API Down | 5xx errors > 10/min | P1 |
| High Latency | p99 > 5000ms | P2 |
| Rate Limited | 429 errors > 5/min | P2 |
| Auth Failures | 401/403 errors > 0 | P1 |
async function healthCheck(): Promise<{ status: string; ideogram: any }> {
const start = Date.now();
try {
await ideogramClient.ping();
return { status: 'healthy', ideogram: { connected: true, latencyMs: Date.now() - start } };
} catch (error) {
return { status: 'degraded', ideogram: { connected: false, latencyMs: Date.now() - start } };
}
}kubectl rollout undo deployment/ideogram-integration
kubectl rollout status deployment/ideogram-integrationFor version upgrades, see ideogram-upgrade-migration.
213e2bd
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.