ideogram-multi-env-setup
/ideogram-multi-env-setup
Configure Ideogram across development, staging, and production environments. Use when setting up multi-environment deployments, configuring per-environment secrets, or implementing environment-specific Ideogram configurations. Trigger with phrases like "ideogram environments", "ideogram staging", "ideogram dev prod", "ideogram environment setup", "ideogram config by env".
- Author
- HelixDevelopment ↗
- Repository
- agent ↗
- Licence
- MIT
- Last repository change
- 14.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 5
No signals detected. Repository changed on 14.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
Configure Ideogram across development, staging, and production environments. Use when setting up multi-environment deployments, configuring per-environment secrets, or implementing environment-specific Ideogram configurations. Trigger with phrases like "ideogram environments", "ideogram staging", "ideogram dev prod", "ideogram environment setup", "ideogram config by env".
Triggers from the description
Original author description
Configure Ideogram across development, staging, and production environments. Use when setting up multi-environment deployments, configuring per-environment secrets, or implementing environment-specific Ideogram configurations. Trigger with phrases like "ideogram environments", "ideogram staging", "ideogram dev prod", "ideogram environment setup", "ideogram config by env".
How it works
- Overview
- Prerequisites
- Environment Strategy
- Configuration Structure
- Environment Detection
- Secret Management by Environment
- Environment Isolation
- Feature Flags by Environment
- Instructions
- Output
SKILL.md preview
---
name: ideogram-multi-env-setup
description: |
Configure Ideogram across development, staging, and production environments.
Use when setting up multi-environment deployments, configuring per-environment secrets,
or implementing environment-specific Ideogram configurations.
Trigger with phrases like "ideogram environments", "ideogram staging",
"ideogram dev prod", "ideogram environment setup", "ideogram config by env".
allowed-tools: Read, Write, Edit, Bash(aws:*), Bash(gcloud:*), Bash(vault:*)
version: 1.0.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
---
# Ideogram Multi-Environment Setup
## Overview
Configure Ideogram across development, staging, and production environments.
## Prerequisites
- Separate Ideogram accounts or API keys per environment
- Secret management solution (Vault, AWS Secrets Manager, etc.)
- CI/CD pipeline with environment variables
- Environment detection in application
## Environment Strategy
| Environment | Purpose | API Keys | Data |
|-------------|---------|----------|------|
| Development | Local dev | Test keys | Sandbox |
| Staging | Pre-prod validation | Staging keys | Test data |
| Production | Live traffic | Production keys | Real data |
## Configuration Structure
```
config/
├── ideogram/
│ ├── base.json # Shared config
│ ├── development.json # Dev overrides
│ ├── staging.json # Staging overrides
│ └── production.json # Prod overrides
```
### base.json
```json
{
"timeout": 30000,
"retries": 3,
"cache": {
"enabled": true,
"ttlSeconds": 60
}
}
```
### development.json
```json
{
"apiKey": "${IDEOGRAM_API_KEY}",
"baseUrl": "https://api-sandbox.ideogram.com",
"debug": true,
"cache": {
"enabled": false
}
}
```
### staging.json
```json
{
"apiKey": "${IDEOGRAM_API_KEY_STAGING}",
"baseUrl": "https://api-staging.ideogram.com",
"debug": false
}
```
### production.json
```json
{
"apiKey": "${IDEOGRAM_API_KEY_PROD}",
"baseUrl": "https://api.ideogram.com",
"debug": false,
"retries": 5
}
```
## Environment Detection
```typescript
// src/ideogram/config.ts
import baseConfig from '../../config/ideogram/base.json';
type Environment = 'development' | 'staging' | 'production';
function detectEnvironment(): Environment {
const env = process.env.NODE_ENV || 'development';
const validEnvs: Environment[] = ['development', 'staging', 'production'];
return validEnvs.includes(env as Environment)
? (env as Environment)
: 'development';
}
export function getIdeogramConfig() {
const env = detectEnvironment();
const envConfig = require(`../../config/ideogram/${env}.json`);
return {
...baseConfig,
...envConfig,
environment: env,
};
}
```
## Secret Management by Environment
### Local Development
```bash
# .env.local (git-ignored)
IDEOGRAM_API_KEY=sk_test_dev_***
```
### CI/CD (GitHub Actions)
```yaml
env:
IDEOGRAM_API_KEY: ${{ secrets.IDEOGRAM_API_KEY_${{ matrix.environment }} }}
```
### Production (Vault/Secrets Manager)
```bash
# AWS Secrets Manager
aws secretsmanager get-secret-value --secret-id ideogram/production/api-key
# GCP Secret Manager
gcloud secrets versions access latest --secret=ideogram-api-key
# HashiCorp Vault
vault kv get -field=api_key secret/ideogram/production
```
## Environment Isolation
```typescript
// Prevent production operations in non-prod
function guardProductionOperation(operation: string): void {
const config = getIdeogramConfig();
if (config.environment !== 'production') {
console.warn(`[ideogram] ${operation} blocked in ${config.environment}`);
throw new Error(`${operation} only allowed in production`);
}
}
// Usage
async function deleteAllData() {
guardProductionOperation('deleteAllData');
// Dangerous operation here
}
```
## Feature Flags by Environment
```typescript
const featureFlags: Record<Environment, Record<string, boolean>> = {
development: {
newFeature: true,
betaApi: true,
},
staging: {
newFeature: true,
betaApi: false,
},
production: {
newFeature: false,
betaApi: false,
},
};
```
## Instructions
### Step 1: Create Config Structure
Set up the base and per-environment configuration files.
### Step 2: Implement Environment Detection
Add logic to detect and load environment-specific config.
### Step 3: Configure Secrets
Store API keys securely using your secret management solution.
### Step 4: Add Environment Guards
Implement safeguards for production-only operations.
## Output
- Multi-environment config structure
- Environment detection logic
- Secure secret management
- Production safeguards enabled
## Error Handling
| Issue | Cause | Solution |
|-------|-------|----------|
| Wrong environment | Missing NODE_ENV | Set environment variable |
| Secret not found | Wrong secret path | Verify secret manager config |
| Config merge fails | Invalid JSON | Validate config files |
| Production guard triggered | Wrong environment | Check NODE_ENV value |
## Examples
### Quick Environment Check
```typescript
const env = getIdeogramConfig();
console.log(`Running in ${env.environment} with ${env.baseUrl}`);
```
## Resources
- [Ideogram Environments Guide](https://docs.ideogram.com/environments)
- [12-Factor App Config](https://12factor.net/config)
## Next Steps
For observability setup, see `ideogram-observability`.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · HelixDevelopment/agent | 100 | MIT |
| jeremylongshore/tons-of-skills-marketplace | 100 | MIT |
Database snapshot: 13.11.2026 · package version 966d2ceaa884 (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
- 100instantly-multi-env-setup
Configure Instantly across development, staging, and production environments. Use when setting up multi-environment deployments, configuring per-environment secrets, or implementing environment-specific Instantly configurations. Trigger with phrases like "instantly… - 100coderabbit-multi-env-setup
Configure CodeRabbit across development, staging, and production environments. Use when setting up multi-environment deployments, configuring per-environment secrets, or implementing environment-specific CodeRabbit configurations. Trigger with phrases like "coderabbit… - 100klaviyo-multi-env-setup
Configure Klaviyo across development, staging, and production environments. Use when setting up multi-environment deployments, configuring per-environment API keys, or implementing environment-specific Klaviyo configurations. Trigger with phrases like "klaviyo environments",… - 100lokalise-multi-env-setup
Configure Lokalise across development, staging, and production environments. Use when setting up multi-environment deployments, configuring per-environment secrets, or implementing environment-specific Lokalise configurations. Trigger with phrases like "lokalise environments",… - 100environment-setup
Configure and manage development, staging, and production environments. Use when setting up environment variables, managing configurations, or separating environments. Handles .env files, config management, and environment-specific settings.