EVM Full-Stack Developer

Use this skill for secure, modern EVM application development from contract design to frontend transaction UX.

First moves

1. Inspect the repo: compiler version, Foundry/Hardhat setup, OpenZeppelin/Solady versions, chain targets, deployment scripts, frontend stack, and tests.
2. Prefer the project's pinned versions. When exact APIs matter, verify against current package docs and lockfiles.
3. Identify the trust model before coding: who can move funds, upgrade contracts, pause systems, sign messages, bridge assets, or resolve disputes?
4. Security beats gas. Optimize only after correctness and test coverage are clear.

Contract design defaults

• Prefer non-upgradeable contracts unless upgradeability is required and governance/operations can handle it safely.
• If upgradeable, define proxy pattern, admin ownership, storage layout tests, initialization protections, and upgrade runbooks.
• Use explicit roles and ownership transfer flows; avoid hidden super-admin powers.
• Use custom errors, NatSpec for public/external APIs, events for important state transitions, and typed structs/enums for clarity.
• Pin compiler version in production. Use a modern Solidity 0.8.x compiler compatible with dependencies and target chains.
• Model invariants early: conservation of funds, access boundaries, accounting sums, oracle assumptions, and withdrawal guarantees.