Go + Docker rules for AI coding agents
Full stack: Go + Docker
Ready-to-commit rules for Go + Docker in every major format: AGENTS.md (Codex, Cursor, Copilot), CLAUDE.md (Claude Code), Cursor .mdc project rules, legacy .cursorrules, Copilot instructions, Windsurf rules and GEMINI.md. A Go HTTP service using the standard library router.
Last reviewed 2026-10-21 · Customise in the generator · Raw: AGENTS.md, CLAUDE.md
The mistake agents make most on this stack
Agents add a router framework for routing that Go 1.22 ServeMux already handles, and swallow errors.
Generated files
AGENTS.md
# AGENTS.md - this project
Instructions for AI coding agents working in this repository.
## Project
A Go + Docker project.
Stack: Go, Docker.
## Commands
- Run: `go run ./cmd/<app>`
- Tests: `go test ./...`
- Vet: `go vet ./...`
- Format: `gofmt -w .`
- Local services: `docker compose up -d`
## Project structure
- Entrypoints in `cmd/<app>/main.go`, private packages in `internal/`.
## How to work in this repo
- Read the relevant files before editing. Follow the patterns already in the codebase over these generic rules.
- Make the smallest change that solves the task. Do not refactor or reformat unrelated code.
- Before saying a task is done, run the type-check, lint and tests listed under Commands and fix what you broke.
- If requirements are ambiguous, ask one clear question instead of guessing.
- Never commit secrets, API keys or `.env` files. Use env vars and keep `.env.example` up to date.
- Do not add a new dependency when the standard library or an existing dependency already covers it.
- Ask before adding, removing or upgrading any dependency.
- Ask before changing database schemas, auth, payments or CI configuration.
- Never delete files, drop data or run destructive commands (`rm -rf`, `git push --force`, `DROP TABLE`) without explicit approval.
- Keep each change under ~200 changed lines where possible; split larger work into steps.
## Go
- Code must be `gofmt`-formatted and pass `go vet`.
- Return errors, do not panic. Wrap with context: `fmt.Errorf("load user %d: %w", id, err)`.
- Pass `context.Context` as the first parameter to anything doing I/O and respect cancellation.
- Use Go 1.22+ `http.ServeMux` patterns (`mux.HandleFunc("GET /items/{id}", h)`, `r.PathValue("id")`) before adding a router dependency.
- Keep interfaces small and define them where they are consumed.
- Write table-driven tests with `t.Run` subtests.
- Use `log/slog` for structured logging.
## Docker
- Use multi-stage builds and slim, pinned base images.
- Run the app as a non-root user in the final image.
- Keep a `.dockerignore` that excludes `.git`, `node_modules`, `.env` and build output.
- Never bake secrets into images; pass them at runtime.
## Reference docs
- [Effective Go](https://go.dev/doc/effective_go)
- [Dockerfile best practices](https://docs.docker.com/build/building/best-practices/)
CLAUDE.md
# CLAUDE.md - this project
Project instructions for Claude Code.
## Project
A Go + Docker project.
Stack: Go, Docker.
## Commands
- Run: `go run ./cmd/<app>`
- Tests: `go test ./...`
- Vet: `go vet ./...`
- Format: `gofmt -w .`
- Local services: `docker compose up -d`
## Project structure
- Entrypoints in `cmd/<app>/main.go`, private packages in `internal/`.
## How to work in this repo
- Read the relevant files before editing. Follow the patterns already in the codebase over these generic rules.
- Make the smallest change that solves the task. Do not refactor or reformat unrelated code.
- Before saying a task is done, run the type-check, lint and tests listed under Commands and fix what you broke.
- If requirements are ambiguous, ask one clear question instead of guessing.
- Never commit secrets, API keys or `.env` files. Use env vars and keep `.env.example` up to date.
- Do not add a new dependency when the standard library or an existing dependency already covers it.
- Ask before adding, removing or upgrading any dependency.
- Ask before changing database schemas, auth, payments or CI configuration.
- Never delete files, drop data or run destructive commands (`rm -rf`, `git push --force`, `DROP TABLE`) without explicit approval.
- Keep each change under ~200 changed lines where possible; split larger work into steps.
## Go
- Code must be `gofmt`-formatted and pass `go vet`.
- Return errors, do not panic. Wrap with context: `fmt.Errorf("load user %d: %w", id, err)`.
- Pass `context.Context` as the first parameter to anything doing I/O and respect cancellation.
- Use Go 1.22+ `http.ServeMux` patterns (`mux.HandleFunc("GET /items/{id}", h)`, `r.PathValue("id")`) before adding a router dependency.
- Keep interfaces small and define them where they are consumed.
- Write table-driven tests with `t.Run` subtests.
- Use `log/slog` for structured logging.
## Docker
- Use multi-stage builds and slim, pinned base images.
- Run the app as a non-root user in the final image.
- Keep a `.dockerignore` that excludes `.git`, `node_modules`, `.env` and build output.
- Never bake secrets into images; pass them at runtime.
## Reference docs
- [Effective Go](https://go.dev/doc/effective_go)
- [Dockerfile best practices](https://docs.docker.com/build/building/best-practices/)
.cursor/rules/project.mdc
---
description: "Core rules for this project"
alwaysApply: true
---
# this project
A Go + Docker project.
Stack: Go, Docker.
## Commands
- Run: `go run ./cmd/<app>`
- Tests: `go test ./...`
- Vet: `go vet ./...`
- Format: `gofmt -w .`
- Local services: `docker compose up -d`
## How to work in this repo
- Read the relevant files before editing. Follow the patterns already in the codebase over these generic rules.
- Make the smallest change that solves the task. Do not refactor or reformat unrelated code.
- Before saying a task is done, run the type-check, lint and tests listed under Commands and fix what you broke.
- If requirements are ambiguous, ask one clear question instead of guessing.
- Never commit secrets, API keys or `.env` files. Use env vars and keep `.env.example` up to date.
- Do not add a new dependency when the standard library or an existing dependency already covers it.
- Ask before adding, removing or upgrading any dependency.
- Ask before changing database schemas, auth, payments or CI configuration.
- Never delete files, drop data or run destructive commands (`rm -rf`, `git push --force`, `DROP TABLE`) without explicit approval.
- Keep each change under ~200 changed lines where possible; split larger work into steps.
.cursor/rules/go.mdc
---
description: "Go conventions: Go service using the standard library net/http router."
globs: **/*.go
alwaysApply: false
---
# Go
- Code must be `gofmt`-formatted and pass `go vet`.
- Return errors, do not panic. Wrap with context: `fmt.Errorf("load user %d: %w", id, err)`.
- Pass `context.Context` as the first parameter to anything doing I/O and respect cancellation.
- Use Go 1.22+ `http.ServeMux` patterns (`mux.HandleFunc("GET /items/{id}", h)`, `r.PathValue("id")`) before adding a router dependency.
- Keep interfaces small and define them where they are consumed.
- Write table-driven tests with `t.Run` subtests.
- Use `log/slog` for structured logging.
Docs: https://go.dev/doc/effective_go
.cursor/rules/docker.mdc
---
description: "Docker conventions: Containerised builds and local services with Docker."
globs: Dockerfile, **/Dockerfile, compose.yaml, docker-compose.yml, .dockerignore
alwaysApply: false
---
# Docker
- Use multi-stage builds and slim, pinned base images.
- Run the app as a non-root user in the final image.
- Keep a `.dockerignore` that excludes `.git`, `node_modules`, `.env` and build output.
- Never bake secrets into images; pass them at runtime.
Docs: https://docs.docker.com/build/building/best-practices/
.cursorrules
# Cursor rules - this project
You are an expert Go, Docker engineer working on this codebase. Follow these rules.
## Project
A Go + Docker project.
Stack: Go, Docker.
## Commands
- Run: `go run ./cmd/<app>`
- Tests: `go test ./...`
- Vet: `go vet ./...`
- Format: `gofmt -w .`
- Local services: `docker compose up -d`
## Project structure
- Entrypoints in `cmd/<app>/main.go`, private packages in `internal/`.
## How to work in this repo
- Read the relevant files before editing. Follow the patterns already in the codebase over these generic rules.
- Make the smallest change that solves the task. Do not refactor or reformat unrelated code.
- Before saying a task is done, run the type-check, lint and tests listed under Commands and fix what you broke.
- If requirements are ambiguous, ask one clear question instead of guessing.
- Never commit secrets, API keys or `.env` files. Use env vars and keep `.env.example` up to date.
- Do not add a new dependency when the standard library or an existing dependency already covers it.
- Ask before adding, removing or upgrading any dependency.
- Ask before changing database schemas, auth, payments or CI configuration.
- Never delete files, drop data or run destructive commands (`rm -rf`, `git push --force`, `DROP TABLE`) without explicit approval.
- Keep each change under ~200 changed lines where possible; split larger work into steps.
## Go
- Code must be `gofmt`-formatted and pass `go vet`.
- Return errors, do not panic. Wrap with context: `fmt.Errorf("load user %d: %w", id, err)`.
- Pass `context.Context` as the first parameter to anything doing I/O and respect cancellation.
- Use Go 1.22+ `http.ServeMux` patterns (`mux.HandleFunc("GET /items/{id}", h)`, `r.PathValue("id")`) before adding a router dependency.
- Keep interfaces small and define them where they are consumed.
- Write table-driven tests with `t.Run` subtests.
- Use `log/slog` for structured logging.
## Docker
- Use multi-stage builds and slim, pinned base images.
- Run the app as a non-root user in the final image.
- Keep a `.dockerignore` that excludes `.git`, `node_modules`, `.env` and build output.
- Never bake secrets into images; pass them at runtime.
## Reference docs
- [Effective Go](https://go.dev/doc/effective_go)
- [Dockerfile best practices](https://docs.docker.com/build/building/best-practices/)
.github/copilot-instructions.md
# Copilot instructions - this project
A Go + Docker project.
Stack: Go, Docker.
## Commands
- Run: `go run ./cmd/<app>`
- Tests: `go test ./...`
- Vet: `go vet ./...`
- Format: `gofmt -w .`
- Local services: `docker compose up -d`
## How to work in this repo
- Read the relevant files before editing. Follow the patterns already in the codebase over these generic rules.
- Make the smallest change that solves the task. Do not refactor or reformat unrelated code.
- Before saying a task is done, run the type-check, lint and tests listed under Commands and fix what you broke.
- If requirements are ambiguous, ask one clear question instead of guessing.
- Never commit secrets, API keys or `.env` files. Use env vars and keep `.env.example` up to date.
- Do not add a new dependency when the standard library or an existing dependency already covers it.
- Ask before adding, removing or upgrading any dependency.
- Ask before changing database schemas, auth, payments or CI configuration.
- Never delete files, drop data or run destructive commands (`rm -rf`, `git push --force`, `DROP TABLE`) without explicit approval.
- Keep each change under ~200 changed lines where possible; split larger work into steps.
.github/instructions/go.instructions.md
---
applyTo: "**/*.go"
---
# Go
- Code must be `gofmt`-formatted and pass `go vet`.
- Return errors, do not panic. Wrap with context: `fmt.Errorf("load user %d: %w", id, err)`.
- Pass `context.Context` as the first parameter to anything doing I/O and respect cancellation.
- Use Go 1.22+ `http.ServeMux` patterns (`mux.HandleFunc("GET /items/{id}", h)`, `r.PathValue("id")`) before adding a router dependency.
- Keep interfaces small and define them where they are consumed.
- Write table-driven tests with `t.Run` subtests.
- Use `log/slog` for structured logging.
.github/instructions/docker.instructions.md
---
applyTo: "Dockerfile,**/Dockerfile,compose.yaml,docker-compose.yml,.dockerignore"
---
# Docker
- Use multi-stage builds and slim, pinned base images.
- Run the app as a non-root user in the final image.
- Keep a `.dockerignore` that excludes `.git`, `node_modules`, `.env` and build output.
- Never bake secrets into images; pass them at runtime.
.windsurf/rules/project.md
---
trigger: always_on
---
# this project
A Go + Docker project.
Stack: Go, Docker.
## Commands
- Run: `go run ./cmd/<app>`
- Tests: `go test ./...`
- Vet: `go vet ./...`
- Format: `gofmt -w .`
- Local services: `docker compose up -d`
## How to work in this repo
- Read the relevant files before editing. Follow the patterns already in the codebase over these generic rules.
- Make the smallest change that solves the task. Do not refactor or reformat unrelated code.
- Before saying a task is done, run the type-check, lint and tests listed under Commands and fix what you broke.
- If requirements are ambiguous, ask one clear question instead of guessing.
- Never commit secrets, API keys or `.env` files. Use env vars and keep `.env.example` up to date.
- Do not add a new dependency when the standard library or an existing dependency already covers it.
- Ask before adding, removing or upgrading any dependency.
- Ask before changing database schemas, auth, payments or CI configuration.
- Never delete files, drop data or run destructive commands (`rm -rf`, `git push --force`, `DROP TABLE`) without explicit approval.
- Keep each change under ~200 changed lines where possible; split larger work into steps.
.windsurf/rules/go.md
---
trigger: glob
globs: **/*.go
---
# Go
- Code must be `gofmt`-formatted and pass `go vet`.
- Return errors, do not panic. Wrap with context: `fmt.Errorf("load user %d: %w", id, err)`.
- Pass `context.Context` as the first parameter to anything doing I/O and respect cancellation.
- Use Go 1.22+ `http.ServeMux` patterns (`mux.HandleFunc("GET /items/{id}", h)`, `r.PathValue("id")`) before adding a router dependency.
- Keep interfaces small and define them where they are consumed.
- Write table-driven tests with `t.Run` subtests.
- Use `log/slog` for structured logging.
.windsurf/rules/docker.md
---
trigger: glob
globs: Dockerfile, **/Dockerfile, compose.yaml, docker-compose.yml, .dockerignore
---
# Docker
- Use multi-stage builds and slim, pinned base images.
- Run the app as a non-root user in the final image.
- Keep a `.dockerignore` that excludes `.git`, `node_modules`, `.env` and build output.
- Never bake secrets into images; pass them at runtime.
GEMINI.md
# GEMINI.md - this project
Project context for Gemini CLI.
## Project
A Go + Docker project.
Stack: Go, Docker.
## Commands
- Run: `go run ./cmd/<app>`
- Tests: `go test ./...`
- Vet: `go vet ./...`
- Format: `gofmt -w .`
- Local services: `docker compose up -d`
## Project structure
- Entrypoints in `cmd/<app>/main.go`, private packages in `internal/`.
## How to work in this repo
- Read the relevant files before editing. Follow the patterns already in the codebase over these generic rules.
- Make the smallest change that solves the task. Do not refactor or reformat unrelated code.
- Before saying a task is done, run the type-check, lint and tests listed under Commands and fix what you broke.
- If requirements are ambiguous, ask one clear question instead of guessing.
- Never commit secrets, API keys or `.env` files. Use env vars and keep `.env.example` up to date.
- Do not add a new dependency when the standard library or an existing dependency already covers it.
- Ask before adding, removing or upgrading any dependency.
- Ask before changing database schemas, auth, payments or CI configuration.
- Never delete files, drop data or run destructive commands (`rm -rf`, `git push --force`, `DROP TABLE`) without explicit approval.
- Keep each change under ~200 changed lines where possible; split larger work into steps.
## Go
- Code must be `gofmt`-formatted and pass `go vet`.
- Return errors, do not panic. Wrap with context: `fmt.Errorf("load user %d: %w", id, err)`.
- Pass `context.Context` as the first parameter to anything doing I/O and respect cancellation.
- Use Go 1.22+ `http.ServeMux` patterns (`mux.HandleFunc("GET /items/{id}", h)`, `r.PathValue("id")`) before adding a router dependency.
- Keep interfaces small and define them where they are consumed.
- Write table-driven tests with `t.Run` subtests.
- Use `log/slog` for structured logging.
## Docker
- Use multi-stage builds and slim, pinned base images.
- Run the app as a non-root user in the final image.
- Keep a `.dockerignore` that excludes `.git`, `node_modules`, `.env` and build output.
- Never bake secrets into images; pass them at runtime.
## Reference docs
- [Effective Go](https://go.dev/doc/effective_go)
- [Dockerfile best practices](https://docs.docker.com/build/building/best-practices/)
Commands your agent should run
| Task | Command |
|---|---|
| Run | go run ./cmd/<app> |
| Tests | go test ./... |
| Vet | go vet ./... |
| Format | gofmt -w . |
| Local services | docker compose up -d |
What the rules cover
Go
Go service using the standard library net/http router. Scoped to **/*.go in Cursor, Copilot and Windsurf.
- Code must be
gofmt-formatted and passgo vet. - Return errors, do not panic. Wrap with context:
fmt.Errorf("load user %d: %w", id, err). - Pass
context.Contextas the first parameter to anything doing I/O and respect cancellation. - Use Go 1.22+
http.ServeMuxpatterns (mux.HandleFunc("GET /items/{id}", h),r.PathValue("id")) before adding a router dependency. - Keep interfaces small and define them where they are consumed.
- Write table-driven tests with
t.Runsubtests. - Use
log/slogfor structured logging.
Source docs: Effective Go
Docker
Containerised builds and local services with Docker. Scoped to Dockerfile, **/Dockerfile, compose.yaml, docker-compose.yml, .dockerignore in Cursor, Copilot and Windsurf.
- Use multi-stage builds and slim, pinned base images.
- Run the app as a non-root user in the final image.
- Keep a
.dockerignorethat excludes.git,node_modules,.envand build output. - Never bake secrets into images; pass them at runtime.
Source docs: Dockerfile best practices
How to install
- Copy
AGENTS.mdto your repo root. That covers Codex, Cursor, GitHub Copilot and most other agents. - Using Claude Code? Add a
CLAUDE.mdwith the single line@AGENTS.md, or use the standalone CLAUDE.md tab above. - Want rules that only load for certain files in Cursor? Add the
.cursor/rules/*.mdcfiles. - Commit the files so your whole team (and every agent) shares them.
FAQ
Where do I put the AGENTS.md for Go + Docker?
Save it as AGENTS.md in the root of your repository, next to your main config file. Codex, Cursor and GitHub Copilot pick it up automatically. For Claude Code, add a CLAUDE.md containing @AGENTS.md (or use the standalone CLAUDE.md on this page).
What is the most common mistake AI agents make with Go?
Agents add a router framework for routing that Go 1.22 ServeMux already handles, and swallow errors.
Which commands should the agent run to check its work?
For this stack: go run ./cmd/<app>, go test ./..., go vet ./..., gofmt -w .. They are listed in the generated files so the agent runs them before finishing a task.
Do these Go + Docker rules work with Cursor and Claude Code?
Yes. This page includes the same rules as AGENTS.md, CLAUDE.md, Cursor .mdc project rules, a legacy .cursorrules file, GitHub Copilot instructions, Windsurf rules and GEMINI.md.
Can I customise these rules?
Yes. Open this stack in the generator to add or remove libraries, set your project name and package manager, switch beginner explanations on, and download everything as a zip.
Related stacks
Node.js + Express + Prisma + Zod validation + Vitest + Docker
A TypeScript REST API with Express 5, Prisma and Zod.
Node.js + Express + Drizzle ORM + Zod validation + Docker
An Express API on Drizzle ORM, packaged with Docker.
Python + FastAPI + SQLAlchemy 2 + Alembic + pytest + Docker
A production-style Python API: FastAPI, SQLAlchemy 2 and Alembic, tested with pytest.
Python + Django + pytest + Docker
A Django app tested with pytest.
Ruby on Rails + Tailwind CSS v4 + Docker
Ruby on Rails 8 with Hotwire and Tailwind.
Rust + Axum + Docker
A Rust web service with Axum and Tokio.