Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →austintgriffith/frontend-playbook
The complete build-to-production pipeline for Ethereum dApps. Fork mode setup, IPFS deployment, Vercel config, ENS subdomain setup, and the full production checklist. Built around Scaffold-ETH 2 but applicable to any Ethereum frontend project.
Passed 22 of 22 test cases with the skill, and 11 of 22 without it.
and 12 more in the full report
11 fixed11 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
When I open the root route of my static dApp on IPFS it loads fine, but navigating directly to subroutes like /debug results in 404 errors on IPFS gateways. What Next.js configuration option fixes this gateway resolution issue?
| Checked | Without skill | With skill |
|---|---|---|
| Instructs setting trailingSlash: true in next.config.ts. | Missed | Passed |
The instructions your model reads when the skill loads.
"I'll use yarn chain." Wrong. yarn chain gives you an empty local chain with no protocols, no tokens, no state. yarn fork --network base gives you a copy of real Base with Uniswap, Aave, USDC, real whale balances — everything (verified addresses: addresses/SKILL.md). Always fork.
"I deployed to IPFS and it works." Did the CID change? If not, you deployed stale output. Did routes work? Without trailingSlash: true, every route except / returns 404. Did you check the OG image? Without NEXT_PUBLIC_PRODUCTION_URL, it points to localhost:3000.
"I'll set up the project manually." Don't. npx create-eth@latest handles everything — Foundry, Next.js, RainbowKit, scaffold hooks. Never run forge init or create Next.js projects from scratch.
yarn chain (WRONG) yarn fork --network base (CORRECT)
└─ Empty local chain └─ Fork of real Base mainnet
└─ No protocols └─ Uniswap, Aave, etc. available
└─ No tokens └─ Real USDC, WETH exist
└─ Testing in isolation └─ Test against REAL state
npx create-eth@latest # Select: foundry, target chain, name
cd <project-name>
yarn install
yarn fork --network base # Terminal 1: fork of real Base
yarn deploy # Terminal 2: deploy contracts to fork
yarn start # Terminal 3: Next.js frontend
When using fork mode, the frontend target network MUST be chains.foundry (chain ID 31337), NOT the chain you're forking.
The fork runs locally on Anvil with chain ID 31337. Even if you're forking Base:
test cases passed, vs 11 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.