ideogram-multi-env-setup
Configure Ideogram across development, staging, and production environments. Use when setting up multi-environment deployments, configuring per-environment keys, or implementing environment-specific Ideogram configurations. Trigger with phrases like "ideogram environments", "ideogram staging", "ideogram dev prod", "ideogram environment setup", "ideogram multi-env". '
Profile →npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill ideogram-multi-env-setup --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Ideogram Multi-Environment Setup ## Overview Configure Ideogram API access across development, staging, and production with isolated API keys, environment-specific model/speed settings, and proper secret management. Each environment gets its own key and configuration to prevent cross-environment issues. ## Environment Strategy | Environment | API Key Source | Model | Speed | Cache | Billing | |-------------|---------------|-------|-------|-------|---------| | Development | `.env.local` | V_2_TURBO | TURBO | Disabled | Minimal top-up | | Staging | CI/CD secrets | V_2 | DEFAULT | 5 min TTL | Moderate | | Production | Secret manager | V_2 or V3 | DEFAULT | 10 min TTL | Full auto top-up | ## Instructions ### Step 1: Configuration Structure ```typescript // config/ideogram.ts type Environment = "development" | "staging" | "production"; interface IdeogramConfig { apiKey: string; defaultModel: string; renderingSpeed: string; timeout: number; maxRetries: number; concurrency: number; cache: { enabled: boolean; ttlSeconds: number }; debug: boolean; } const configs: Record<Environment, Omit<IdeogramConfig, "apiKey">> = { development: { defaultModel: "V_2_TURBO", renderingSpeed: "TURBO", tim
- Overview
- Environment Strategy
- Instructions
- Step 1: Configuration Structure
- Step 2: Environment Files
- Step 3: Secret Management by Platform
- Step 4: GitHub Actions with Environment Secrets
- Step 5: Startup Validation
- Error Handling
- Output
- Resources
- Next Steps
set -euo pipefail gh secret set IDEOGRAM_API_KEY_STAGING --env staging gh secret set IDEOGRAM_API_KEY --env production aws secretsmanager create-secret \ echo -n "your-staging-key" | gcloud secrets create ideogram-api-key-staging --data-file=- echo -n "your-production-key" | gcloud secrets create ideogram-api-key-prod --data-file=-
What does the ideogram-multi-env-setup skill do?
Configure Ideogram across development, staging, and production environments. Use when setting up multi-environment deployments, configuring per-environment keys, or implementing environment-specific Ideogram configurations. Trigger with phrases like "ideogram environments", "ideogram staging", "ideogram dev prod", "ideogram environment setup", "ideogram multi-env". '
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill ideogram-multi-env-setup --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,630 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.