What problem does it solve?
Modern dApp frontends require careful coordination of wallet integration, server-side rendering, and on-chain interaction to avoid hydration mismatches, leaked secrets, duplicated RPC calls, and poor transaction UX. This Skill codifies production patterns for Next.js 16 app-router projects to wire wallet providers safely, perform cacheable server reads, and deliver resilient client-side signing and transaction flows.
Core Features & Use Cases
- SSR-safe wallet configuration: Guidance for cookie-based storage, per-request wagmi config, and initial state hydration to eliminate flicker.
- On-chain reads and multicall: Patterns for server-side viem public clients, multicall batching, and caching using Next.js cache directives.
- Transaction lifecycle and error handling: End-to-end UX states from signature through mining to receipt, typed error parsing, and explorer linking.
- Auth and sessions: SIWE flows, nonce management, smart-account verification, and secure sealed cookies for server session handling.
- Wallet UX and guards: ENS resolution, network guards, connect gates, capability detection, and account-change invalidation.
- ABI codegen and typing: Recommendations to use codegen for typed ABIs and address tables per chain to avoid silent runtime errors.
Quick Start
Use the web3-frontend skill to get step-by-step guidance for wiring wagmi and viem into a Next.js 16 app with cookie-based SSR storage and SIWE authentication.