What problem does it solve? Building a full Ethereum dApp involves contracts, frontend, and deployment steps that are easy to get wrong — editing auto-generated files, using raw wagmi instead of Scaffold hooks, leaking API keys, or skipping verification. This Skill enforces the correct Scaffold-ETH 2 patterns and a gated three-phase build process. ## Core Features & Use Cases - Three-Phase Build System: Phase 1 scaffolds contracts and UI on a local fork, Phase 2 deploys contracts to a live network with a local UI, and Phase 3 ships the frontend to IPFS or Vercel with a production QA checklist. - SE2 Pattern Enforcement: Mandates Scaffold hooks (useScaffoldReadContract, useScaffoldWriteContract, useScaffoldEventHistory), the three-button approve/execute flow, and forbids editing auto-generated deployedContracts.ts. - Secret Leak Prevention: Provides grep-based checks and .gitignore rules to stop private keys, Alchemy/Infura API keys, and RPC URLs from being committed to Git. - Use Case: Ask an agent to build a token swap dApp on Base — it forks the chain, writes and tests contracts, wires the frontend with Scaffold hooks, deploys and verifies on mainnet, then publishes to IPFS. ## Quick Start Use the orchestration skill to plan and build my Scaffold-ETH 2 dApp from contracts through frontend to production deployment.