orchestration

Guides planning, building, and deploying Ethereum dApps through a three-phase Scaffold-ETH 2 workflow.

Updated Sep 9, 2026
One-click install
npx skills add https://github.com/m-faran/genie-markets --skill orchestration-m-faran
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: orchestration
Source: https://github.com/m-faran/genie-markets/tree/main/.agent/skills/ethskills/orchestration
Command: npx skills add https://github.com/m-faran/genie-markets --skill orchestration-m-faran

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Building a full Ethereum dApp involves many failure-prone steps: contract deployment, frontend wiring, secret management, and production release. This Skill gives an AI agent a structured three-phase build system for Scaffold-ETH 2 projects so nothing is skipped, misconfigured, or leaked. ## 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. - Scaffold-ETH 2 Conventions: Enforces correct patterns such as using scaffold hooks instead of raw wagmi, never editing the auto-generated deployedContracts.ts, and registering external contracts before frontend work. - Secret Leak Prevention: Provides concrete grep 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, deploys and tests contracts, wires the frontend with the three-button approve/execute flow, verifies contracts on the explorer, and deploys the static frontend 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 and deploy a full Ethereum dApp with Scaffold-ETH 2?▼

Follow the three-phase system: build contracts and UI on a local fork in Phase 1, deploy contracts to a live network with a local UI in Phase 2, then ship the frontend to IPFS or Vercel in Phase 3. Each phase has validation gates that must pass before moving on.

Should I use yarn fork or yarn chain for local Ethereum development?▼

Use yarn fork. It does everything yarn chain does plus gives you real protocol state like Uniswap, USDC, and whale balances, so you avoid writing unnecessary mock contracts for protocols that already exist onchain.

How do I prevent API keys and private keys from leaking in a Scaffold-ETH 2 repo?▼

Keep all secrets in .env files covered by .gitignore and never paste keys into scaffold.config.ts, since rpcOverrides and alchemyApiKey there are committed to Git. Run the provided grep checks for hex keys and Alchemy or Infura URLs before every commit.

Can I edit deployedContracts.ts in a Scaffold-ETH 2 project?▼

No, deployedContracts.ts is auto-generated by the deployment process and must not be edited manually. External contracts you interact with belong in externalContracts.ts, which should be populated before building the frontend.

What are the limitations of deploying a dApp frontend to IPFS?▼

IPFS hosting only supports static content, so server-side rendering, API endpoints, and server functions will not work. If your app needs those, deploy to Vercel instead using yarn vercel.