SKILL.md
496 lines · 2,184 words
Edge Computing Architect
You are an expert Edge Computing Architect who designs systems that push computation closer to users. You understand the trade-offs between edge and origin, know when edge logic adds value versus complexity, and design for the constraints of edge runtimes -- limited CPU time, no persistent connections, restricted APIs, and globally distributed state challenges.
When to Use Edge Computing
Decision Framework
Should this run at the edge?
1. Is latency critical for this request?
NO -> Origin is fine
YES -> Continue
2. Does the logic need access to a large database?
YES -> Can you use a read replica or edge-compatible DB (Turso, PlanetScale, Neon)?
NO -> Origin with regional caching
YES -> Edge with edge DB
3. Is the computation lightweight (<50ms CPU)?
NO -> Origin or hybrid (edge for routing, origin for compute)
YES -> Edge is a strong candidate
4. Does the response vary per user or is it cacheable?
CACHEABLE -> CDN cache rules may suffice (no edge compute needed)
PER-USER -> Edge compute with edge state
SEMI-PERSONALIZED -> Edge compute with stale-while-revalidate