Gemini Code Assist vs Void | agentconfig.ing

Gemini Code Assist vs VoidComparisonUpdated 2026-03-18

SUMMARY

Gemini Code Assist (IDE) uses markdown configuration while Void (IDE) uses markdown. They differ on 2 of 11 compared features. Both tools provide AI-assisted development but take different approaches to project configuration.

FEATURE COMPARISON

Feature	Gemini Code Assist	Void	Notes
Config format	markdown	markdown
Hierarchy support	✓	✗	Whether config files can be placed at multiple directory levels
Global config	✗	✗	User-wide configuration outside any project
Project config	✓	✓
Subdirectory scoping	✓	✗	Config files in subdirectories that apply only to that subtree
File inclusion / imports	✗	✗	Ability to include or reference other files from config
Ignore file	✗	✗
IDE integration	✓	✓
Schema / structure	Free-form (Markdown)	Free-form (Markdown)	Whether config uses structured schema or free-form content
Git committed	✓	✓	Whether primary config files are intended to be version-controlled
Encoding	UTF-8	UTF-8

SIDE-BY-SIDE CODE SAMPLES

Gemini Code Assist

GEMINI.md

markdown

# Project Rules

## Overview
E-commerce platform built with Go microservices and React frontend.
All services communicate via gRPC with Protocol Buffers.

## Go Services
- Follow standard Go project layout (cmd/, internal/, pkg/)
- Use structured logging with slog (not log or fmt.Println)
- Error handling: always wrap errors with fmt.Errorf("%w", err)
- Database access through repository pattern in internal/repo/
- All public functions must have godoc comments

## API Design
- Proto files live in proto/ directory with buf for linting
- Use field masks for partial updates
- Pagination via cursor-based tokens, not offset

## Testing
- Table-driven tests for all business logic
- Use testcontainers-go for integration tests
- Minimum 80% coverage on internal/ packages
- Mock external services with gomock interfaces

## Do Not
- Use global variables or init() functions
- Import internal packages across service boundaries
- Commit generated .pb.go files (CI generates them)

Void

.void/rules/*.md

markdown

---
description: Python backend conventions
globs: "app/**/*.py"
auto_apply: true
---

# Backend Rules

## Stack
- Python 3.12 with FastAPI
- SQLAlchemy 2.0 with async sessions
- Alembic for migrations
- pytest for testing

## Conventions
- Use type hints on all function signatures
- Async endpoints by default
- Pydantic v2 models for request/response schemas
- Repository pattern for database access

## File Structure
- app/api/routes/ — API endpoints
- app/models/ — SQLAlchemy models
- app/schemas/ — Pydantic schemas
- app/services/ — Business logic

KEY DIFFERENCES

1. Hierarchy support

Gemini Code Assist: Supported. Void: Not supported.

2. Subdirectory scoping

Gemini Code Assist: Supported. Void: Not supported.

WHICH SHOULD I USE?

Recommendation

Choose based on your IDE/CLI preference. If you use Gemini Code Assist, configure GEMINI.md. If you use Void, configure .void/rules/*.md. Many projects include config files for multiple tools so each team member can use their preferred editor.

PORTABILITY TIP

sync-instructions.sh

bash

# Maintain a single source of truth:
cp AI-INSTRUCTIONS.md CLAUDE.md
cp AI-INSTRUCTIONS.md .cursorrules
cp AI-INSTRUCTIONS.md AGENTS.md