@intentsolutionsio/vercel-pack 1.0.0

package/.claude-plugin/plugin.json

@@ -0,0 +1,17 @@
+{
+  "name": "vercel-pack",
+  "version": "1.0.0",
+  "description": "Claude Code skill pack for Vercel (30 skills)",
+  "author": {
+    "name": "Jeremy Longshore",
+    "email": "jeremy@intentsolutions.io"
+  },
+  "license": "MIT",
+  "keywords": [
+    "vercel",
+    "vercel",
+    "saas",
+    "sdk",
+    "integration"
+  ]
+}

package/000-docs/001-BL-LICN-license.txt

@@ -0,0 +1,3 @@
+MIT License
+
+Copyright (c) 2025 Jeremy Longshore

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 Jeremy Longshore
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,69 @@
+# Vercel Skill Pack
+
+> Claude Code skill pack for Vercel integration (30 skills)
+
+## Installation
+
+```bash
+/plugin install vercel-pack@claude-code-plugins-plus
+```
+
+## Skills Included
+
+### Standard Skills (S01-S12)
+| Skill | Description |
+|-------|-------------|
+| `vercel-install-auth` | Install Auth |
+| `vercel-hello-world` | Hello World |
+| `vercel-local-dev-loop` | Local Dev Loop |
+| `vercel-sdk-patterns` | Sdk Patterns |
+| `vercel-deploy-preview` | Deploy Preview |
+| `vercel-edge-functions` | Edge Functions |
+| `vercel-common-errors` | Common Errors |
+| `vercel-debug-bundle` | Debug Bundle |
+| `vercel-rate-limits` | Rate Limits |
+| `vercel-security-basics` | Security Basics |
+| `vercel-prod-checklist` | Prod Checklist |
+| `vercel-upgrade-migration` | Upgrade Migration |
+
+### Pro Skills (P13-P18)
+| Skill | Description |
+|-------|-------------|
+| `vercel-ci-integration` | Ci Integration |
+| `vercel-deploy-integration` | Deploy Integration |
+| `vercel-webhooks-events` | Webhooks Events |
+| `vercel-performance-tuning` | Performance Tuning |
+| `vercel-cost-tuning` | Cost Tuning |
+| `vercel-reference-architecture` | Reference Architecture |
+
+### Flagship Skills (F19-F24)
+| Skill | Description |
+|-------|-------------|
+| `vercel-multi-env-setup` | Multi Env Setup |
+| `vercel-observability` | Observability |
+| `vercel-incident-runbook` | Incident Runbook |
+| `vercel-data-handling` | Data Handling |
+| `vercel-enterprise-rbac` | Enterprise Rbac |
+| `vercel-migration-deep-dive` | Migration Deep Dive |
+
+### Flagship+ Skills (X25-X30)
+| Skill | Description |
+|-------|-------------|
+| `vercel-advanced-troubleshooting` | Advanced Troubleshooting |
+| `vercel-load-scale` | Load Scale |
+| `vercel-reliability-patterns` | Reliability Patterns |
+| `vercel-policy-guardrails` | Policy Guardrails |
+| `vercel-architecture-variants` | Architecture Variants |
+| `vercel-known-pitfalls` | Known Pitfalls |
+
+## Usage
+
+Skills trigger automatically when you discuss Vercel topics. For example:
+
+- "Help me set up Vercel" → triggers `vercel-install-auth`
+- "Debug this Vercel error" → triggers `vercel-common-errors`
+- "Deploy my Vercel integration" → triggers `vercel-deploy-integration`
+
+## License
+
+MIT

package/package.json

@@ -0,0 +1,43 @@
+{
+  "name": "@intentsolutionsio/vercel-pack",
+  "version": "1.0.0",
+  "description": "Claude Code skill pack for Vercel - 30 skills covering deployments, edge functions, preview environments, performance optimization, and production operations",
+  "main": "README.md",
+  "type": "module",
+  "files": [
+    "README.md",
+    "LICENSE",
+    ".claude-plugin/",
+    "skills/",
+    "000-docs/"
+  ],
+  "keywords": [
+    "claude-code",
+    "claude-code-plugin",
+    "vercel",
+    "deployment",
+    "edge-functions",
+    "serverless",
+    "preview-deployments",
+    "nextjs",
+    "ai-skills",
+    "saas-pack"
+  ],
+  "author": {
+    "name": "Jeremy Longshore",
+    "email": "jeremy@intentsolutions.io"
+  },
+  "license": "MIT",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/jeremylongshore/claude-code-plugins.git",
+    "directory": "plugins/saas-packs/vercel-pack"
+  },
+  "bugs": {
+    "url": "https://github.com/jeremylongshore/claude-code-plugins/issues"
+  },
+  "homepage": "https://claudecodeplugins.io/plugins/vercel-pack",
+  "publishConfig": {
+    "access": "public"
+  }
+}

