gamma-multi-env-setup
Configure Gamma across development, staging, and production environments. Use when setting up multi-environment deployments, configuring per-environment secrets, or implementing environment-specific Gamma configurations. Trigger with phrases like "gamma environments", "gamma staging", "gamma dev prod", "gamma environment setup", "gamma config by env".
What this skill does
# Gamma Multi-Environment Setup
## Overview
Configure Gamma API access across development, staging, and production environments. Since Gamma is a SaaS API with no self-hosted option, environment separation is achieved through separate workspaces (API keys), mock servers for development, and environment-aware client configuration.
## Prerequisites
- Separate Gamma workspaces (or at minimum separate API keys) per environment
- Secret management solution
- Completed `gamma-install-auth` setup
## Environment Architecture
```
┌─────────────────────────────────────────────────────────┐
│ Development │
│ API: localhost:9876 (mock server) or Gamma API │
│ Key: GAMMA_API_KEY=gma_dev_xxx │
│ Mock: enabled (no credits consumed) │
├─────────────────────────────────────────────────────────┤
│ Staging │
│ API: public-api.gamma.app (separate workspace) │
│ Key: GAMMA_API_KEY=gma_stg_xxx │
│ Mock: disabled │
├─────────────────────────────────────────────────────────┤
│ Production │
│ API: public-api.gamma.app (production workspace) │
│ Key: GAMMA_API_KEY=gma_prod_xxx (from secret manager) │
│ Mock: disabled │
└─────────────────────────────────────────────────────────┘
```
## Instructions
### Step 1: Environment Configuration
```typescript
// src/config/gamma.ts
interface GammaEnvConfig {
apiKey: string;
baseUrl: string;
useMock: boolean;
timeoutMs: number;
maxRetries: number;
}
function getGammaConfig(): GammaEnvConfig {
const env = process.env.NODE_ENV ?? "development";
const configs: Record<string, Partial<GammaEnvConfig>> = {
development: {
baseUrl: process.env.GAMMA_MOCK === "true"
? "http://localhost:9876/v1.0"
: "https://public-api.gamma.app/v1.0",
useMock: process.env.GAMMA_MOCK === "true",
timeoutMs: 60000,
maxRetries: 1,
},
staging: {
baseUrl: "https://public-api.gamma.app/v1.0",
useMock: false,
timeoutMs: 30000,
maxRetries: 3,
},
production: {
baseUrl: "https://public-api.gamma.app/v1.0",
useMock: false,
timeoutMs: 30000,
maxRetries: 5,
},
};
const apiKey = process.env.GAMMA_API_KEY;
if (!apiKey && !configs[env]?.useMock) {
throw new Error(`GAMMA_API_KEY required for ${env} environment`);
}
return {
apiKey: apiKey ?? "mock-key",
...configs[env],
} as GammaEnvConfig;
}
export const gammaConfig = getGammaConfig();
```
### Step 2: Environment-Aware Client Factory
```typescript
// src/gamma/factory.ts
import { createGammaClient } from "./client";
import { gammaConfig } from "../config/gamma";
let client: ReturnType<typeof createGammaClient> | null = null;
export function getGammaClient() {
if (!client) {
client = createGammaClient({
apiKey: gammaConfig.apiKey,
baseUrl: gammaConfig.baseUrl,
timeoutMs: gammaConfig.timeoutMs,
});
}
return client;
}
// Reset for testing
export function resetGammaClient() {
client = null;
}
```
### Step 3: Environment Files
```bash
# .env.development
GAMMA_API_KEY=gma_dev_xxxxxxxxxxxx
GAMMA_MOCK=false
NODE_ENV=development
LOG_LEVEL=debug
# .env.test
GAMMA_MOCK=true
NODE_ENV=test
LOG_LEVEL=warn
# .env.staging
GAMMA_API_KEY=gma_stg_xxxxxxxxxxxx
NODE_ENV=staging
LOG_LEVEL=info
# .env.production (use secret manager instead)
# GAMMA_API_KEY loaded from AWS Secrets Manager / Vault
NODE_ENV=production
LOG_LEVEL=warn
```
### Step 4: Production Secret Management
```typescript
// src/config/secrets.ts
// For production, fetch API key from secret manager at startup
import { SecretsManager } from "@aws-sdk/client-secrets-manager";
let cachedKey: string | null = null;
let cacheExpiry = 0;
async function getProductionApiKey(): Promise<string> {
if (cachedKey && Date.now() < cacheExpiry) return cachedKey;
const sm = new SecretsManager({ region: "us-east-1" });
const secret = await sm.getSecretValue({ SecretId: "gamma/api-key" });
cachedKey = JSON.parse(secret.SecretString!).apiKey;
cacheExpiry = Date.now() + 300000; // Cache for 5 minutes
return cachedKey!;
}
```
### Step 5: Environment Guards
```typescript
// src/guards.ts
function blockProduction(operation: string) {
if (process.env.NODE_ENV === "production") {
throw new Error(`${operation} is blocked in production`);
}
}
// Block destructive operations in production
async function deleteAllGenerations() {
blockProduction("deleteAllGenerations");
// ... cleanup logic for dev/staging
}
// Warn about credit-consuming operations in non-production
function warnCredits(env: string) {
if (env !== "production" && !gammaConfig.useMock) {
console.warn("WARNING: Using live Gamma API — credits will be consumed");
}
}
```
### Step 6: CI/CD Environment Configuration
```yaml
# .github/workflows/gamma.yml
jobs:
test:
runs-on: ubuntu-latest
env:
GAMMA_MOCK: 'true'
NODE_ENV: test
steps:
- uses: actions/checkout@v4
- run: npm ci && npm test
# Uses mock server — no API key needed, no credits consumed
staging:
runs-on: ubuntu-latest
if: github.ref == 'refs/heads/develop'
env:
GAMMA_API_KEY: ${{ secrets.GAMMA_STAGING_API_KEY }}
NODE_ENV: staging
steps:
- uses: actions/checkout@v4
- run: npm ci && npm run test:integration
production:
runs-on: ubuntu-latest
if: github.ref == 'refs/heads/main'
env:
GAMMA_API_KEY: ${{ secrets.GAMMA_PRODUCTION_API_KEY }}
NODE_ENV: production
steps:
- uses: actions/checkout@v4
- run: npm ci && npm run deploy
```
## Environment Checklist
| Check | Dev | Test | Staging | Production |
|-------|-----|------|---------|------------|
| API key source | .env file | Not needed (mock) | GitHub Secret | Secret Manager |
| Mock mode | Optional | Yes | No | No |
| Debug logging | On | On | On | Off |
| Credit consumption | Optional | None | Real (staging workspace) | Real |
| Secret manager | No | No | Optional | Required |
## Error Handling
| Issue | Cause | Solution |
|-------|-------|----------|
| Wrong API key for env | Env var mismatch | Verify `NODE_ENV` and matching key |
| Credits consumed in dev | Mock mode off | Set `GAMMA_MOCK=true` in development |
| Secret fetch fails | IAM permissions | Check secret manager access policy |
| Production data in dev | No env guard | Add `blockProduction()` guards |
## Resources
- [12-Factor App Config](https://12factor.net/config)
- [Gamma API Key Management](https://gamma.app/settings)
- [AWS Secrets Manager](https://docs.aws.amazon.com/secretsmanager/)
## Next Steps
Proceed to `gamma-observability` for monitoring setup.
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.