ship

Guide dApp teams from concept to deployed production applications.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/mashharuki/flare-sample --skill ship-mashharuki
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/mashharuki/flare-sample/tree/main/.claude/skills/eth-ship
Command: npx skills add https://github.com/mashharuki/flare-sample --skill ship-mashharuki

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps teams avoid common dApp development failures by forcing deliberate architecture, minimizing onchain surface area, and ensuring every state transition has an accountable caller and incentive. It prevents premature coding, over-engineering, and forgotten operational steps (testing, audits, multisig transfers, and monitoring).

Core Features & Use Cases

  • Architecture planning: Onchain litmus test, contract count guidance, and state transition audits to decide what must be onchain versus offchain.
  • Chain selection & deployment strategy: Comparative guidance for mainnet and L2 choices based on your app's superpower and cost profile.
  • Build, test, and ship playbooks: Phased workflow covering contract building with OpenZeppelin, unit/fuzz/fork testing, security audits, frontend shipping, multisig deployment, and post-launch monitoring.
  • Anti-patterns and checklist: Common pitfalls, QA checklist, and routing to specialist skills (security, gas, indexing) for deeper work.

Quick Start

Ask the ship skill to design an MVP dApp: identify what must be onchain, recommend contract count and chain, and provide testing and deployment steps.

Frequently Asked Questions about ship

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

FAQPage Schema
How do I plan dApp architecture and decide what needs to be onchain?

Ship provides an onchain litmus test and state transition audits to decide what must be onchain versus offchain. It recommends minimizing onchain surface area while ensuring every state transition has an accountable caller and incentive.

What is the best way to choose an EVM chain for deploying a production dApp?

Chain selection involves comparing mainnet and Layer 2 options based on your application's specific superpower and cost profile. Ship provides comparative guidance to align deployment strategy with your project's operational requirements.

How do I deploy smart contracts to production with OpenZeppelin and a multisig?

Deploying smart contracts securely requires a phased workflow covering contract building with OpenZeppelin, security audits, and multisig deployment. This approach ensures proper access control and secure production release.

What testing checklists are needed before deploying Web3 smart contracts?

Testing smart contracts requires unit, fuzz, and fork testing phases alongside a comprehensive QA checklist. This prevents forgotten operational steps and ensures contract logic holds up under edge-case scenarios before deployment.

When should I avoid over-engineering my Web3 application architecture?

You should avoid over-engineering Web3 architecture when it leads to unnecessary onchain surface area or premature coding. Forcing deliberate architecture prevents bloated contracts and ensures state transitions remain accountable.

Does this dApp development workflow support integration with indexing tools?

Yes, the dApp development workflow supports integration with indexing tools and routes to specialist skills for deeper work. It includes post-launch monitoring and integration advice for multisigs and OpenZeppelin.