Menu

Individual skill

solidity-patterns

Core Solidity design patterns for safe, maintainable smart contracts. Use when writing new contracts, reviewing architecture, or refactoring existing protocol code. Covers checks-effects-interactions, pull-over-push, guard checks, state machines, access restriction, and commit-reveal.

skills/solidity-patterns/SKILL.md

Read pinned source

Source commit a53141f10a1bbf9c634e44af6bc5a29dd1660697

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 7, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
132
Repository last updated
Oct 23, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Solidity Design Patterns

## Checks-Effects-Interactions (CEI)

The most critical pattern in Solidity. All functions that interact with external contracts must follow this order:

1. **Checks** — validate inputs and preconditions
2. **Effects** — update state
3. **Interactions** — call external contracts

```solidity
function withdraw(uint256 amount) external {
    // CHECKS
    if (amount == 0) revert ZeroAmount();