Official agent skill

Dce Edge

DCE-safe require() patterns and edge runtime constraints. An agent skill from vercel/next.js.

OfficialMITAuto-check passedBackend & APIs

Install Dce Edge

skills CLI

$ npx skills add vercel/next.js --skill dce-edge -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install vercel/next.js dce-edge --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/vercel/next.js.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/dce-edge .claude/skills/dce-edge && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "dce-edge" agent skill from https://github.com/vercel/next.js/tree/canary/.agents/skills/dce-edge into .claude/skills/dce-edge/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dce-edge", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/vercel/next.js/tree/canary/.agents/skills/dce-edge

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add vercel/next.js --skill dce-edge -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install vercel/next.js dce-edge --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/vercel/next.js.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/dce-edge .agents/skills/dce-edge && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "dce-edge" agent skill from https://github.com/vercel/next.js/tree/canary/.agents/skills/dce-edge into .agents/skills/dce-edge/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dce-edge", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add vercel/next.js --skill dce-edge -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install vercel/next.js dce-edge --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/vercel/next.js.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/dce-edge .cursor/skills/dce-edge && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "dce-edge" agent skill from https://github.com/vercel/next.js/tree/canary/.agents/skills/dce-edge into .cursor/skills/dce-edge/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dce-edge", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/vercel/next.js.git --path .agents/skills/dce-edge

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add vercel/next.js --skill dce-edge -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install vercel/next.js dce-edge --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/vercel/next.js.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/dce-edge .gemini/skills/dce-edge && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "dce-edge" agent skill from https://github.com/vercel/next.js/tree/canary/.agents/skills/dce-edge into .gemini/skills/dce-edge/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dce-edge", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install vercel/next.js dce-edge

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add vercel/next.js --skill dce-edge -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/vercel/next.js.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/dce-edge .github/skills/dce-edge && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "dce-edge" agent skill from https://github.com/vercel/next.js/tree/canary/.agents/skills/dce-edge into .github/skills/dce-edge/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dce-edge", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add vercel/next.js --skill dce-edge -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install vercel/next.js dce-edge --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/vercel/next.js.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/dce-edge .opencode/skills/dce-edge && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "dce-edge" agent skill from https://github.com/vercel/next.js/tree/canary/.agents/skills/dce-edge into .opencode/skills/dce-edge/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "dce-edge", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: dce-edge
GitHub stars: 143k
Token cost: ~1k tokens
SKILL.md length: 428 words
Files: 1
Skills in repo: 27
Repo updated: Oct 8, 2026
First seen: Oct 8, 2026
Licence: MIT

At a glance

DCE-safe require() patterns and edge runtime constraints. An agent skill from vercel/next.js.

Writing conditional require() calls
SKILL.md covers DCE-Safe require() Pattern, TypeScript + DCE Interaction, Compile-Time Switcher Pattern and NEXT_RUNTIME Is Not a Feature…, plus 4 more sections
Calls pnpm
Guarding Node-only imports (node:stream etc.)

What it does

Dce Edge is an agent skill from vercel/next.js, published by the product's own GitHub organization. DCE-safe require() patterns and edge runtime constraints. Use when writing conditional require() calls, guarding Node-only imports (node:stream etc.), or editing define-env-plugin.ts / app-render / stream-utils for edge builds. Covers if/else branching for webpack DCE, TypeScript definite assignment, the NEXTRUNTIME vs real feature flag distinction, and forcing flags false for edge in define-env.ts.

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Backend & APIs, covering Serverless. It works with TypeScript and webpack. The licence is MIT.

When your agent uses it

Writing conditional require() calls
Guarding Node-only imports (node:stream etc.)
Editing define-env-plugin.ts / app-render / stream-utils for edge builds

Example prompts

“/dce-edge”

Requirements

Node.js

What it can do on your machine

Read from SKILL.md and the folder at commit a32ddfd. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- pnpm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use pnpm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Dce Edge loads about 1k tokens when it runs. Until then it costs about 103 tokens; SKILL.md has 428 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~103
When it runs · the whole SKILL.md, loaded when a task matches: ~1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from vercel/next.js at commit a32ddfd, republished under its MIT licence (© vercel). 428 words, ~1,026 tokens.

