What problem does it solve?
This Skill solves the confusion and recurring breakages that happen when moving an Ethereum dApp frontend from local dev into production, especially around fork-mode correctness, static export, IPFS routing, and deployment configuration.
Core Features & Use Cases
- Fork-mode setup that matches real chain conditions: Use a fork instead of an empty local chain so contracts, tokens, and protocol state behave like production.
- IPFS-first production build workflow: Build, clean stale artifacts, verify route outputs, and upload a fresh static site to IPFS to avoid CID staleness.
- Next.js static export pitfalls guide for dApps: Fix issues like missing localStorage APIs during prerender, ensure correct
trailingSlash, and validate OG metadata and ENS content routing.
- Vercel production deployment configuration: Configure a monorepo-friendly Vercel build without common root directory and install command mistakes.
Use case: You have an Ethereum frontend that works on your machine but returns 404s on IPFS after deploy; this Skill helps you rebuild correctly and verify that the exported routes, metadata, and domain/ENS links behave as users expect.
Quick Start
Follow the fork-mode setup steps, then run a clean IPFS production build and deployment checklist for your Next.js dApp in a Scaffold-ETH 2 style monorepo.