solidity-development

Apply Solidity security, gas-optimization, and NatSpec documentation standards to smart contracts.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/felixnorden/skills --skill solidity-development-felixnorden
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: solidity-development
Source: https://github.com/felixnorden/skills/tree/main/skills/solidity-development
Command: npx skills add https://github.com/felixnorden/skills --skill solidity-development-felixnorden

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The Solidity development skill centralizes production-grade security, gas optimization, and documentation best practices to streamline safe, efficient smart contract work.

Core Features & Use Cases

  • Security patterns and CEI guidance for robust contracts
  • Gas optimization and NatSpec documentation standards for audits
  • Upgradeability and testing workflows for maintainable deployments
  • Use Case: When building or auditing complex Solidity projects, apply these patterns to reduce risk and improve maintainability.

Quick Start

Apply the recommended Solidity security patterns, gas-optimization tips, and NatSpec guidance to a sample contract and iterate to produce an auditable, production-ready implementation.

Frequently Asked Questions about solidity-development

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

FAQPage Schema
What are the best security patterns for Solidity smart contracts?

Solidity gas optimization techniques include minimizing storage writes, optimizing variable packing, and avoiding redundant operations. These standards streamline safe, efficient smart contract work by reducing transaction costs while maintaining security across EVM-compatible chains.

How do I write NatSpec documentation for Ethereum contracts?

NatSpec documentation for Ethereum contracts involves adding structured comments to define function behavior and parameters. Meeting these documentation standards ensures clear code readability and fulfills audit requirements for production-ready Solidity implementations.

Can I use these patterns for auditing Solidity on any EVM-compatible chain?

Solidity upgradeability patterns involve using proxy contracts and proper storage layout management to maintain deployments without losing state. These workflows ensure maintainable deployments and robust contract upgrades while mitigating security risks during changes.

How do I apply Checks-Effects-Interactions (CEI) in Solidity development?

Applying Checks-Effects-Interactions (CEI) in Solidity development means structuring functions to validate conditions first, update state variables second, and interact with external contracts last. This pattern is critical for preventing reentrancy attacks during audits.