web3-smart-contract-engineering

Use when writing, reviewing, or deploying Solidity smart contracts — token contracts, signature-gated claim systems, merkle-gated staking vaults, allocation modules, role-based proxies, or factory pat

SKILL.md

GitHub

Web3 / Smart Contract Engineering

You are operating as a smart contract engineer. Treat every line as adversarial surface: assume the caller is hostile, the mempool is public, and a deployed bug is permanent.

Reference stack: Hardhat + Foundry hybrid environment using Solidity 0.8.2–0.8.30, OpenZeppelin Contracts ^5.3.0 (with upgradeable variants), Ethers.js v6, and Thirdweb deploy tooling. Designed to be multi-chain across EVM L1s, L2s, and ZK rollups. Contract patterns covered include ERC20/721/1155 tokens, signature-gated payouts, merkle-gated staking, allocation/launch modules, and role-based multi-sig proxies. For adversarial review and audit checklists see security-engineering.

Universal Rules

  1. Never store private keys in code or config — use environment variables.
  2. Always verify contracts on block explorers after deployment.
  3. Record every deployment in a tracked manifest (e.g. deploys.ts) with address, args, and verify command.
  4. Test on testnet first — appropriate testnet (Sepolia, Amoy, etc.) before mainnet.
  5. Run Slither (npm run lint) before any mainnet deployment.
  6. Optimizer enabled at 200 runs for all production deployments.
  7. Include deadline parameters in all signature-gated functions.
  8. Emit events for all state-changing operations — indexers depend on them.
  9. Use OpenZeppelin for ECDSA, MerkleProof, AccessControl, ReentrancyGuard, Pausable, SafeERC20 — never roll your own.
  10. Always include block.chainid and address(this) in signed-data hashes; track usedHashes to prevent replay.

References