context-loader

Load `.claude/` project context for Gemini tasks.

Updated May 29, 2021
One-click install
npx skills add https://github.com/hikch/dotfiles --skill context-loader-hikch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: context-loader
Source: https://github.com/hikch/dotfiles/tree/main/.gemini/skills/context-loader
Command: npx skills add https://github.com/hikch/dotfiles --skill context-loader-hikch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures consistent project-specific context and coding policies are available to Gemini tasks by loading the standardized .claude/ directory at task start.

Core Features & Use Cases

  • Synchronizes context by reading coding rules, design decisions, and library constraints from .claude/.
  • Guarantees alignment with Claude Code across research and analysis tasks by loading architecture guidelines from .claude/docs/ and rules from .claude/rules/.
  • Supports reproducible analysis by providing a single source of truth for project conventions and safety constraints.

Quick Start

Load the .claude/ context at the start of every task to align Gemini with Claude Code rules, design decisions, and library constraints.

Frequently Asked Questions about context-loader

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I load Claude Code context into Gemini CLI tasks?▼

Context-loading from `.claude/` directories synchronizes Gemini CLI with Claude Code by reading rules, docs, and library files to enforce architecture guidelines, safety constraints, and coding policies across analysis tasks.

How do I sync Gemini analysis with Claude Code design decisions and library constraints?▼

You sync Gemini with Claude Code by loading context from `.claude/rules/` and `.claude/docs/` to enforce project-specific design decisions, architecture guidelines, and library constraints during analysis tasks.

What is the best way to enforce Claude Code safety guidelines in Gemini CLI?▼

Loading the `.claude/` context directory at the start of every Gemini task enforces Claude Code safety constraints, ensuring reproducible analysis and alignment with project conventions.

Can I use existing `.claude/` rules and docs files to align Gemini with project architecture?▼

Yes, context-loader reads existing `.claude/rules/` and `.claude/docs/` files to align Gemini CLI with your project's architecture decisions and coding principles without requiring additional configuration.

Why does Gemini CLI ignore my Claude Code coding rules during analysis tasks?▼

Gemini CLI ignores Claude Code rules because it lacks the project context by default; loading the `.claude/` directory at task start applies the necessary coding policies and library constraints.

Do I need to manually copy `.claude/` files for every Gemini task?▼

No, context-loader automatically reads `.claude/rules/`, `.claude/docs/`, and relevant library files at the start of every task, establishing a single source of truth without manual file copying.