AWSKnown publisherawslabs/operator-for-ai-chips-on-aws/.cursor/rules/make-commands.md

operator-for-ai-chips-on-aws / rules

Cursor rule6 starsChanged 4 months agoApache-2.0View on GitHub

How to run make targets — check Go toolchain first, fall back to skipper

Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.
Of the Cursor rule files we read, the 4,157 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository3 other files it gives its agents.
- .cursor/rules/github-repo.mdCursor rule
- implementSkill
- implementSkill

The file

We split this make-commands.md into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
Before executing any make target (e.g., make unit-test, make fmt, make lint, make generate, make manifests, make manager):
line 8

≈ “Common” is an estimate: at least 1 in 5 of the 6,668 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

make-commands.md

Running `make` Commands

Before executing any make target (e.g., make unit-test, make fmt, make lint, make generate, make manifests, make manager):

Check the local Go version:
```
go version 2>/dev/null
```
Compare the output against the version required by go.mod (currently Go 1.24). The environment is compatible only if go version succeeds and reports a version that satisfies the go.mod requirement.
If the environment is compatible, run the make target directly:
```
make unit-test
```
If the environment is NOT compatible (wrong Go version, go not found, or required utilities like mockgen/controller-gen are missing), do NOT attempt to install, upgrade, or modify the local toolchain. Instead, run the command through Skipper, which provides a containerised build environment with the correct Go version and all required tools:
```
skipper make unit-test
```

This applies to every make invocation — tests, linting, formatting, code generation, manifest generation, and builds. Never try to fix a Go version mismatch or install missing tools on the host; always fall back to skipper make ....

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.

Check your setup, free