What problem does it solve?
Before writing or modifying any Solidity contract, developers need consistent standards to avoid pragma drift, naming inconsistencies, insecure patterns, and misconfigurations.
Core Features & Use Cases
- Enforce pragma version consistency (e.g., ^0.8.19) across all files and modules.
- Standardize project layout and file organization (src, test, scripts) to improve maintainability.
- Guide OpenZeppelin library selection and import practices to reduce risk.
- Establish coding conventions for documentation, error handling, events, and naming.
- Provide guardrails for oracle integration, upgradeability, and anti-patterns.
- Promote NatSpec usage and inline documentation for public/external functions.
- Document project structure and configuration management for Foundry/Remix workflows.
Use cases: a team kicks off a Solidity project and runs this skill to automatically validate the initial contract skeleton; a reviewer applies it to ensure new PRs adhere to standards; a maintainer uses it to audit and refactor existing contracts.
Quick Start
Invoke this skill before writing or editing any Solidity contract to enforce versioning, naming, layout, and security best practices.