agentleFS
hiromailyhiromaily/go-crypto-wallet/.cursor/rules/go/go-path.mdc

go-crypto-wallet / go

Cursor rule128 starsChanged 6 months agoMITView on GitHub

Go Path Configuration Rules

We split this go-path.mdc into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If a version manager is interfering, remove it from PATH for this session:

    line 38

≈ “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
go-path.mdc
---
description: Go Path Configuration Rules
globs: ["**/*.go"]
alwaysApply: false
---


# Go Path Configuration Rules

## Overview

This project uses **Homebrew-installed Go only**. Version managers (e.g., `mise`, `asdf`, `goenv`) must NOT affect this project.

## Required Go Version

The Go version is specified in `go.mod`. Always use the Homebrew-installed Go that matches this version.

## Common Symptoms of Version Manager Interference

- `compile: version "go1.X.X" does not match go tool version "go1.Y.Y"`
- `go version` shows different version than expected
- Build failures after Go upgrade

## Diagnosis

```bash
# Check which Go is being used
which go
go version
go env GOROOT

# Check for version managers in PATH (should NOT be present)
echo $PATH | tr ':' '\n' | grep -E 'mise|asdf|goenv'
```

## Solution: Disable Version Managers

If a version manager is interfering, remove it from PATH for this session:

```bash
# Remove version managers from PATH and use Homebrew Go
export PATH=$(echo $PATH | tr ':' '\n' | grep -v 'mise' | tr '\n' ':' | sed 's/:$//')
export GOROOT=/opt/homebrew/Cellar/go/1.26.2/libexec

# Verify
go version
```

## Expected Environment

| Variable     | Expected Value                              |
| ------------ | ------------------------------------------- |
| `which go`   | `/opt/homebrew/bin/go`                      |
| `go version` | Matches `go.mod` version                    |
| `GOROOT`     | `/opt/homebrew/Cellar/go/<version>/libexec` |

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.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

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.