Skip to content

GEMINI.md

Latest commit

 

History

History
50 lines (34 loc) · 2.31 KB

GEMINI.md

File metadata and controls

50 lines (34 loc) · 2.31 KB

Gemini

Shyed AI Tooling Policy

Canonical shared AI/tooling index:

F:\GitHubDesktop\GitHubCloneFiles\Obsidian_Vault\8 AI_Prompt_Engineering\000 AI Tools Workflow Index.md

Use local repo instructions first, then the canonical index, then tool defaults as fallback if needed.

Rules:

  • Do not duplicate full global policy here; reference the canonical index.
  • Respect existing lockfiles and local project conventions.
  • Use pnpm only for pnpm-managed repos; use npm for package-lock.json repos.
  • Prefer Windows-native Node 22+ for global tools on Shyed's current Windows/WSL 1 machine.
  • Ask before global installs, lockfile replacement, package-manager migration, MCP changes, hook changes, destructive actions, or broad rewrites.

Persistent AI Reminder

Do not make Shyed repeat stable setup/context instructions.

Before asking setup/context questions or recreating previous work:

  1. Read local repo instructions in this order when present: AGENTS.md, CLAUDE.md, GEMINI.md, .cursorrules, .windsurfrules, .clinerules, .github/copilot-instructions.md, ANTIGRAVITY.md.
  2. Read canonical workflow index: F:\GitHubDesktop\GitHubCloneFiles\Obsidian_Vault\8 AI_Prompt_Engineering\000 AI Tools Workflow Index.md
  3. Read cross-reference hub: F:\GitHubDesktop\GitHubCloneFiles\Obsidian_Vault\8 AI_Prompt_Engineering\docs\ai-tooling-crossrefs.md
  4. Read Caveman/Cavemem/MemPalace hub: F:\GitHubDesktop\GitHubCloneFiles\Obsidian_Vault\8 AI_Prompt_Engineering\Local_RAG_RAFT_AI_Tools\CavemanCavemen\CavemanCavemen.md
  5. Check process/install log: F:\GitHubDesktop\GitHubCloneFiles\Obsidian_Vault\8 AI_Prompt_Engineering\docs\installation-process-log.md
  6. Search existing files before creating new ones.

Default behavior:

  • Use compact references, not duplicated large docs.
  • Link/interlink/cross-reference instead of copying full content.
  • Preserve local repo defaults and existing tool behavior.
  • Fall back to tool defaults if canonical/local references are missing or fail.
  • Ask only before risky actions: global installs, MCP/hook changes, destructive edits, lockfile/package-manager migration, credential/account changes, broad rewrites.