AI Coding Rules
Google GeminiGoGeneral AI

Generic Debugging Rules for Google Gemini

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

rules file
# Generic Debugging Rules for Google Gemini

## Triage flow
- Reproduce reliably before changing code.
- Narrow blast radius with logs/metrics/traces.
- Form one hypothesis at a time; verify/falsify quickly.

## Incident handling
- Prioritize user impact reduction first, root cause second.
- Add temporary guardrails if full fix needs longer.
- Capture timeline, contributing factors, and concrete follow-up actions.

## Prevention
- Add regression tests for every production bug.
- Improve visibility where detection was delayed.
- Remove ambiguity from error messages and status signals.

How to use with Google Gemini

← All Google Gemini rulesAll Go rules →
#debugging#incident-response#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