ship

Guides AI agents through planning, building, testing, and deploying Ethereum dApps end to end.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI agents and developers often jump straight into writing Solidity without an architecture plan, over-engineer contracts, pick the wrong chain, or skip security and QA — leading to rewrites, vulnerabilities, and failed launches. This Skill provides a phased, opinionated workflow that routes you from dApp idea to deployed production app. ## Core Features & Use Cases - Architecture Planning (Phase 0): CROPS gate (Censorship Resistance, Open Source, Privacy, Security), onchain vs offchain litmus test, MVP contract count guidance, state transition audits, and chain selection across mainnet, Base, Arbitrum, Optimism, and ZK chains. - dApp Archetype Templates: Predefined contract architectures for token launches, NFT collections, marketplaces, lending/vaults, DAOs, and AI agent services, each with common mistakes and fetch sequences. - Phased Build Pipeline: Step-by-step guidance for writing contracts with OpenZeppelin, testing with Foundry (unit, fuzz, fork), auditing with a fresh agent, building frontends with Scaffold-ETH 2, and shipping to IPFS or Vercel. - Use Case: You want to launch a prediction market. The Skill tells you it needs 1-2 contracts (market + resolution oracle), routes you through security and testing skills, and walks you through deployment, multisig ownership transfer, and post-launch monitoring. ## Quick Start Ask the agent to plan and ship your dApp idea, starting with the architecture phase before writing any Solidity code.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I plan a dApp architecture before writing Solidity?▼

Start with the onchain litmus test: put ownership, trustless exchange, composability, and permanent commitments onchain, and keep profiles, search, and media offchain. Then run a state transition audit for every function, asking who calls it and why.

How many smart contracts does a dApp MVP need?▼

Most dApps need 0-2 contracts. A token or NFT launch needs one, a marketplace using existing DEX liquidity may need zero, and a DAO needs at most three. More than three contracts for an MVP indicates over-engineering.

Should I deploy my dApp on Ethereum mainnet or an L2?▼

Mainnet is cheaper than commonly assumed (~$0.004 per transfer) and offers maximum decentralization and composability. Choose an L2 only when its specific strength fits your app, such as Base for consumer onboarding or Arbitrum for DeFi liquidity.

What testing should I run before deploying smart contracts?▼

Use Foundry for unit tests on custom functions, fuzz tests on all math operations, and fork tests for external protocol integrations. Run Slither for static analysis, then have a separate agent perform a security audit before deployment.

What are common dApp development anti-patterns to avoid?▼

Avoid kitchen-sink contracts, unnecessary factories, storing everything onchain, admin-key dependencies, premature multi-chain deployment, and rewriting audited primitives like ERC-20 instead of using OpenZeppelin. Also budget significant time for frontend quality.