ENS for Developers

This skill guides ENS integration work. It covers two modes:

• Greenfield — adding ENS to an app for the first time.
• Audit — checking an existing integration is correct against current ENS best practices (ENSv2-ready, normalization, multichain, L2 primary, CCIP-Read).

Most apps (~99%) only need Scenario 1. Bigger surface areas — custom records, subnames, contract naming, querying at scale, library implementation, AI-agent identity — are organized as scenarios below and detailed in references/.

Scope and source of truth

• Source of truth: docs.ens.domains. When in doubt or addresses/specs may have moved, check there.
• Stack: principles are stack-agnostic; concrete code defaults to viem ≥ 2.35 + wagmi, with notes for ethers v6.
• Out of scope: any specific naming product or registrar SDK. Pure protocol + canonical libraries only.

The five rules that apply to every ENS integration

These show up in every scenario. If a single one is missing, the integration is wrong even if it appears to work.