orchestration

Orchestrate Scaffold-ETH 2 dApp lifecycle from contracts to production deployment.

7|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/Zodomo/DrandVerifier --skill orchestration-zodomo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orchestration
Source: https://github.com/Zodomo/DrandVerifier/tree/main/.opencode/skills/ethskills/orchestration
Command: npx skills add https://github.com/Zodomo/DrandVerifier --skill orchestration-zodomo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents teams from wasting time on generic, wrong approaches to building Ethereum dApps by enforcing the Scaffold-ETH 2 three-phase workflow and validation gates.

Core Features & Use Cases

  • Three-phase build system with validation gates: Contracts → Frontend → Production, with explicit Phase 1, Phase 2, and Phase 3 checks.
  • Correct Scaffold-ETH 2 patterns: Guidance to rely on auto-generated deployment artifacts and scaffold hooks rather than raw wagmi, and to place external contracts before building the frontend.
  • Production-ready operational safety: Guardrails for key safety (no secrets committed), wallet behavior, and deploy checklists for IPFS/Vercel.

Quick Start

Ask an AI agent to follow the Skill’s three phases to fork a real chain locally, deploy contracts, build the frontend using scaffold hooks, and finally deploy the production frontend after completing the Phase 2 and Phase 3 validation steps.

Frequently Asked Questions about orchestration

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

FAQPage Schema
How do I build and ship an Ethereum dApp end-to-end?

Building an Ethereum dApp end-to-end requires orchestrating contract deployment, frontend integration, and production deployment across three validation phases to ensure correct scaffold hooks and operational safety.

How does Scaffold-ETH 2 frontend integration work with wagmi?

Scaffold-ETH 2 frontend integration relies on auto-generated deployment artifacts and scaffold hooks instead of raw wagmi, ensuring your frontend correctly interacts with deployed contracts and external protocol state.

What is the best way to deploy a dApp to IPFS and Vercel?

The best way to deploy a dApp to IPFS and Vercel is to complete the phase three validation checklist, ensuring no secrets are committed, correct wallet behavior is verified, and production frontend assets are properly prepared.

Can I use external protocol state when building on a local chain fork?

Yes, you can use real protocol state when building on a local chain fork, and you must correctly place external contracts before building the frontend to ensure proper interaction within the Scaffold-ETH 2 environment.

Why does my dApp deployment require validation gates between phases?

Validation gates are required between phases to prevent teams from using wrong approaches, enforcing correct credential-safety practices, external contract placement, and scaffold hook usage before moving to frontend and production.