Download SKILL.mdSave it as .claude/skills/dce-edge/SKILL.md (or your agent's skills folder).

name: dce-edge
description: DCE-safe require() patterns and edge runtime constraints. Use when writing conditional require() calls, guarding Node-only imports (node:stream etc.), or editing define-env-plugin.ts / app-render / stream-utils for edge builds. Covers if/else branching for webpack DCE, TypeScript definite assignment, the NEXT_RUNTIME vs real feature flag distinction, and forcing flags false for edge in define-env.ts.
metadata.internal: true

DCE + Edge

Use this skill when changing conditional require() paths, Node-only imports, or edge/runtime branching.

DCE-Safe `require()` Pattern

Webpack only DCEs a require() when it sits inside the dead branch of an if/else whose condition DefinePlugin can evaluate at compile time.

// CORRECT - webpack can eliminate the dead branch
if (process.env.__NEXT_USE_NODE_STREAMS) {
  require('node:stream')
} else {
  // web path
}

What does NOT work:

Early-return/throw guards: webpack doesn't do control-flow analysis for throws/returns, so the require() is still traced.
Bare if without else: works for inline node:* specifiers but NOT for require('./some-module') that pulls a new file into the module graph.

Always test edge changes with pnpm test-start-webpack on test/e2e/app-dir/app/standalone.test.ts (has edge routes), not with NEXT_SKIP_ISOLATE=1 which skips the full webpack compilation.

TypeScript + DCE Interaction

Use if/else (not two independent if blocks) when assigning a variable conditionally on process.env.X. TypeScript cannot prove exhaustiveness across if (flag) { x = a }; if (!flag) { x = b } and will error with "variable used before being assigned". The if/else pattern satisfies both TypeScript (definite assignment) and webpack DCE.

Compile-Time Switcher Pattern

Platform-specific code (node vs web) can use a single .ts switcher module that conditionally require()s either .node.ts or .web.ts into a typed variable, then re-exports the shared runtime API as named exports. Keep the branch as if/else so DefinePlugin can dead-code-eliminate the unused require(). Keep shared types canonical in .node.ts, with .web.ts importing them via import type and the switcher re-exporting types as needed. Examples: stream-ops.ts and debug-channel-server.ts.

`NEXT_RUNTIME` Is Not a Feature Flag

In user-project webpack server compilers, process.env.NEXT_RUNTIME is inlined to 'nodejs'. Guarding Node-only require('node:*') paths with NEXT_RUNTIME === 'nodejs' does not prune anything. For feature-gated codepaths, guard on the real feature define (e.g. process.env.__NEXT_USE_NODE_STREAMS).

Show full SKILL.md (166 more words)Show less

Edge Runtime Constraints

Edge routes do NOT use pre-compiled runtime bundles. They are compiled by the user's webpack/Turbopack, so define-env.ts controls DCE. Feature flags that gate node:* imports must be forced to false for edge builds in define-env.ts (isEdgeServer ? false : flagValue), otherwise webpack will try to resolve node:stream etc. and fail.

`app-page.ts` Template Gotchas

app-page.ts is a build template compiled by the user's bundler. Any require() in this file is traced by webpack/turbopack at next build time. You cannot require internal modules with relative paths because they won't be resolvable from the user's project. Instead, export new helpers from entry-base.ts and access them via entryBase.* in the template.
Template helpers should stay out of RenderResult. If app-page.ts needs a Node-stream-only utility, prefer a small dedicated helper module in server/stream-utils/ (with DCE-safe if/else + require()).

Verification

Validate edge bundling regressions with pnpm test-start-webpack test/e2e/app-dir/app/standalone.test.ts
For module-resolution/build-graph fixes, verify without NEXT_SKIP_ISOLATE=1

$flags - flag wiring (config/schema/define-env/runtime env)
$react-vendoring - entry-base boundaries and vendored React
$runtime-debug - reproduction and verification workflow

Files

Just SKILL.md in .agents/skills/dce-edge of vercel/next.js.

Open the folder on GitHubat commit a32ddfd

Compare with similar skills

Dce Edge next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Dce Edge compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Dce Edge this skillvercel/next.js	143k	—	~1k	Automated safety check: Pass	MIT	today
AWS Serverless Edazxkane/aws-skills	367	4 repos	~3.2k	Automated safety check: Pass	MIT	3 mo ago
Qstash JSupstash/qstash-js	269	1 repos	~746	Automated safety check: Pass	MIT	2 days ago
Sokra Modemodule-federation/core	2.7k	—	~2.2k	Automated safety check: Pass	MIT	today
AWS Lambda Durable Functionsawslabs/agent-plugins	915	—	~2.3k	Automated safety check: Pass	Apache-2.0	3 days ago
Twelve Factorcitypaul/.dotfiles	739	—	~4.4k	Automated safety check: Notes	Custom licence	6 days ago

Similar skills

AWS Serverless Eda
zxkane/aws-skills
AWS serverless and event-driven architecture expert based on Well-Architected Framework.
367 GitHub starsUsed in 4 repos~3.2k tokens
Backend & APIsAuto-check passed
Qstash JS
upstash/qstash-js
Official
Work with the QStash JavaScript/TypeScript SDK for serverless messaging, scheduling.
269 GitHub starsUsed in 1 repo~746 tokens
Backend & APIsAuto-check passed
Sokra Mode
module-federation/core
Design, build, and maintain module-federation/core the way sokra (Tobias Koppers) built webpack 5: plugin architecture, container/sharing, runtime, caching, and reviews.
2.7k GitHub stars~2.2k tokensUpdated today
Backend & APIsAuto-check passed
AWS Lambda Durable Functions
awslabs/agent-plugins
Official
Build resilient, long-running, multi-step applications with AWS Lambda durable functions with automatic state persistence, retry logic, and orchestration for long-running executions.
915 GitHub stars~2.3k tokensUpdated 3 days ago
Backend & APIsAuto-check passed
Twelve Factor
citypaul/.dotfiles
Twelve-Factor App patterns for software-as-a-service and long-running process applications.
739 GitHub stars~4.4k tokensUpdated 6 days ago
Backend & APIsAuto-check: notes
AWS Lambda Typescript Integration
giuseppe-trisciuoglio/developer-kit
Provides AWS Lambda integration patterns for TypeScript with cold start optimization.
355 GitHub stars~2.9k tokensUpdated 28 days ago
Backend & APIsAuto-check: notes

Questions about Dce Edge

What does Dce Edge do?

DCE-safe require() patterns and edge runtime constraints. An agent skill from vercel/next.js. js, published by the product's own GitHub organization. DCE-safe require() patterns and edge runtime constraints.

When should I use Dce Edge?

Dce Edge fits situations like: writing conditional require() calls; guarding Node-only imports (node:stream etc.); editing define-env-plugin.ts / app-render / stream-utils for edge builds.

How do I install Dce Edge in Claude Code?

Run `npx skills add vercel/next.js --skill dce-edge -a claude-code`. Or copy the skill folder (.agents/skills/dce-edge in vercel/next.js) into .claude/skills/dce-edge in your project. Claude Code loads it when a task matches its description.

How do I install Dce Edge in Codex?

Run `npx skills add vercel/next.js --skill dce-edge -a codex`. Or copy the skill folder (.agents/skills/dce-edge in vercel/next.js) into .agents/skills/dce-edge in your project. Codex loads it when a task matches its description.

Can I use Dce Edge in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add vercel/next.js --skill dce-edge -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/dce-edge, .gemini/skills/dce-edge, .github/skills/dce-edge and .opencode/skills/dce-edge in your project.

What does Dce Edge need to run?

Going by SKILL.md and its folder, Dce Edge needs the command-line tools its instructions call (pnpm). Our summary lists: Node.js.

Does Dce Edge access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Dce Edge safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Dce Edge use?

Dce Edge is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Dce Edge use?

About 1k tokens (SKILL.md is roughly 4.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Dce Edge?

Skills that share tags, products or a category with Dce Edge: AWS Serverless Eda (zxkane/aws-skills, 367 stars), Qstash JS (upstash/qstash-js, 269 stars), Sokra Mode (module-federation/core, 2.7k stars) and AWS Lambda Durable Functions (awslabs/agent-plugins, 915 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Dce Edge?

vercel (a GitHub organization, an official publisher) maintains it in vercel/next.js, which has 143,241 GitHub stars. The repository holds 27 skills in this directory. The repository was last updated on October 8, 2026.

Source: vercel/next.js on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Dce Edge

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

DCE + Edge

DCE-Safe require() Pattern

TypeScript + DCE Interaction

Compile-Time Switcher Pattern

NEXT_RUNTIME Is Not a Feature Flag

Edge Runtime Constraints

app-page.ts Template Gotchas

Verification

Related Skills

Files

Compare with similar skills

Similar skills

More from vercel/next.js

Related

Questions about Dce Edge

DCE-Safe `require()` Pattern

`NEXT_RUNTIME` Is Not a Feature Flag

`app-page.ts` Template Gotchas