skills.rest
idchain-world
idchain-worldOFFICIAL
Explore all skills by this author →
WebsiteGitHub

solidity-style-modern

Enforce modern Solidity style for 0.8.20+ projects.

16|4|Updated Mar 22, 2026
Search Tags:#security#style#best-practices#solidity#pragma#natspec
One-click install
npx skills add https://github.com/idchain-world/id-agents --skill solidity-style-modern
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: solidity-style-modern
Source: https://github.com/idchain-world/id-agents/tree/main/configs/agents/foundry-dev/skills/solidity-style-modern
Command: npx skills add https://github.com/idchain-world/id-agents --skill solidity-style-modern

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Solidity projects often suffer from inconsistent style and overlooked best practices, leading to harder audits and avoidable bugs. This Skill codifies a modern set of conventions and checks to ensure code meets engineering standards across a codebase.

Core Features & Use Cases

  • Pinned compiler version and explicit SPDX headers to avoid drift and licensing confusion.
  • Enforcement of modern patterns: custom errors over string-based requires, Checks-Effects-Interactions, NatSpec on external surfaces, and disciplined naming and storage layout.
  • Use Case: Teams adopting a shared Solidity style guide across contracts and audits.

Quick Start

Review your Solidity files and update them to pin the compiler version, add SPDX headers, replace legacy require strings with custom errors, apply Checks-Effects-Interactions, and add NatSpec on public surfaces.

Frequently Asked Questions about solidity-style-modern

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce modern Solidity style and safe patterns in my codebase?▼

To enforce modern Solidity style, apply pinned compiler versions, explicit SPDX headers, custom errors, Checks-Effects-Interactions, and NatSpec to improve consistency, safety, and auditability across 0.8.20+ projects.

What is the best way to replace legacy require strings in Solidity 0.8.20+?▼

The best way to replace legacy require strings in Solidity is by using custom errors, which reduces gas costs and aligns with modern best practices for safer and more auditable smart contracts.

Why should I pin the Solidity compiler version and add SPDX headers?▼

Pinning the Solidity compiler version prevents unexpected breaking changes from compiler drift, while explicit SPDX headers avoid licensing confusion and ensure your project meets modern engineering standards.

How do I apply Checks-Effects-Interactions and NatSpec to Solidity contracts?▼

Apply Checks-Effects-Interactions by ordering state changes before external calls to prevent reentrancy, and add NatSpec documentation to all public surfaces to ensure your Solidity code is auditable and safe.

Does this Solidity style enforcement work for 0.8.20+ projects?▼

Yes, this Solidity style enforcement is explicitly designed for 0.8.20+ projects, targeting modern compiler features to ensure your codebase maintains safe patterns and high auditability.

What are the limitations of applying modern Solidity style conventions to existing code?▼

Applying modern Solidity style conventions to existing code requires updating pragma pins, SPDX headers, and storage layouts, which may demand significant refactoring for legacy contracts to meet current standards.

Related Skills

Explore More Software Engineering Skills→
0bkevin0bkevin

solidity-coding

Enforces Solidity coding standards including pragma, naming, layout, and OpenZeppelin usage for contracts.

Community
Advanced
hairyfhairyf
4

slither

Perform static analysis on Solidity and Vyper smart contracts to detect vulnerabilities.

Community
Intermediate
augustoheissaugustoheiss

agency-solidity-smart-contract-engineer

Design secure, gas-optimized Solidity smart contracts with Foundry testing and upgrade patterns.

Community
Advanced
knckknckknckknck

go-style-guide

Standardize Go code quality and style across projects.

Community
Intermediate