Google Antigravity vs PearAI

Google Antigravity vs PearAIComparisonUpdated 2026-03-18

SUMMARY

Google Antigravity (IDE) uses markdown configuration while PearAI (Editor) uses markdown. They differ on 3 of 11 compared features. Both tools provide AI-assisted development but take different approaches to project configuration.

FEATURE COMPARISON

Feature	Google Antigravity	PearAI	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	✓	Editor
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

FILE MAPPING

Purpose	Google Antigravity	PearAI
Project instructions	AGENTS.md	AGENTS.md

SIDE-BY-SIDE CODE SAMPLES

Google Antigravity

AGENTS.md

markdown

# Project Instructions

## Architecture
- Monorepo with apps/ and packages/ directories
- Each app is a standalone Next.js deployment
- Shared packages use TypeScript project references

## Code Standards
- TypeScript strict mode everywhere
- Use Zod for runtime validation at API boundaries
- Prefer server components; use "use client" only when needed
- All database queries go through the data-access layer

## Testing
- Unit tests with Vitest for business logic
- Integration tests for API routes
- E2E tests with Playwright for critical user flows

## Deployment
- Preview deployments on every PR
- Production deploys from main branch only
- Environment variables managed via .env.local (never committed)

PearAI

.pearai/rules

markdown

# PearAI Project Rules

## Framework
- Next.js 15 App Router with TypeScript
- Drizzle ORM with PostgreSQL
- TailwindCSS v4 for styling

## Patterns
- Use server actions for mutations
- Colocate loading.tsx and error.tsx with page routes
- Prefer RSC; add "use client" only when needed

## Naming
- Components: PascalCase (UserProfile.tsx)
- Utilities: camelCase (formatDate.ts)
- Database tables: snake_case

## Dependencies
- Do NOT add new dependencies without asking
- Use date-fns for date manipulation
- Use zod for all validation

## Commands
- Dev: pnpm dev
- Build: pnpm build
- Lint: pnpm lint

KEY DIFFERENCES

1. Hierarchy support

Google Antigravity: Supported. PearAI: Not supported.

2. Subdirectory scoping

Google Antigravity: Supported. PearAI: Not supported.

3. IDE integration

Google Antigravity: Supported. PearAI: Editor.

WHICH SHOULD I USE?

Recommendation

Choose based on your IDE/CLI preference. If you use Google Antigravity, configure AGENTS.md. If you use PearAI, configure .pearai/rules. 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