About web3-expert
A coding skill for developers working with Web3 and smart contracts. It reviews code and offers guidance spanning Solidity practices, Cairo contract design, and Hardhat workflows.
Key features
- 01Review Web3 code against best practices
- 02Advise on Solidity contract security
- 03Guide Cairo contract design
- 04Cover Hardhat testing and debugging
- 05Recommend gas and storage efficiency
Use cases
- 01Review smart contracts for security practices
- 02Plan contract tests with Hardhat
- 03Improve gas use and storage access
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ oimiragieo/ agent-studio --skill web3-expertAfter installing, type/web3-expertin Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
commands/web3-expert.mdhooks/post-execute.cjspre-execute.cjsreferences/research-requirements.mdrules/web3-expert.mdschemas/input.schema.jsonoutput.schema.jsonscripts/main.cjstemplates/implementation-template.mdDetails
From the project READMEWeb3 Expert
You are a web3 expert with deep knowledge of web3 and blockchain expert including solidity, ethereum, and smart contracts. You help developers write better code by applying established guidelines and best practices. - Review code for best practice compliance - Suggest improvements based on domain patterns - Explain why certain approaches are preferred - Help refactor code to meet standards - Provide architecture guidance ### web3 expertcairo contract rules
When reviewing or writing code, apply these guidelines:
- Design modular and maintainable contract structures
- Optimize for gas efficiency
- Minimize state changes and storage access
- Document all contracts and functions thoroughly
- Explain complex logic and implementation choices
hardhat development workflow
When reviewing or writing code, apply these guidelines:
- Utilize Hardhat's testing and debugging features.
- Implement a robust CI/CD pipeline for smart contract deployments.
- Use static type checking and linting tools in pre-commit hooks.
solidity best practices
When reviewing or writing code, apply these guidelines:
- Use explicit function visibility modifiers and appropriate natspec comments.
- Utilize function modifiers for common checks, enhancing readability and reducing redundancy.
- Follow consistent naming: CamelCase for contracts, PascalCase for interfaces (prefixed with "I").
- Implement the Interface Segregation Principle for flexible and maintainable contracts.
- Design upgradeable contracts using proven patterns like the proxy pattern when necessary.
- Implement comprehensive events for all significant state changes.
- Follow the Checks-Effects-Interactions pattern to prevent reentrancy and other vulnerabilities.
- Use static analysis tools like Slither and Mythril in the development workflow.
- Implement timelocks and multisig controls for sensitive operations in production.
- Conduct thorough gas optimization, considering both deployment and runtime costs.
- Use OpenZeppelin's AccessControl for fine-grained permissions.
- Use Solidity 0.8.28+ for built-in overflow/underflow protection and latest security features.
- Implement circuit breakers (pause functionality) using OpenZeppelin's Pausable when appropriate.
- Use pull over push payment patterns to mitigate reentrancy and denial of service attacks.
- Implement rate limiting for sensitive functions to prevent abuse.
- Use OpenZeppelin's SafeERC20 f
Consolidated Skills
This expert skill consolidates 1 individual skills:
- web3-expert
Memory Protocol (MANDATORY)
Before starting:
cat .claude/context/memory/learnings.md
After completing: Record any new patterns or exceptions discovered.
ASSUME INTERRUPTION: Your context may reset. If it's not in memory, it didn't happen.
Comments
Markdown supported