thecil/solidity-foundry-assistant

thecil/solidity-foundry-assistant icon

public

Published on 7/15/2025

Solidity Foundry Assistant

Rules

Models

Context

Models

Relace Instant Apply

relace

40kinput·32koutput

Claude 3.7 Sonnet

anthropic

200kinput·8.192koutput

Claude 3.5 Sonnet

anthropic

200kinput·8.192koutput

Codestral

mistral

voyage-code-3

voyage

Voyage AI rerank-2

voyage

Rules

solidity-foundry-rules

---
name: Solidity Foundry Rules
---
- Follow the Solidity best practices.
- Use the latest version of Solidity.
- Always import specific contracts from their respective libraries.
- Use OpenZeppelin libraries for common patterns like ERC20 or ERC721.
- Utilize Foundry for development and testing.
- Solidity and Foundry for contract testing.
- Use Alchemy for interacting with Ethereum networks.
- Use CamelCase for naming functions and variables in Solidity.
- Use named exports for JavaScript files related to smart contracts.
- Always write the functions or contract documentation based on NatSpect Format.
- DO NOT TEACH ME HOW TO SET UP THE PROJECT, JUMP STRAIGHT TO WRITING CONTRACTS AND CODE.

Docs

Foundryhttps://book.getfoundry.sh/

Solidity Docshttps://docs.soliditylang.org/en/v0.8.30/

OpenZeppelin Docshttps://docs.openzeppelin.com/contracts/5.x/

ChainLink Docshttps://docs.chain.link/

Natspec Format Docshttps://docs.soliditylang.org/en/latest/natspec-format.html

Prompts

No Prompts configured

Context

@diff

Reference all of the changes you've made to your current branch

@codebase

Reference the most relevant snippets from your codebase

@url

Reference the markdown converted contents of a given URL

@folder

Uses the same retrieval mechanism as @Codebase, but only on a single folder

@terminal

Reference the last command you ran in your IDE's terminal and its output

@code

Reference specific functions or classes from throughout your project

@file

Reference any file in your current workspace

Data

No Data configured

MCP Servers

No MCP Servers configured