orchestration

Plans, builds, and deploys Ethereum dApps through a three-phase Scaffold-ETH 2 workflow.

1|Updated Sep 4, 2025
One-click install
npx skills add https://github.com/FuzzysTodd/The-Nexus-Protocol-Token-DAO --skill orchestration-fuzzystodd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: orchestration
Source: https://github.com/FuzzysTodd/The-Nexus-Protocol-Token-DAO/tree/main/skills/orchestration
Command: npx skills add https://github.com/FuzzysTodd/The-Nexus-Protocol-Token-DAO --skill orchestration-fuzzystodd

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about orchestration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a full dApp with Scaffold-ETH 2?▼

Follow the three-phase system: scaffold contracts and UI on a local fork, deploy contracts to a live network while testing with a local UI, then publish the frontend to IPFS or Vercel. Each phase has validation gates that must pass before moving on.

Should I use Scaffold hooks or raw wagmi in SE2?▼

Use Scaffold hooks such as useScaffoldReadContract, useScaffoldWriteContract, and useScaffoldEventHistory instead of raw wagmi. They integrate with SE2's auto-generated contract typings and handle network and wallet state for you.

Why use yarn fork instead of yarn chain in Scaffold-ETH 2?▼

yarn fork gives you real onchain state — Uniswap, USDC, Aave, and whale balances already deployed — while yarn chain starts an empty chain. Forking avoids writing unnecessary mock contracts for protocols that already exist.

How do I prevent API keys from being committed in an SE2 project?▼

Never paste keys into scaffold.config.ts rpcOverrides or alchemyApiKey; use environment variables from .env.local instead. Run grep checks for hex private keys and Alchemy or Infura URLs before every commit, and keep .env in .gitignore.

Can I deploy a Scaffold-ETH 2 frontend to IPFS?▼

Yes, run yarn ipfs to publish via BGIPFS, which is built into SE2 with no setup. Note that IPFS only supports static content, so server-side rendering, API endpoints, and functions will not work.

What should I do when a bug appears in production?▼

Follow the phase transition rules: a Phase 3 bug means returning to Phase 2 with local UI against production contracts, and a contract bug means returning to Phase 1 to fix locally, add a regression test, and redeploy. Never hack around bugs in production.