with one click
construct-protocol
construct-protocol contains 10 collected skills from 0xHoneyJar, with repository-level occupation coverage and site-owned skill detail pages.
Skills in this repository
Decode, trace, and explain failed or complex transactions. Handles reverts, custom errors, Safe multisig payloads, multicalls, and nested calldata; explains what happened in plain language.
Ground dApp frontend assumptions in on-chain reality. Reads deployed smart contract state via `cast` and compares against hardcoded values in the frontend codebase to catch UI/contract drift.
Compare frontend ABI definitions against deployed contract reality. Finds inline ABIs, ABI files, and contract interface references; cross-checks each against on-chain state via `cast`; reports mismatches that cause silent failures or reverts.
Agent-Browser Web3 E2E testing — drives wallet flows in a real browser (or generates Playwright scripts), submits transactions against test environments only, and writes a report to grimoires/protocol/e2e-report.md.
Web3 frontend linter — scans for BigInt safety violations, wei handling errors, address checksum failures, timestamp confusion, and unsafe number coercions in dApp frontends.
Web3 test suite runner — runs the project's tests, diagnoses Web3-specific failures (BigInt, gas, reverts, nonce), audits coverage of contract interactions, and generates starter test scaffolding when missing.
Contract type verification — ensures TypeScript types in the frontend exactly match deployed smart contract ABIs by inspecting wagmi codegen, foundry/hardhat configs, and manual ABI imports.
Cross-model adversarial contract review — deep audit of every place the frontend touches contracts (parameter mismatches, error handling gaps, gas estimation, optimistic update races, BigInt safety) in Bridgebuilder format, written to grimoires/protocol/contract-review.md.
Identify proxy architecture, implementation, and upgrade authority. Reads EIP-1967 storage slots via `cast`, classifies proxy type (UUPS, Transparent, Beacon), and reports who controls upgrades with security implications.
Dry-run user flows to catch reverts before users hit them. Uses `cast call` and `cast estimate` to verify contract interactions will succeed, estimate gas costs, and compare simulated outcomes against frontend display.