gemini-precision

gemini-precision

Overview

High-precision operational standard designed specifically to harness the high speed and expansive context window of Google Gemini models while eliminating common LLM failure modes: hasty assumptions, partial code placeholders (// ...), unverified assertions, and scope creep.

When to Use

Activate whenever:

• Executing non-trivial code modifications, refactoring, bug fixes, or architecture design.
• The user requires maximum rigor, reliability, and precision from Gemini.
• Handling complex multi-file changes where accidental side-effects must be zero.

Rules & Patterns

1. The Read-Before-Write Invariant (Zero Assumptions)

Never write code based on assumptions about the codebase.

• Before modifying a function or creating an integration, always inspect the actual files using view_file or grep_search.
• Check the exact runtime, framework version, and installed dependencies (e.g. React 19 vs 18, Next.js 15 vs 14, Tailwind v4 vs v3, Zod vs Joi) in package.json or config files before generating code.
• Verify imported symbol names and parameter signatures directly from source files.

2. The Zero-Placeholder Invariant (Complete Code Only)

Never produce lazy, incomplete, or stubbed output.

• ❌ Forbidden:
  • // TODO: implement logic here
  • // ... rest of existing code ...
  • // ... existing imports ...
  • Mock stub returns when real integration is required
• ✅ Mandatory:
  • Provide 100% complete, fully-implemented, compilable, and drop-in ready code.
  • When replacing a block of code, include all necessary imports, type definitions, and edge-case handling.

3. The Proof-of-Work Invariant (Verification Before Completion)

Never claim a task is complete without tool-verified evidence.

• When modifying code or configuration:
  1. Run the project validator or compiler (node .agents/ctx.js validate, tsc --noEmit, etc.).
  2. Run unit and integration tests (npm test, pytest, etc.).
  3. Run linter and formatting checks (npm run lint:md, eslint, etc.).
• If a test or validation fails, do not guess: read the exact error trace, fix the root cause, and re-run until green.