edge-computing
Cloudflare Workers, Deno Deploy, Vercel Edge Functions, edge patterns (geo-routing, caching). Use when implementing edge compute, CDN logic, or global low-latency APIs.
Works with
---
name: edge-computing
description: Cloudflare Workers, Deno Deploy, Vercel Edge Functions, edge patterns (geo-routing, caching). Use when implementing edge compute, CDN logic, or global low-latency APIs.
license: MIT
---
# Edge Computing — Cloudflare Workers, Deno Deploy
Compute global faible latence, proche utilisateur.
## Platforms
**Cloudflare Workers** — V8, 300+ POPs, KV/Durable
**Deno Deploy** — Deno, 30+ POPs, TypeScript
**Vercel Edge** — V8, 20+ POPs, Next.js
**Fastly Compute@Edge** — WASM, 70+ POPs
## Geo-Routing
```javascript
export default {
async fetch(req) {
const api = req.cf.country === 'US' ? 'us-api' : 'eu-api';
return fetch(`https://${api}.example.com${req.url}`);
}
};
```
## Edge Caching (KV)
```javascript
const key = new URL(req.url).pathname;
let cached = await env.KV.get(key);
if (cached) return new Response(cached, { headers: { 'X-Cache': 'HIT' } });
const resp = await fetch('https://origin.com' + key);
const body = await resp.text();
await env.KV.put(key, body, { expirationTtl: 3600 });
return new Response(body, { headers: { 'X-Cache': 'MISS' } });
```
## A/B Testing
```javascript
const variant = Math.random() < 0.5 ? 'A' : 'B';
resp.cookies.set('ab_test', variant);
```
## Bot Detection
```javascript
if (/bot|crawler/i.test(req.headers.get('User-Agent'))) {
return new Response('Forbidden', { status: 403 });
}
```
## Durable Objects (Stateful)
```javascript
export class ChatRoom {
async fetch(req) {
const [client, server] = Object.values(new WebSocketPair());
this.sessions.push(server); server.accept();
server.on('message', e => this.broadcast(e.data));
return new Response(null, { status: 101, webSocket: client });
}
}
```
## Constraints
**CPU** 10-50ms → offload heavy
**Memory** 128MB → streaming
**No FS** → KV/R2
---
Voir `@.claude/skills/wasm/SKILL.md`More Performance skills
seo-audit
coreyhaines31/marketingskills
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," or "indexing issues." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema. For AI search optimization, see ai-seo.
competitor-profiling
coreyhaines31/marketingskills
When the user wants to research, profile, or analyze competitors from their URLs. Also use when the user mentions 'competitor profile,' 'competitor research,' 'competitor analysis,' 'profile this competitor,' 'analyze competitor,' 'competitive intelligence,' 'competitor deep dive,' 'who are my competitors,' 'competitor landscape,' 'competitor dossier,' 'competitive audit,' or 'research these competitors.' Input is a list of competitor URLs. Output is structured competitor profile markdown files. For creating comparison/alternative pages from profiles, see competitors. For sales-specific battle cards, see sales-enablement.
vercel-optimize
vercel-labs/agent-skills
Use for Vercel cost and performance optimization on deployed projects, especially Next.js, SvelteKit, Nuxt, and limited Astro apps. Collect Vercel metrics, usage, project config, and code scan results first; investigate only metric-backed candidates; produce ranked recommendations grounded in verified files and version-aware Vercel/framework docs. Trigger for Vercel bill reduction, slow or expensive routes, caching opportunities, Function Invocations, Build Minutes, Fast Data Transfer, Core Web Vitals, Bot Management, Fluid compute, or cost breakdown requests.
