Solidity Coding
[AUTO-INVOKE] MUST be invoked BEFORE writing or modifying any Solidity contract (.sol files). Covers pragma version, naming conventions, project layout, OpenZeppelin library selection standards, Chainlink integration, and anti-patterns. Trigger: any task involving creating, editing, or reviewing .sol source files.
Install
npx skills add NeverSight/learn-skills.dev --skill solidity-codinggit clone --depth 1 https://github.com/NeverSight/learn-skills.dev.git /tmp/learn-skills.dev
mkdir -p ~/.claude/skills
cp -r /tmp/learn-skills.dev/data/skills-md/0xlayerghost/solidity-agent-kit/solidity-coding ~/.claude/skills/solidity-codingPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Solidity Coding Standards ## Language Rule - **Always respond in the same language the user is using.** If the user asks in Chinese, respond in Chinese. If in English, respond in English. ## Coding Principles - **Pragma**: Use `pragma solidity ^0.8.20;` — keep consistent across all files in the project - **Dependencies**: OpenZeppelin Contracts 4.9.x, manage imports via `remappings.txt` - **Error Handling**: Prefer custom errors over `require` strings — saves gas and is more expressive - Define: `error InsufficientBalance(uint256 available, uint256 required);` - Use: `if (balance < amount) revert InsufficientBalance(balance, amount);` - **Documentation**: All `public` / `external` functions must have NatSpec (`@notice`, `@param`, `@return`) - **Event Indexing**: Only add `indexed` to `address` type parameters — add comment if indexing other types - **Special Keywords**: `immutable` / `constant` / `unchecked` / `assembly` must have inline comment explaining why ## Naming Conventions | Element | Convention | Example | |---------|-----------|---------| | Contract / Library | PascalCase | `MyToken`, `StakingPool` | | Interface | `I` + PascalCase | `IMyToken`, `IStakingPool` | | State variable / Function | lowerCamelCase | `totalSupply`, `claimDividend` | | Constant / Immutable | UPPER_SNAKE_CASE | `MAX_SUPPLY`, `ROUTER_ADDRESS` | | Event | PascalCase (past tense) | `TokenTransferred`, `PoolCreated` |
Details
- Skill name
solidity-coding- Repository
- NeverSight/learn-skills.dev
- Path
data/skills-md/0xlayerghost/solidity-agent-kit/solidity-coding/SKILL.md- Repo updated
- 18 November 2026
FAQ
What does the Solidity Coding skill do?
[AUTO-INVOKE] MUST be invoked BEFORE writing or modifying any Solidity contract (.sol files). Covers pragma version, naming conventions, project layout, OpenZeppelin library selection standards, Chainlink integration, and anti-patterns. Trigger: any task involving creating, editing, or reviewing .sol source files.
How do I install the Solidity Coding skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add NeverSight/learn-skills.dev --skill solidity-coding. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Solidity Coding popular?
It lives in NeverSight/learn-skills.dev, which has 223 GitHub stars and 42 forks.
Related skills
Council
223NeverSight/learn-skills.dev
Convene the Council of High Intelligence — multi-persona deliberation with historical thinkers for deeper analysis of complex problems.
Megaeth Developer
223NeverSight/learn-skills.dev
End-to-end MegaETH development playbook (Feb 2026). Covers wallet operations, token swaps (Kyber Network), eth_sendRawTransactionSync (EIP-7966) for instant receipts, JSON-RPC batching, real-time mini-block subscriptions, storage-aware contract patterns (Solady RedBlackTreeLib), MegaEVM gas model, WebSocket keepalive, bridging from Ethereum, and debugging with mega-evme. Use when building on MegaETH, managing wallets, sending transactions, or deploying contracts.
Openclaw Stock Skill
223NeverSight/learn-skills.dev
使用 data.diemeng.chat 提供的接口查询股票日线、分钟线、财务指标等数据,支持 A 股等市场。
Solidity Debug
223NeverSight/learn-skills.dev
[AUTO-INVOKE] MUST be invoked when debugging failed on-chain transactions. Covers transaction receipt analysis, gas diagnosis, calldata decoding, revert reason extraction, and state verification using cast. Trigger: any task involving failed tx analysis, revert debugging, or on-chain transaction troubleshooting.
Solidity Checklist
223NeverSight/learn-skills.dev
[AUTO-INVOKE] MUST be invoked BEFORE any on-chain operation (cast send, forge script --broadcast). Systematic 6-layer verification checklist: permissions, dependencies, parameters, security, testing, and knowledge capture. Trigger: any task involving sending transactions, deploying contracts, or interacting with on-chain state.
Solidity Security
223NeverSight/learn-skills.dev
[AUTO-INVOKE] MUST be invoked BEFORE writing or modifying any Solidity contract (.sol files). Covers private key handling, access control, reentrancy prevention, gas safety, and pre-audit checklists. Trigger: any task involving creating, editing, or reviewing .sol source files.
Browse the most popular Claude skills, all finance & crypto skills, or write your own with the skills generator.