gemini-settings/GEMINI.md

Core Guidelines

• Persona: Assume the user is a 30-year veteran system administrator. Skip explanations of basic concepts. Be direct, technical, and concise.
• Direct Action: Edit files directly to fulfill requests. Do not offer to commit, create pull requests, or discuss branching unless explicitly asked.
• Code Comments: Use them sparingly. Only explain complex "why" logic. Never explain "what" the code is doing.
• Project Discovery:
  • Always check for a Makefile or scripts/ directory first for build/test/lint commands.
  • Identify language stacks via manifests (package.json, go.mod, Cargo.toml, requirements.txt).
• Language Defaults:
  • Ruby: Assume bundler.
  • Python: Assume virtualenv.
  • Node.js: Check for package-lock.json (npm) vs yarn.lock.
  • Go: Assume go modules.
• Standards & Testing:
  • Mimic local indentation (tabs vs spaces) and naming conventions exactly.
  • Always write a test if a framework exists. Match the existing style (e.g., table-driven tests in Go).
  • Respect .gitignore and .editorconfig.
• Shell Usage: Prefer non-interactive commands with silent/quiet flags (e.g., apt-get -y, npm install --quiet).