From ideogram-pack
Diagnose and fix Ideogram common errors and exceptions. Use when encountering Ideogram errors, debugging failed requests, or troubleshooting integration issues. Trigger with phrases like "ideogram error", "fix ideogram", "ideogram not working", "debug ideogram".
How this skill is triggered — by the user, by Claude, or both
Slash command
/ideogram-pack:ideogram-common-errorsThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Quick reference for the top 10 most common Ideogram errors and their solutions.
Quick reference for the top 10 most common Ideogram errors and their solutions.
Check error message and code in your logs or console.
Match your error to one of the documented cases.
Follow the solution steps for your specific error.
Error Message:
Authentication error: Invalid API key
Cause: API key is missing, expired, or invalid.
Solution:
# Verify API key is set
echo $IDEOGRAM_API_KEY
Error Message:
Rate limit exceeded. Please retry after X seconds.
Cause: Too many requests in a short period.
Solution:
Implement exponential backoff. See ideogram-rate-limits skill.
Error Message:
Request timeout after 30000ms
Cause: Network connectivity or server latency issues.
Solution:
// Increase timeout
const client = new Client({ timeout: 60000 }); # 60000: 1 minute in ms
set -euo pipefail
# Check Ideogram status
curl -s https://status.ideogram.com
# Verify API connectivity
curl -I https://api.ideogram.com
# Check local configuration
env | grep IDEOGRAM
ideogram-debug-bundleFor comprehensive debugging, see ideogram-debug-bundle.
npx claudepluginhub terrylica/claude-code-plugins-plus --plugin ideogram-packGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.
4plugins reuse this skill
First indexed Jul 11, 2026