Gemini CLI · JavaScript / TypeScript · Next.js · Popular baseline

# Gemini CLI · JavaScript / TypeScript + Next.js  
Generated February 10, 2026  
Agent: Gemini CLI  
Language: JavaScript / TypeScript  
Framework: Next.js

## Global rules
- Start by reading existing project instructions and architecture docs before changing behavior.

- Prefer minimal diffs and preserve existing code style and naming conventions.

- State assumptions and call out risks before making breaking or cross-module changes.

- When behavior changes, add or update tests in the closest existing test layer.

- Never commit secrets, tokens, credentials, or generated private keys.

Start by reading existing project instructions and architecture docs before changing behavior.

Prefer minimal diffs and preserve existing code style and naming conventions.

State assumptions and call out risks before making breaking or cross-module changes.

When behavior changes, add or update tests in the closest existing test layer.

Never commit secrets, tokens, credentials, or generated private keys.

## Agent-specific
- Prefer deterministic, reproducible shell commands over manual workflows.

- Structure output as actions, results, and next steps.

- When generating code, prioritize maintainability over cleverness.

## Language-specific
- Prefer TypeScript types/interfaces for public contracts.

- Keep functions pure when possible and isolate side effects.

- Avoid implicit any and unstable object shapes.

## Framework-specific
- Use App Router conventions and colocate route logic with pages.

- Keep server/client component boundaries explicit.

- Cache data fetches intentionally and invalidate with clear triggers.

## Options

### Token saving rules
- Reuse shared instruction snippets instead of restating long guidance.

- Avoid duplicating context already available in repository docs.

### Testing rules
- Require tests for changed behavior or document why tests were not added.

- Run the smallest relevant test subset first, then broaden if needed.

### Code style rules
- Follow existing formatter/linter configuration.

- Avoid style-only churn in unrelated files.

### Architecture rules
- Preserve module boundaries and avoid leaking internal abstractions.

- Prefer incremental refactors over large rewrites.

### Security rules
- Validate and sanitize all user-controlled input.

- Apply least-privilege defaults for data access and actions.

### Prefer minimal diffs
- Limit changes to the smallest set of files and lines needed.

- Defer unrelated cleanup to separate follow-up changes.