How do I install the Edge Runtime Handbook skill?

Run npx skillmds@latest add bh611627/edge-runtime-handbook in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Edge Runtime Handbook skill do?

Next.js Edge Runtime limits - what runs where and how to split Node-only code It is listed under Web & Frontend on SkillMD.

Is Edge Runtime Handbook safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Edge Runtime Handbook?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Edge Runtime Handbook free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Edge Runtime Handbook?

bh611627 (@bh611627) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Edge Runtime Handbook by bh611627 — Agent Skill

Name: Edge Runtime Handbook
Author: bh611627

File contents

Instructions

When to Use

Use when deciding Edge vs Node for a Route Handler or middleware.
Prefer next-server-patterns for general App Router placement.
Prefer auth-handbook if Edge auth APIs are the blocker.

Explain Edge vs Node runtimes in Next.js for the user’s code. Always verify against the installed Next version.

Decision matrix

Workload	Prefer	Why
Middleware auth gate (coarse)	Edge	Default; keep tiny
Prisma / native addons / `fs`	Node	Typical Edge blockers
Long-lived WS/SSE fan-out	Node (`realtime-handbook`)	Connection lifespan
Geo/header rewrite only	Edge	Low I/O
Heavy crypto / PDF / image ops	Node	CPU + APIs

Flag imports: fs, native Prisma client, some crypto patterns, large WASM - usually Node.
Middleware defaults to Edge - keep fast; no heavy I/O or DB.
Route segment config runtime = 'edge' | 'nodejs' - justify per route.
Env: Edge often inlines process.env - secrets risk; public env only on Edge unless you know the deploy model.
Split: Edge validates + forwards to a Node Route Handler / internal API when needed.
Observability: many APM exporters are Node-only - split instrumentation (observability-handbook).

Outcomes

Table: file → current runtime → recommended runtime → blockers.

Output Rules

Link to Next docs concepts by name; no fabricated API lists - say “verify against installed Next version”.

Scope and boundaries

In scope: runtime choice, import restrictions, split patterns.
Out of scope: Cloudflare Workers specifics unless the user deploys there.

Safety

Read-only; warn on secret exposure on Edge.

Troubleshooting

Prisma on Edge: Data Proxy / driver adapter or move to Node - state tradeoffs.
Bundle too large for Edge: move dependencies behind a Node route.
Middleware timeout: shrink work; push DB to Node.

Related skills

next-server-patterns - Node vs Edge split
server-caching-handbook - edge-compatible caches
auth-handbook - session checks on Edge limits
realtime-handbook - long-lived connections

GitHub: https://github.com/bh611627/skillcodex/tree/main/skills/edge-runtime-handbook/SKILL.md
npm: https://www.npmjs.com/package/@skillcodex/skills

---name: edge-runtime-handbookdescription: Next.js Edge Runtime limits - what runs where and how to split Node-only code---# Instructions## When to Use- Use when deciding Edge vs Node for a Route Handler or middleware.- Prefer `next-server-patterns` for general App Router placement.- Prefer `auth-handbook` if Edge auth APIs are the blocker.Explain **Edge vs Node** runtimes in **Next.js** for the user’s code. Always **verify against the installed Next version**.### Decision matrix| Workload | Prefer | Why ||----------|--------|-----|| Middleware auth gate (coarse) | Edge | Default; keep tiny || Prisma / native addons / `fs` | Node | Typical Edge blockers || Long-lived WS/SSE fan-out | Node (`realtime-handbook`) | Connection lifespan || Geo/header rewrite only | Edge | Low I/O || Heavy crypto / PDF / image ops | Node | CPU + APIs |1. Flag imports: `fs`, native Prisma client, some `crypto` patterns, large WASM - usually **Node**.2. **Middleware** defaults to Edge - keep fast; no heavy I/O or DB.3. **Route segment config** `runtime = 'edge' | 'nodejs'` - justify per route.4. **Env:** Edge often inlines `process.env` - secrets risk; public env only on Edge unless you know the deploy model.5. **Split:** Edge validates + forwards to a Node Route Handler / internal API when needed.6. **Observability:** many APM exporters are Node-only - split instrumentation (`observability-handbook`).## Outcomes- Table: file → current runtime → recommended runtime → blockers.## Output RulesLink to Next docs concepts by name; no fabricated API lists - say “verify against installed Next version”.## Scope and boundaries- **In scope:** runtime choice, import restrictions, split patterns.- **Out of scope:** Cloudflare Workers specifics unless the user deploys there.## Safety- Read-only; warn on secret exposure on Edge.## Troubleshooting- **Prisma on Edge:** Data Proxy / driver adapter or move to Node - state tradeoffs.- **Bundle too large for Edge:** move dependencies behind a Node route.- **Middleware timeout:** shrink work; push DB to Node.## Related skills- [`next-server-patterns`](../next-server-patterns/SKILL.md) - Node vs Edge split- [`server-caching-handbook`](../server-caching-handbook/SKILL.md) - edge-compatible caches- [`auth-handbook`](../auth-handbook/SKILL.md) - session checks on Edge limits- [`realtime-handbook`](../realtime-handbook/SKILL.md) - long-lived connections**GitHub:** https://github.com/bh611627/skillcodex/tree/main/skills/edge-runtime-handbook/SKILL.md **npm:** https://www.npmjs.com/package/@skillcodex/skills

Frequently asked questions