package/skills/vercel-advanced-troubleshooting/SKILL.md

@@ -0,0 +1,261 @@
+---
+name: vercel-advanced-troubleshooting
+description: |
+  Apply Vercel advanced debugging techniques for hard-to-diagnose issues.
+  Use when standard troubleshooting fails, investigating complex race conditions,
+  or preparing evidence bundles for Vercel support escalation.
+  Trigger with phrases like "vercel hard bug", "vercel mystery error",
+  "vercel impossible to debug", "difficult vercel issue", "vercel deep debug".
+allowed-tools: Read, Grep, Bash(kubectl:*), Bash(curl:*), Bash(tcpdump:*)
+version: 1.0.0
+license: MIT
+author: Jeremy Longshore <jeremy@intentsolutions.io>
+---
+
+# Vercel Advanced Troubleshooting
+
+## Overview
+Deep debugging techniques for complex Vercel 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
+```bash
+#!/bin/bash
+# advanced-vercel-debug.sh
+
+BUNDLE="vercel-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=vercel-integration --since=1h > "$BUNDLE/logs/pods.log"
+journalctl -u vercel-service --since "1 hour ago" > "$BUNDLE/logs/system.log"
+
+# 2. Metrics dump
+curl -s localhost:9090/api/v1/query?query=vercel_requests_total > "$BUNDLE/metrics/requests.json"
+curl -s localhost:9090/api/v1/query?query=vercel_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=vercel > "$BUNDLE/traces/jaeger.json"
+
+# 5. Configuration state
+kubectl get cm vercel-config -o yaml > "$BUNDLE/config/configmap.yaml"
+kubectl get secret vercel-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
+
+```typescript
+// Test each layer independently
+async function diagnoseVercelIssue(): Promise<DiagnosisReport> {
+  const results: DiagnosisResult[] = [];
+
+  // Layer 1: Network connectivity
+  results.push(await testNetworkConnectivity());
+
+  // Layer 2: DNS resolution
+  results.push(await testDNSResolution('api.vercel.com'));
+
+  // Layer 3: TLS handshake
+  results.push(await testTLSHandshake('api.vercel.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
+
+```typescript
+// Strip down to absolute minimum
+async function minimalRepro(): Promise<void> {
+  // 1. Fresh client, no customization
+  const client = new VercelClient({
+    apiKey: process.env.VERCEL_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.code,
+      stack: error.stack,
+    });
+  }
+}
+```
+
+## Timing Analysis
+
+```typescript
+class TimingAnalyzer {
+  private timings: Map<string, number[]> = new Map();
+
+  async measure<T>(label: string, fn: () => Promise<T>): Promise<T> {
+    const start = performance.now();
+    try {
+      return await fn();
+    } finally {
+      const duration = performance.now() - start;
+      const existing = this.timings.get(label) || [];
+      existing.push(duration);
+      this.timings.set(label, existing);
+    }
+  }
+
+  report(): TimingReport {
+    const report: TimingReport = {};
+    for (const [label, times] of this.timings) {
+      report[label] = {
+        count: times.length,
+        min: Math.min(...times),
+        max: Math.max(...times),
+        avg: times.reduce((a, b) => a + b, 0) / times.length,
+        p95: this.percentile(times, 95),
+      };
+    }
+    return report;
+  }
+}
+```
+
+## Memory and Resource Analysis
+
+```typescript
+// Detect memory leaks in Vercel client usage
+const heapUsed: number[] = [];
+
+setInterval(() => {
+  const usage = process.memoryUsage();
+  heapUsed.push(usage.heapUsed);
+
+  // Alert on sustained growth
+  if (heapUsed.length > 60) { // 1 hour at 1/min
+    const trend = heapUsed[59] - heapUsed[0];
+    if (trend > 100 * 1024 * 1024) { // 100MB growth
+      console.warn('Potential memory leak in vercel integration');
+    }
+  }
+}, 60000);
+```
+
+## Race Condition Detection
+
+```typescript
+// Detect concurrent access issues
+class VercelConcurrencyChecker {
+  private inProgress: Set<string> = new Set();
+
+  async execute<T>(key: string, fn: () => Promise<T>): Promise<T> {
+    if (this.inProgress.has(key)) {
+      console.warn(`Concurrent access detected for ${key}`);
+    }
+
+    this.inProgress.add(key);
+    try {
+      return await fn();
+    } finally {
+      this.inProgress.delete(key);
+    }
+  }
+}
+```
+
+## Support Escalation Template
+
+```markdown
+## Vercel Support Escalation
+
+**Severity:** P[1-4]
+**Request ID:** [from error response]
+**Timestamp:** [ISO 8601]
+
+### Issue Summary
+[One paragraph description]
+
+### Steps to Reproduce
+1. [Step 1]
+2. [Step 2]
+
+### Expected vs Actual
+- Expected: [behavior]
+- Actual: [behavior]
+
+### Evidence Attached
+- [ ] Debug bundle (vercel-advanced-debug-*.tar.gz)
+- [ ] Minimal reproduction code
+- [ ] Timing analysis
+- [ ] Network capture (if relevant)
+
+### Workarounds Attempted
+1. [Workaround 1] - Result: [outcome]
+2. [Workaround 2] - Result: [outcome]
+```
+
+## Instructions
+
+### Step 1: Collect Evidence Bundle
+Run the comprehensive debug script to gather all relevant data.
+
+### Step 2: Systematic Isolation
+Test each layer independently to identify the failure point.
+
+### Step 3: Create Minimal Reproduction
+Strip down to the simplest failing case.
+
+### Step 4: Escalate with Evidence
+Use the support template with all collected evidence.
+
+## Output
+- Comprehensive debug bundle collected
+- Failure layer identified
+- Minimal reproduction created
+- Support escalation submitted
+
+## Error Handling
+| Issue | Cause | Solution |
+|-------|-------|----------|
+| Can't reproduce | Race condition | Add timing analysis |
+| Intermittent failure | Timing-dependent | Increase sample size |
+| No useful logs | Missing instrumentation | Add debug logging |
+| Memory growth | Resource leak | Use heap profiling |
+
+## Examples
+
+### Quick Layer Test
+```bash
+# Test each layer in sequence
+curl -v https://api.vercel.com/health 2>&1 | grep -E "(Connected|TLS|HTTP)"
+```
+
+## Resources
+- [Vercel Support Portal](https://support.vercel.com)
+- [Vercel Status Page](https://www.vercel-status.com)
+
+## Next Steps
+For load testing, see `vercel-load-scale`.

package/skills/vercel-architecture-variants/SKILL.md

@@ -0,0 +1,284 @@
+---
+name: vercel-architecture-variants
+description: |
+  Choose and implement Vercel validated architecture blueprints for different scales.
+  Use when designing new Vercel integrations, choosing between monolith/service/microservice
+  architectures, or planning migration paths for Vercel applications.
+  Trigger with phrases like "vercel architecture", "vercel blueprint",
+  "how to structure vercel", "vercel project layout", "vercel microservice".
+allowed-tools: Read, Grep
+version: 1.0.0
+license: MIT
+author: Jeremy Longshore <jeremy@intentsolutions.io>
+---
+
+# Vercel Architecture Variants
+
+## Overview
+Three validated architecture blueprints for Vercel 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/
+│   ├── vercel/
+│   │   ├── client.ts          # Singleton client
+│   │   ├── types.ts           # Types
+│   │   └── middleware.ts      # Express middleware
+│   ├── routes/
+│   │   └── api/
+│   │       └── vercel.ts    # API routes
+│   └── index.ts
+├── tests/
+│   └── vercel.test.ts
+└── package.json
+```
+
+### Key Characteristics
+- Single deployment unit
+- Synchronous Vercel calls in request path
+- In-memory caching
+- Simple error handling
+
+### Code Pattern
+```typescript
+// Direct integration in route handler
+app.post('/api/create', async (req, res) => {
+  try {
+    const result = await vercelClient.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/
+│   │   ├── vercel/
+│   │   │   ├── client.ts      # Client wrapper
+│   │   │   ├── service.ts     # Business logic
+│   │   │   ├── repository.ts  # Data access
+│   │   │   └── types.ts
+│   │   └── index.ts           # Service exports
+│   ├── controllers/
+│   │   └── vercel.ts
+│   ├── routes/
+│   ├── middleware/
+│   ├── queue/
+│   │   └── vercel-processor.ts  # Async processing
+│   └── index.ts
+├── config/
+│   └── vercel/
+└── package.json
+```
+
+### Key Characteristics
+- Separation of concerns
+- Background job processing
+- Redis caching
+- Circuit breaker pattern
+- Structured error handling
+
+### Code Pattern
+```typescript
+// Service layer abstraction
+class VercelService {
+  constructor(
+    private client: VercelClient,
+    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('vercel.post-create', result);
+
+    return result;
+  }
+}
+```
+
+---
+
+## Variant C: Microservice (Complex)
+
+**Best for:** Enterprise, 100K+ DAU, strict SLAs
+
+```
+vercel-service/              # Dedicated microservice
+├── src/
+│   ├── api/
+│   │   ├── grpc/
+│   │   │   └── vercel.proto
+│   │   └── rest/
+│   │       └── routes.ts
+│   ├── domain/
+│   │   ├── entities/
+│   │   ├── events/
+│   │   └── services/
+│   ├── infrastructure/
+│   │   ├── vercel/
+│   │   │   ├── client.ts
+│   │   │   ├── mapper.ts
+│   │   │   └── circuit-breaker.ts
+│   │   ├── cache/
+│   │   ├── queue/
+│   │   └── database/
+│   └── index.ts
+├── config/
+├── k8s/
+│   ├── deployment.yaml
+│   ├── service.yaml
+│   └── hpa.yaml
+└── package.json
+
+other-services/
+├── order-service/       # Calls vercel-service
+├── payment-service/
+└── notification-service/
+```
+
+### Key Characteristics
+- Dedicated Vercel microservice
+- gRPC for internal communication
+- Event-driven architecture
+- Database per service
+- Kubernetes autoscaling
+- Distributed tracing
+- Circuit breaker per service
+
+### Code Pattern
+```typescript
+// Event-driven with domain isolation
+class VercelAggregate {
+  private events: DomainEvent[] = [];
+
+  process(command: VercelCommand): void {
+    // Domain logic
+    const result = this.execute(command);
+
+    // Emit domain event
+    this.events.push(new VercelProcessedEvent(result));
+  }
+
+  getUncommittedEvents(): DomainEvent[] {
+    return [...this.events];
+  }
+}
+
+// Event handler
+@EventHandler(VercelProcessedEvent)
+class VercelEventHandler {
+  async handle(event: VercelProcessedEvent): Promise<void> {
+    // Saga orchestration
+    await this.sagaOrchestrator.continue(event);
+  }
+}
+```
+
+---
+
+## Decision Matrix
+
+| Factor | Monolith | Service Layer | Microservice |
+|--------|----------|---------------|--------------|
+| Team Size | 1-5 | 5-20 | 20+ |
+| DAU | < 10K | 10K-100K | 100K+ |
+| Deployment Frequency | Weekly | Daily | Continuous |
+| Failure Isolation | None | Partial | Full |
+| Operational Complexity | Low | Medium | High |
+| Time to Market | Fastest | Moderate | Slowest |
+
+## Migration Path
+
+```
+Monolith → Service Layer:
+1. Extract Vercel code to service/
+2. Add caching layer
+3. Add background processing
+
+Service Layer → Microservice:
+1. Create dedicated vercel-service repo
+2. Define gRPC contract
+3. Add event bus
+4. Deploy to Kubernetes
+5. Migrate traffic gradually
+```
+
+## Instructions
+
+### Step 1: Assess Requirements
+Use the decision matrix to identify appropriate variant.
+
+### Step 2: Choose Architecture
+Select Monolith, Service Layer, or Microservice based on needs.
+
+### Step 3: Implement Structure
+Set up project layout following the chosen blueprint.
+
+### Step 4: Plan Migration Path
+Document upgrade path for future scaling.
+
+## Output
+- Architecture variant selected
+- Project structure implemented
+- Migration path documented
+- Appropriate patterns applied
+
+## Error Handling
+| Issue | Cause | Solution |
+|-------|-------|----------|
+| Over-engineering | Wrong variant choice | Start simpler |
+| Performance issues | Wrong layer | Add caching/async |
+| Team friction | Complex architecture | Simplify or train |
+| Deployment complexity | Microservice overhead | Consider service layer |
+
+## Examples
+
+### Quick Variant Check
+```bash
+# Count team size and DAU to select variant
+echo "Team: $(git log --format='%ae' | sort -u | wc -l) developers"
+echo "DAU: Check analytics dashboard"
+```
+
+## Resources
+- [Monolith First](https://martinfowler.com/bliki/MonolithFirst.html)
+- [Microservices Guide](https://martinfowler.com/microservices/)
+- [Vercel Architecture Guide](https://vercel.com/docs/architecture)
+
+## Next Steps
+For common anti-patterns, see `vercel-known-pitfalls`.