agentleFS
hiromailyhiromaily/go-crypto-wallet/.cursor/rules/apps/eth-contracts.mdc

go-crypto-wallet / apps

Cursor rule128 starsChanged 6 months agoMITView on GitHub

ETH Contracts Directory Rules

  • Reads credentials

We split this eth-contracts.mdc into the rules it gives an agent

6 rules. About 0 are common, 1 is distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use the solidity-development skill for all changes in this directory.

    line 14
  2. Very specific:

    Always: keep .env in .gitignore

    line 50
  3. Distinctive:

    Do not add custom access control, pausability, or upgradeability unless explicitly required

    line 51
  4. Very specific:

    Run npm install or yarn — use bun install

    line 68
  5. Very specific:

    Use truffle or hardhat — this project uses Foundry only

    line 69
  6. Very specific:

    Commit lib/, out/, node_modules/, or .env

    line 71

≈ “Common” is an estimate: at least 1 in 5 of the 6,350 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
eth-contracts.mdc
---
description: ETH Contracts Directory Rules
globs: ["apps/eth-contracts/**"]
alwaysApply: false
---


# ETH Contracts Directory Rules

Rules for working in `apps/eth-contracts/` — a standalone Foundry project for Ethereum smart contracts.

## Skill

Use the `solidity-development` skill for all changes in this directory.

## Toolchain

| Tool | Command | Notes |
|------|---------|-------|
| Compile | `forge build` | Artifacts go to `out/` |
| Test | `forge test -v` | All `*.t.sol` files in `test/` |
| Lint | `bun run lint` | solhint — must exit 0, zero errors |
| Format | `bun run fmt` | dprint — must exit 0 |
| Install deps | `bun install` | npm packages (`node_modules/`) |
| Install forge libs | `forge install foundry-rs/forge-std` | Foundry libs go to `lib/` |

> `forge` is at `~/.foundry/bin/forge` if not in PATH.

## Verification (required before commit)

```bash
cd apps/eth-contracts
forge build       # must succeed with zero errors
bun run lint      # must exit 0, zero solhint errors
forge test -v     # must pass with zero failures
```

## Solidity Conventions

- **Pragma**: `^0.8.34` (or latest stable)
- **Imports**: Named imports only — `import {ERC20} from "..."` (no global imports)
- **NatSpec**: Required on all contracts (`@title`, `@author`, `@notice`) and public/external functions (`@notice`, `@param`, `@return`)
- **Visibility**: Explicit on all functions; constructors exempt in Solidity ≥0.8
- **Dependencies**: OpenZeppelin Contracts `^5.6.1` via npm (`node_modules/`)
- **Foundry libs**: forge-std via `forge install` (not npm), stored in `lib/`

## Security Rules

- **Never** hardcode private keys — use `vm.envUint("PRIVATE_KEY")` in scripts
- **Always** keep `.env` in `.gitignore`
- Do not add custom access control, pausability, or upgradeability unless explicitly required
- `_mint` should only be called in constructors (fixed supply)

## File Layout

```
apps/eth-contracts/
├── contracts/    ← production Solidity source (*.sol)
├── script/       ← Foundry deploy scripts (*.s.sol)
├── test/         ← Foundry unit tests (*.t.sol)
├── lib/          ← forge install libraries (gitignored)
├── node_modules/ ← bun install packages (gitignored)
└── out/          ← compiled artifacts (gitignored)
```

## Do NOT

- Run `npm install` or `yarn` — use `bun install`
- Use `truffle` or `hardhat` — this project uses Foundry only
- Edit files in `out/`, `lib/`, or `node_modules/` — these are generated/installed
- Commit `lib/`, `out/`, `node_modules/`, or `.env`

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.