context-loader

To load project coding context into Gemini CLI, you need a context loader to read files under the .claude/rules and .claude/docs directories. This syncs Gemini CLI with your project's specific coding rules, design decisions, and library constraints.

Gemini CLI ignores design docs and testing guidelines because it lacks your project's coding context. Loading context from the .claude directory enforces language protocols and library constraints, ensuring generated code conforms to existing architecture decisions and team standards.

To ensure downstream agents follow Claude Code conventions, load context from the .claude directory at the start of research tasks. This enforces coding rules and persists findings into .claude/docs/research, keeping downstream analyses aligned and reproducible.

Yes, you can use Gemini CLI for project analysis while applying type hints and simplicity principles. A context loader reads these specific coding rules from the project's rules directory, aligning implementation suggestions and research with your existing architecture.

The best way to sync Gemini CLI with project library constraints is to load the .claude directory context. This reads design documentation and library limits, enforcing output protocols to align implementation suggestions with existing architecture decisions for actionable results.