ensnode

Run perf tests on the ENSIndexer (Ponder app under apps/ensindexer). Establishes a clean, reproducible baseline by disabling ENSRainbow healing on the hot path (DISABLE_ENSRAINBOW_HEAL), isolating the schema, wiping prometheus between runs, and snapshotting per-handler metrics at realtime. Use when the user asks to compare branches/configs, build a perf baseline, or measure a plugin combination.

How the Ethereum Follow Protocol (EFP) works and how it surfaces in the ENS Omnigraph — the onchain social graph (lists, list records, tags), primary-list validation, block/mute follower semantics, and the `Query.efp` / `Account.efp` fields for reading follows, followers, and following. Read this before querying or displaying EFP follow data.

Query ENS data (names, addresses, records, primary names, ownership, registrations, subnames, resolvers) via the ENS Omnigraph — a single GraphQL API that unifies ENSv1 and ENSv2 across all chains. Use whenever a task needs to read ENS state, instead of querying chains/the subgraph from first principles.

Inspect and surgically edit Ponder's RPC sync cache (the `ponder_sync` Postgres schema): understand what's cached, diagnose stale/contaminated cache (e.g. a restarted ens-test-env devnet reusing chain id 31337), and clip/purge a block range so Ponder re-fetches it cleanly without re-syncing the whole chain. Use when a handler throws RecordNotFoundError on an entity that should exist, when cached block hashes diverge from the live chain, or when splicing one chain's sync data into another (upstream chain → a fork of it).

Fix security vulnerabilities found by pnpm audit using a git worktree off of `main`. Also use to maintain `pnpm.overrides` hygiene: prune overrides that are no longer necessary and scope overrides so they don't rewrite peerDependency ranges.

How the ENS protocol works at a conceptual level — names and the nametree, normalization, namehash/labelhash, the registry/resolver/registrar architecture, forward & reverse resolution, primary names, records (addresses/text/contenthash), name ownership (NFTs, the NameWrapper), and ENS across many chains (L2 subdomains, DNS-imported names, CCIP-Read). Read this for protocol fundamentals before querying, displaying, or integrating ENS.

Build ENS React UIs with enskit — set up the OmnigraphProvider, run typed ENS Omnigraph queries with useOmnigraphQuery (gql.tada documents, loading/error states, union/connection handling), get a normalized urql cache for free, paginate Relay connections, and render beautified names. Use when wiring ENS data into a React app.

Integrate ENS into JavaScript/TypeScript apps with enssdk — a fully-typed ENS Omnigraph client (typed GraphQL via gql.tada) plus the easy-to-get-wrong primitives (namehash/labelhash, ENSIP-15 normalization, name interpretation/beautification, branded Name/Label/Address types). Use when writing TS/JS that reads ENS data or manipulates ENS names.

Shared working conventions every ENS skill assumes — prefer the ENS Omnigraph for reads, use enssdk for the easy-to-get-wrong primitives, prefer `Node` over "namehash" in user-facing communication, follow the ENSNode terminology reference, and report results without leaking internal procedure. Foundational dependency of every other ENS skill.

Drive the enscli command-line tool to read ENS data — run ENS Omnigraph GraphQL queries, explore the schema offline, compute namehash/labelhash, heal labels via ENSRainbow, and check ENSNode indexing status. Use this when executing ENS lookups from a shell (the omnigraph skill authors queries; this skill runs them).

Guide for migrating an app from the legacy ENS Subgraph API to the ENS Omnigraph (rewriting queries, flattening connections, offset→cursor pagination). Coming soon.

Guide for querying live ENS state via SQL over ENSDb (ENS Unigraph) for question shapes the ENS Omnigraph GraphQL API doesn't express. Coming soon — prefer the omnigraph skill first; escalate to SQL only when needed.