gemini-workspace-bridge

# Gemini Workspace Bridge

## Documentation Delegation

> **Documentation Source:** For authoritative workspace patterns and current conventions, query `gemini-cli-docs` skill.
> This skill provides integration guidance; `gemini-cli-docs` provides official Gemini CLI documentation.

## Overview

This skill defines the hybrid workspace architecture for Claude Code and Gemini CLI collaboration. It establishes conventions for file storage, artifact exchange, and cross-CLI communication.

## When to Use This Skill

**Keywords:** workspace structure, artifact storage, cross-cli, shared files, gemini artifacts, claude artifacts, file locations, where to store

**Use this skill when:**

- Setting up a project for dual-CLI workflow
- Deciding where to store AI-generated artifacts
- Understanding the hybrid tracked/gitignored strategy
- Managing cross-CLI file exchange

## Core Architecture

### Hybrid Approach

The workspace uses a **hybrid strategy**:

- **Tracked files**: Memory files, valuable artifacts (plans, reports)
- **Gitignored temp**: Session state, caches, transient outputs

### Directory Structure

```text
project-root/
├── CLAUDE.md                    # Source of truth (tracked)
├── GEMINI.md                    # Points to CLAUDE.md + overrides (tracked)
│
├── .claude/
│   ├── settings.json            # Claude Code configuration
│   └── temp/                    # (gitignored) Session artifacts
│       └── gemini-results/      # Parsed Gemini outputs
│
├── .gemini/
│   ├── settings.json            # Gemini CLI configuration
│   └── temp/                    # (gitignored) Gemini session state
│
└── docs/                        # (tracked) Persistent AI artifacts
    └── ai-artifacts/            # Version-controlled reports
        ├── explorations/        # Codebase exploration reports
        └── plans/               # Implementation plans
```

## Artifact Location Guide

### Decision Tree

```text
Is this artifact valuable long-term?
├── YES: Should others see