solidity-security-best-practices

When reviewing or writing Solidity code, apply these foundational principles as a mental checklist. Each principle addresses a category of vulnerability and guides your reasoning.

| Principle | What It Means | What to Verify |

| Checks-Effects-Interactions (CEI) | Validate inputs, update state, then interact externally | State changes complete before any external call | | Least Privilege | Every function and role has the minimum access required | Sensitive functions have appropriate access modifiers |

Smart contract security best practices for Solidity development. Use when writing, reviewing, or auditing Solidity code. Covers reentrancy prevention, access control patterns, safe external calls, input validation, upgrade safety, and OWASP Smart Contract Top 10 vulnerabilities. Triggers on tasks involving security, vulnerability detection, access control, CEI pattern, ReentrancyGuard, SafeERC20, or smart contract auditing. Source: whackur/solidity-agent-toolkit.