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.