AI Coding Rules
Google GeminiGoDocumentation

Generic Documentation Rules for Google Gemini

Generic Documentation Rules adapted for Google Gemini. High-signal generic engineering guidance for real projects.

rules file
# Generic Documentation Rules for Google Gemini

## What to document
- Setup, run, test, deploy, rollback.
- Architecture decisions with rationale and tradeoffs.
- Operational runbooks for common incidents.

## Standards
- Keep docs close to code (repo-first).
- Update docs in same PR as behavior changes.
- Prefer examples and command snippets over prose-heavy explanations.

## DevEx
- README should get a new engineer productive in <15 minutes.
- Keep env var documentation complete and current.

How to use with Google Gemini

← All Google Gemini rulesAll Go rules →
#docs#readme#runbooks#gemini#generic-rules#go#ai-coding-rules

Related Rules

Go Cursor Rules

CursorGo

Cursor rules for Go: idiomatic Go patterns, error handling, concurrency, and Go module conventions.

Code Style
go · golangCopy Ready

Go Claude Rules

ClaudeGo

Claude rules for Go: project structure, error handling, testing, and idiomatic Go patterns.

Architecture
go · golangCopy Ready

Go Windsurf Rules

WindsurfGo

Windsurf rules for Go: hexagonal architecture, clean code, observability, and production Go patterns.

Architecture
go · windsurfCopy Ready

Echo Architecture Rules for GitHub Copilot

GitHub CopilotGo

SEO-ready GitHub Copilot rules for Echo architecture with copy-paste instructions, testing guardrails, and production-safe patterns.

General AI
copilot · goCopy Ready