Claude Code skill pack for Adobe (30 skills)
Installation
Open Claude Code and run this command:
/plugin install adobe-pack@claude-code-plugins-plus
Use --global to install for all projects, or --project for current project only.
Skills (30)
Apply Adobe advanced debugging techniques for hard-to-diagnose issues.
Adobe Advanced Troubleshooting
Overview
Deep debugging techniques for complex Adobe issues that resist standard troubleshooting.
Prerequisites
- Access to production logs and metrics
- kubectl access to clusters
- Network capture tools available
- Understanding of distributed tracing
Evidence Collection Framework
Comprehensive Debug Bundle
#!/bin/bash
# advanced-adobe-debug.sh
BUNDLE="adobe-advanced-debug-$(date +%Y%m%d-%H%M%S)"
mkdir -p "$BUNDLE"/{logs,metrics,network,config,traces}
# 1. Extended logs (1 hour window)
kubectl logs -l app=adobe-integration --since=1h > "$BUNDLE/logs/pods.log"
journalctl -u adobe-service --since "1 hour ago" > "$BUNDLE/logs/system.log"
# 2. Metrics dump
curl -s localhost:9090/api/v1/query?query=adobe_requests_total > "$BUNDLE/metrics/requests.json"
curl -s localhost:9090/api/v1/query?query=adobe_errors_total > "$BUNDLE/metrics/errors.json"
# 3. Network capture (30 seconds)
timeout 30 tcpdump -i any port 443 -w "$BUNDLE/network/capture.pcap" &
# 4. Distributed traces
curl -s localhost:16686/api/traces?service=adobe > "$BUNDLE/traces/jaeger.json"
# 5. Configuration state
kubectl get cm adobe-config -o yaml > "$BUNDLE/config/configmap.yaml"
kubectl get secret adobe-secrets -o yaml > "$BUNDLE/config/secrets-redacted.yaml"
tar -czf "$BUNDLE.tar.gz" "$BUNDLE"
echo "Advanced debug bundle: $BUNDLE.tar.gz"
Systematic Isolation
Layer-by-Layer Testing
// Test each layer independently
async function diagnoseAdobeIssue(): Promise<DiagnosisReport> {
const results: DiagnosisResult[] = [];
// Layer 1: Network connectivity
results.push(await testNetworkConnectivity());
// Layer 2: DNS resolution
results.push(await testDNSResolution('api.adobe.com'));
// Layer 3: TLS handshake
results.push(await testTLSHandshake('api.adobe.com'));
// Layer 4: Authentication
results.push(await testAuthentication());
// Layer 5: API response
results.push(await testAPIResponse());
// Layer 6: Response parsing
results.push(await testResponseParsing());
return { results, firstFailure: results.find(r => !r.success) };
}
Minimal Reproduction
// Strip down to absolute minimum
async function minimalRepro(): Promise<void> {
// 1. Fresh client, no customization
const client = new AdobeClient({
apiKey: process.env.ADOBE_API_KEY!,
});
// 2. Simplest possible call
try {
const result = await client.ping();
console.log('Ping successful:', result);
} catch (error) {
console.error('Ping failed:', {
message: error.message,
code: error.codChoose and implement Adobe validated architecture blueprints for different scales.
Adobe Architecture Variants
Overview
Three validated architecture blueprints for Adobe integrations.
Prerequisites
- Understanding of team size and DAU requirements
- Knowledge of deployment infrastructure
- Clear SLA requirements
- Growth projections available
Variant A: Monolith (Simple)
Best for: MVPs, small teams, < 10K daily active users
my-app/
├── src/
│ ├── adobe/
│ │ ├── client.ts # Singleton client
│ │ ├── types.ts # Types
│ │ └── middleware.ts # Express middleware
│ ├── routes/
│ │ └── api/
│ │ └── adobe.ts # API routes
│ └── index.ts
├── tests/
│ └── adobe.test.ts
└── package.json
Key Characteristics
- Single deployment unit
- Synchronous Adobe calls in request path
- In-memory caching
- Simple error handling
Code Pattern
// Direct integration in route handler
app.post('/api/create', async (req, res) => {
try {
const result = await adobeClient.create(req.body);
res.json(result);
} catch (error) {
res.status(500).json({ error: error.message });
}
});
Variant B: Service Layer (Moderate)
Best for: Growing startups, 10K-100K DAU, multiple integrations
my-app/
├── src/
│ ├── services/
│ │ ├── adobe/
│ │ │ ├── client.ts # Client wrapper
│ │ │ ├── service.ts # Business logic
│ │ │ ├── repository.ts # Data access
│ │ │ └── types.ts
│ │ └── index.ts # Service exports
│ ├── controllers/
│ │ └── adobe.ts
│ ├── routes/
│ ├── middleware/
│ ├── queue/
│ │ └── adobe-processor.ts # Async processing
│ └── index.ts
├── config/
│ └── adobe/
└── package.json
Key Characteristics
- Separation of concerns
- Background job processing
- Redis caching
- Circuit breaker pattern
- Structured error handling
Code Pattern
// Service layer abstraction
class AdobeService {
constructor(
private client: AdobeClient,
private cache: CacheService,
private queue: QueueService
) {}
async createResource(data: CreateInput): Promise<Resource> {
// Business logic before API call
const validated = this.validate(data);
// Check cache
const cached = await this.cache.get(cacheKey);
if (cached) return cached;
// API call with retry
const result = await this.withRetry(() =>
this.client.create(validated)
);
// Cache result
await this.cache.set(cacheKey, result, 300);
// Async follow-up
await this.queue.enqueue('adobe.post-create', result);
return result;
}
}
Variant C: Microservice (Complex)
Be
Configure Adobe CI/CD integration with GitHub Actions and testing.
Adobe CI Integration
Overview
Set up CI/CD pipelines for Adobe integrations with automated testing.
Prerequisites
- GitHub repository with Actions enabled
- Adobe test API key
- npm/pnpm project configured
Instructions
Step 1: Create GitHub Actions Workflow
Create .github/workflows/adobe-integration.yml:
name: Adobe Integration Tests
on:
push:
branches: [main]
pull_request:
branches: [main]
env:
ADOBE_API_KEY: ${{ secrets.ADOBE_API_KEY }}
jobs:
test:
runs-on: ubuntu-latest
env:
ADOBE_API_KEY: ${{ secrets.ADOBE_API_KEY }}
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: '20'
cache: 'npm'
- run: npm ci
- run: npm test -- --coverage
- run: npm run test:integration
Step 2: Configure Secrets
gh secret set ADOBE_API_KEY --body "sk_test_***"
Step 3: Add Integration Tests
describe('Adobe Integration', () => {
it.skipIf(!process.env.ADOBE_API_KEY)('should connect', async () => {
const client = getAdobeClient();
const result = await client.healthCheck();
expect(result.status).toBe('ok');
});
});
Output
- Automated test pipeline
- PR checks configured
- Coverage reports uploaded
- Release workflow ready
Error Handling
| Issue | Cause | Solution |
|---|---|---|
| Secret not found | Missing configuration | Add secret via gh secret set |
| Tests timeout | Network issues | Increase timeout or mock |
| Auth failures | Invalid key | Check secret value |
Examples
Release Workflow
on:
push:
tags: ['v*']
jobs:
release:
runs-on: ubuntu-latest
env:
ADOBE_API_KEY: ${{ secrets.ADOBE_API_KEY_PROD }}
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: '20'
- run: npm ci
- name: Verify Adobe production readiness
run: npm run test:integration
- run: npm run build
- run: npm publish
Branch Protection
required_status_checks:
- "test"
- "adobe-integration"
Resources
Next Steps
For deployment patterns, see adobe-deploy-integration.
Diagnose and fix Adobe common errors and exceptions.
Adobe Common Errors
Overview
Quick reference for the top 10 most common Adobe errors and their solutions.
Prerequisites
- Adobe SDK installed
- API credentials configured
- Access to error logs
Instructions
Step 1: Identify the Error
Check error message and code in your logs or console.
Step 2: Find Matching Error Below
Match your error to one of the documented cases.
Step 3: Apply Solution
Follow the solution steps for your specific error.
Output
- Identified error cause
- Applied fix
- Verified resolution
Error Handling
Authentication Failed
Error Message:
Authentication error: Invalid API key
Cause: API key is missing, expired, or invalid.
Solution:
# Verify API key is set
echo $ADOBE_API_KEY
Rate Limit Exceeded
Error Message:
Rate limit exceeded. Please retry after X seconds.
Cause: Too many requests in a short period.
Solution:
Implement exponential backoff. See adobe-rate-limits skill.
Network Timeout
Error Message:
Request timeout after 30000ms
Cause: Network connectivity or server latency issues.
Solution:
// Increase timeout
const client = new Client({ timeout: 60000 });
Examples
Quick Diagnostic Commands
# Check Adobe status
curl -s https://status.adobe.com
# Verify API connectivity
curl -I https://api.adobe.com
# Check local configuration
env | grep ADOBE
Escalation Path
- Collect evidence with
adobe-debug-bundle - Check Adobe status page
- Contact support with request ID
Resources
Next Steps
For comprehensive debugging, see adobe-debug-bundle.
Execute Adobe primary workflow: Core Workflow A.
Adobe Core Workflow A
Overview
Primary money-path workflow for Adobe. This is the most common use case.
Prerequisites
- Completed
adobe-install-authsetup - Understanding of Adobe core concepts
- Valid API credentials configured
Instructions
Step 1: Initialize
// Step 1 implementation
Step 2: Execute
// Step 2 implementation
Step 3: Finalize
// Step 3 implementation
Output
- Completed Core Workflow A execution
- Expected results from Adobe API
- Success confirmation or error details
Error Handling
| Error | Cause | Solution |
|---|---|---|
| Error 1 | Cause | Solution |
| Error 2 | Cause | Solution |
Examples
Complete Workflow
// Complete workflow example
Common Variations
- Variation 1: Description
- Variation 2: Description
Resources
Next Steps
For secondary workflow, see adobe-core-workflow-b.
Execute Adobe secondary workflow: Core Workflow B.
Adobe Core Workflow B
Overview
Secondary workflow for Adobe. Complements the primary workflow.
Prerequisites
- Completed
adobe-install-authsetup - Familiarity with
adobe-core-workflow-a - Valid API credentials configured
Instructions
Step 1: Setup
// Step 1 implementation
Step 2: Process
// Step 2 implementation
Step 3: Complete
// Step 3 implementation
Output
- Completed Core Workflow B execution
- Results from Adobe API
- Success confirmation or error details
Error Handling
| Aspect | Workflow A | Workflow B |
|---|---|---|
| Use Case | Primary | Secondary |
| Complexity | Medium | Lower |
| Performance | Standard | Optimized |
Examples
Complete Workflow
// Complete workflow example
Error Recovery
// Error handling code
Resources
Next Steps
For common errors, see adobe-common-errors.
Optimize Adobe costs through tier selection, sampling, and usage monitoring.
Adobe Cost Tuning
Overview
Optimize Adobe costs through smart tier selection, sampling, and usage monitoring.
Prerequisites
- Access to Adobe billing dashboard
- Understanding of current usage patterns
- Database for usage tracking (optional)
- Alerting system configured (optional)
Pricing Tiers
| Tier | Monthly Cost | Included | Overage |
|---|---|---|---|
| Free | $0 | 1,000 requests | N/A |
| Pro | $99 | 100,000 requests | $0.001/request |
| Enterprise | Custom | Unlimited | Volume discounts |
Cost Estimation
interface UsageEstimate {
requestsPerMonth: number;
tier: string;
estimatedCost: number;
recommendation?: string;
}
function estimateAdobeCost(requestsPerMonth: number): UsageEstimate {
if (requestsPerMonth <= 1000) {
return { requestsPerMonth, tier: 'Free', estimatedCost: 0 };
}
if (requestsPerMonth <= 100000) {
return { requestsPerMonth, tier: 'Pro', estimatedCost: 99 };
}
const proOverage = (requestsPerMonth - 100000) * 0.001;
const proCost = 99 + proOverage;
return {
requestsPerMonth,
tier: 'Pro (with overage)',
estimatedCost: proCost,
recommendation: proCost > 500
? 'Consider Enterprise tier for volume discounts'
: undefined,
};
}
Usage Monitoring
class AdobeUsageMonitor {
private requestCount = 0;
private bytesTransferred = 0;
private alertThreshold: number;
constructor(monthlyBudget: number) {
this.alertThreshold = monthlyBudget * 0.8; // 80% warning
}
track(request: { bytes: number }) {
this.requestCount++;
this.bytesTransferred += request.bytes;
if (this.estimatedCost() > this.alertThreshold) {
this.sendAlert('Approaching Adobe budget limit');
}
}
estimatedCost(): number {
return estimateAdobeCost(this.requestCount).estimatedCost;
}
private sendAlert(message: string) {
// Send to Slack, email, PagerDuty, etc.
}
}
Cost Reduction Strategies
Step 1: Request Sampling
function shouldSample(samplingRate = 0.1): boolean {
return Math.random() < samplingRate;
}
// Use for non-critical telemetry
if (shouldSample(0.1)) { // 10% sample
await adobeClient.trackEvent(event);
}
Step 2: Batching Requests
// Instead of N individual calls
await Promise.all(ids.map(id => adobeClient.get(id)));
// Use batch endpoint (1 call)
await adobeClient.batchGet(ids);
Step 3: Caching (from P16)
- Cache frequently accessed data
- Use cache invalidation webhooks
Implement Adobe PII handling, data retention, and GDPR/CCPA compliance patterns.
Adobe Data Handling
Overview
Handle sensitive data correctly when integrating with Adobe.
Prerequisites
- Understanding of GDPR/CCPA requirements
- Adobe SDK with data export capabilities
- Database for audit logging
- Scheduled job infrastructure for cleanup
Data Classification
| Category | Examples | Handling |
|---|---|---|
| PII | Email, name, phone | Encrypt, minimize |
| Sensitive | API keys, tokens | Never log, rotate |
| Business | Usage metrics | Aggregate when possible |
| Public | Product names | Standard handling |
PII Detection
const PII_PATTERNS = [
{ type: 'email', regex: /[a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\.[a-zA-Z]{2,}/g },
{ type: 'phone', regex: /\b\d{3}[-.]?\d{3}[-.]?\d{4}\b/g },
{ type: 'ssn', regex: /\b\d{3}-\d{2}-\d{4}\b/g },
{ type: 'credit_card', regex: /\b\d{4}[- ]?\d{4}[- ]?\d{4}[- ]?\d{4}\b/g },
];
function detectPII(text: string): { type: string; match: string }[] {
const findings: { type: string; match: string }[] = [];
for (const pattern of PII_PATTERNS) {
const matches = text.matchAll(pattern.regex);
for (const match of matches) {
findings.push({ type: pattern.type, match: match[0] });
}
}
return findings;
}
Data Redaction
function redactPII(data: Record<string, any>): Record<string, any> {
const sensitiveFields = ['email', 'phone', 'ssn', 'password', 'apiKey'];
const redacted = { ...data };
for (const field of sensitiveFields) {
if (redacted[field]) {
redacted[field] = '[REDACTED]';
}
}
return redacted;
}
// Use in logging
console.log('Adobe request:', redactPII(requestData));
Data Retention Policy
Retention Periods
| Data Type | Retention | Reason |
|---|---|---|
| API logs | 30 days | Debugging |
| Error logs | 90 days | Root cause analysis |
| Audit logs | 7 years | Compliance |
| PII | Until deletion request | GDPR/CCPA |
Automatic Cleanup
async function cleanupAdobeData(retentionDays: number): Promise<void> {
const cutoff = new Date();
cutoff.setDate(cutoff.getDate() - retentionDays);
await db.adobeLogs.deleteMany({
createdAt: { $lt: cutoff },
type: { $nin: ['audit', 'compliance'] },
});
}
// Schedule daily cleanup
cron.schedule('0 3 * * *', () => cleanupAdobeData(30));
Collect Adobe debug evidence for support tickets and troubleshooting.
Adobe Debug Bundle
Overview
Collect all necessary diagnostic information for Adobe support tickets.
Prerequisites
- Adobe SDK installed
- Access to application logs
- Permission to collect environment info
Instructions
Step 1: Create Debug Bundle Script
#!/bin/bash
# adobe-debug-bundle.sh
BUNDLE_DIR="adobe-debug-$(date +%Y%m%d-%H%M%S)"
mkdir -p "$BUNDLE_DIR"
echo "=== Adobe Debug Bundle ===" > "$BUNDLE_DIR/summary.txt"
echo "Generated: $(date)" >> "$BUNDLE_DIR/summary.txt"
Step 2: Collect Environment Info
# Environment info
echo "--- Environment ---" >> "$BUNDLE_DIR/summary.txt"
node --version >> "$BUNDLE_DIR/summary.txt" 2>&1
npm --version >> "$BUNDLE_DIR/summary.txt" 2>&1
echo "ADOBE_API_KEY: ${ADOBE_API_KEY:+[SET]}" >> "$BUNDLE_DIR/summary.txt"
Step 3: Gather SDK and Logs
# SDK version
npm list @adobe/sdk 2>/dev/null >> "$BUNDLE_DIR/summary.txt"
# Recent logs (redacted)
grep -i "adobe" ~/.npm/_logs/*.log 2>/dev/null | tail -50 >> "$BUNDLE_DIR/logs.txt"
# Configuration (redacted - secrets masked)
echo "--- Config (redacted) ---" >> "$BUNDLE_DIR/summary.txt"
cat .env 2>/dev/null | sed 's/=.*/=***REDACTED***/' >> "$BUNDLE_DIR/config-redacted.txt"
# Network connectivity test
echo "--- Network Test ---" >> "$BUNDLE_DIR/summary.txt"
echo -n "API Health: " >> "$BUNDLE_DIR/summary.txt"
curl -s -o /dev/null -w "%{http_code}" https://api.adobe.com/health >> "$BUNDLE_DIR/summary.txt"
echo "" >> "$BUNDLE_DIR/summary.txt"
Step 4: Package Bundle
tar -czf "$BUNDLE_DIR.tar.gz" "$BUNDLE_DIR"
echo "Bundle created: $BUNDLE_DIR.tar.gz"
Output
adobe-debug-YYYYMMDD-HHMMSS.tar.gzarchive containing:summary.txt- Environment and SDK infologs.txt- Recent redacted logsconfig-redacted.txt- Configuration (secrets removed)
Error Handling
| Item | Purpose | Included | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Environment versions | Compatibility check | ✓ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| SDK version | Version-specific bugs | ✓ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Error logs (redacted) | Root cause analysis | ✓ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Config (redacted) | Configuration issues | ✓ | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Network test | Connectivi
Deploy Adobe integrations to Vercel, Fly.
ReadWriteEditBash(vercel:*)Bash(fly:*)Bash(gcloud:*)
Adobe Deploy IntegrationOverviewDeploy Adobe-powered applications to popular platforms with proper secrets management. Prerequisites
Vercel DeploymentEnvironment Setup
vercel.json Configuration
Fly.io Deploymentfly.toml
Secrets
Google Cloud RunDockerfile
Deploy Script
Environment Configuration Pattern
Health Check EndpointConfigure Adobe enterprise SSO, role-based access control, and organization management.
ReadWriteEdit
Adobe Enterprise RBACOverviewConfigure enterprise-grade access control for Adobe integrations. Prerequisites
Role Definitions
Role Implementation
SSO IntegrationSAML Configuration
OAuth2/OIDC Integration
Organization ManagementCreate a minimal working Adobe example.
ReadWriteEdit
Adobe Hello WorldOverviewMinimal working example demonstrating core Adobe functionality. Prerequisites
InstructionsStep 1: Create Entry FileCreate a new file for your hello world example. Step 2: Import and Initialize Client
Step 3: Make Your First API Call
Output
Error Handling
ExamplesTypeScript Example
Python Example
ResourcesNext StepsProceed to Execute Adobe incident response procedures with triage, mitigation, and postmortem.
ReadGrepBash(kubectl:*)Bash(curl:*)
Adobe Incident RunbookOverviewRapid incident response procedures for Adobe-related outages. Prerequisites
Severity Levels
Quick Triage
Decision Tree
Immediate Actions by Error Type401/403 - Authentication
429 - Rate Limited
500/503 - Adobe Errors
Communication TemplatesInternal (Slack)Install and configure Adobe SDK/CLI authentication.
ReadWriteEditBash(npm:*)Bash(pip:*)Grep
Adobe Install & AuthOverviewSet up Adobe SDK/CLI and configure authentication credentials. Prerequisites
InstructionsStep 1: Install SDK
Step 2: Configure Authentication
Step 3: Verify Connection
Output
Error Handling
ExamplesTypeScript Setup
Python Setup
ResourcesNext StepsAfter successful auth, proceed to Identify and avoid Adobe anti-patterns and common integration mistakes.
ReadGrep
Adobe Known PitfallsOverviewCommon mistakes and anti-patterns when integrating with Adobe. Prerequisites
Pitfall #1: Synchronous API Calls in Request Path❌ Anti-Pattern
✅ Better Approach
Pitfall #2: Not Handling Rate Limits❌ Anti-Pattern
✅ Better Approach
Pitfall #3: Leaking API Keys❌ Anti-Pattern
✅ Better Approach
Pitfall #4: Ignoring Idempotency❌ Anti-Pattern
✅ Better Approach
Pitfall #5: Not Validating WebhooksImplement Adobe load testing, auto-scaling, and capacity planning strategies.
ReadWriteEditBash(k6:*)Bash(kubectl:*)
Adobe Load & ScaleOverviewLoad testing, scaling strategies, and capacity planning for Adobe integrations. Prerequisites
Load Testing with k6Basic Load Test
Run Load Test
Scaling PatternsHorizontal Scaling
Connection PoolingConfigure Adobe local development with hot reload and testing.
ReadWriteEditBash(npm:*)Bash(pnpm:*)Grep
Adobe Local Dev LoopOverviewSet up a fast, reproducible local development workflow for Adobe. Prerequisites
InstructionsStep 1: Create Project Structure
Step 2: Configure Environment
Step 3: Setup Hot Reload
Step 4: Configure Testing
Output
Error Handling
ExamplesMock Adobe Responses
Debug Mode
ResourcesNext StExecute Adobe major re-architecture and migration strategies with strangler fig pattern.
ReadWriteEditBash(npm:*)Bash(node:*)Bash(kubectl:*)
Adobe Migration Deep DiveOverviewComprehensive guide for migrating to or from Adobe, or major version upgrades. Prerequisites
Migration Types
Pre-Migration AssessmentStep 1: Current State Analysis
Step 2: Data Inventory
Migration Strategy: Strangler Fig Pattern
Implementation PlanPhase 1: Setup (Week 1-2)
Phase 2: Adapter Layer (Week 3-4)Configure Adobe across development, staging, and production environments.
ReadWriteEditBash(aws:*)Bash(gcloud:*)Bash(vault:*)
Adobe Multi-Environment SetupOverviewConfigure Adobe across development, staging, and production environments. Prerequisites
Environment Strategy
Configuration Structure
base.json
development.json
staging.json
production.json
Environment Detection
Secret Management by EnvironmentLocal Development
CISet up comprehensive observability for Adobe integrations with metrics, traces, and alerts.
ReadWriteEdit
Adobe ObservabilityOverviewSet up comprehensive observability for Adobe integrations. Prerequisites
Metrics CollectionKey Metrics
Prometheus Metrics
Instrumented Client
Distributed TracingOpenTelemetry SetupOptimize Adobe API performance with caching, batching, and connection pooling.
ReadWriteEdit
Adobe Performance TuningOverviewOptimize Adobe API performance with caching, batching, and connection pooling. Prerequisites
Latency Benchmarks
Caching StrategyResponse Caching
Redis Caching (Distributed)
Request Batching
Connection Optimization
Pagination OptimizationImplement Adobe lint rules, policy enforcement, and automated guardrails.
ReadWriteEditBash(npx:*)
Adobe Policy & GuardrailsOverviewAutomated policy enforcement and guardrails for Adobe integrations. Prerequisites
ESLint RulesCustom Adobe Plugin
ESLint Configuration
Pre-Commit Hooks
TypeScript Strict Patterns
Architecture Decision RecordsADR TemplateExecute Adobe production deployment checklist and rollback procedures.
ReadBash(kubectl:*)Bash(curl:*)Grep
Adobe Production ChecklistOverviewComplete checklist for deploying Adobe integrations to production. Prerequisites
InstructionsStep 1: Pre-Deployment Configuration
Step 2: Code Quality Verification
Step 3: Infrastructure Setup
Step 4: Documentation Requirements
Step 5: Deploy with Gradual Rollout
Output
Error Handling
ExamplesHealth Check ImplementationImplement Adobe rate limiting, backoff, and idempotency patterns.
ReadWriteEdit
Adobe Rate LimitsOverviewHandle Adobe rate limits gracefully with exponential backoff and idempotency. Prerequisites
InstructionsStep 1: Understand Rate Limit Tiers
Step 2: Implement Exponential Backoff with Jitter
Step 3: Add Idempotency Keys
Output
Error Handling
ExamplesFactory Pattern (Multi-tenant)
Apply Adobe security best practices for secrets and access control.
ReadWriteGrep
Adobe Security BasicsOverviewSecurity best practices for Adobe API keys, tokens, and access control. Prerequisites
InstructionsStep 1: Configure Environment Variables
Step 2: Implement Secret Rotation
Step 3: Apply Least Privilege
Output
Error Handling
ExamplesService Account Pattern
Webhook Signature Verification
Security Checklist
Audit LoggingAnalyze, plan, and execute Adobe SDK upgrades with breaking change detection.
ReadWriteEditBash(npm:*)Bash(git:*)
Adobe Upgrade & MigrationOverviewGuide for upgrading Adobe SDK versions and handling breaking changes. Prerequisites
InstructionsStep 1: Check Current Version
Step 2: Review Changelog
Step 3: Create Upgrade Branch
Step 4: Handle Breaking ChangesUpdate import statements, configuration, and method signatures as needed. Output
Error Handling
ExamplesImport Changes
Configuration Changes
Rollback Procedure
Deprecation Handling
ResourcesNext StepsFor CI integration during upgrades, see Implement Adobe webhook signature validation and event handling.
ReadWriteEditBash(curl:*)
Adobe Webhooks & EventsOverviewSecurely handle Adobe webhooks with signature validation and replay protection. Prerequisites
Webhook Endpoint SetupExpress.js
Signature Verification
Event Handler PatternReady to use adobe-pack?Related Pluginsai-ethics-validatorAI ethics and fairness validation ai-experiment-loggerTrack and analyze AI experiments with a web dashboard and MCP tools ai-ml-engineering-packProfessional AI/ML Engineering toolkit: Prompt engineering, LLM integration, RAG systems, AI safety with 12 expert plugins ai-sdk-agentsMulti-agent orchestration with AI SDK v5 - handoffs, routing, and coordination for any AI provider (OpenAI, Anthropic, Google) anomaly-detection-systemDetect anomalies and outliers in data automl-pipeline-builderBuild AutoML pipelines
Tags
adobesaassdkintegration
|