Google Antigravity vs TabnineComparisonUpdated 2026-03-18
SUMMARY
Google Antigravity (IDE) uses markdown configuration while Tabnine (IDE) 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 | Tabnine |
|---|---|---|
| Config format | markdown | markdown |
| Hierarchy support | ✓ | ✗ |
| Global config | ✗ | ✓ |
| Project config | ✓ | ✓ |
| Subdirectory scoping | ✓ | ✗ |
| File inclusion / imports | ✗ | ✗ |
| Ignore file | ✗ | ✗ |
| IDE integration | ✓ | ✓ |
| Schema / structure | Free-form (Markdown) | Free-form (Markdown) |
| Git committed | ✓ | ✓ |
| Encoding | UTF-8 | UTF-8 |
FILE MAPPING
| Purpose | Google Antigravity | Tabnine |
|---|---|---|
| Project instructions | AGENTS.md | .tabnine/guidelines/*.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)
Tabnine
.tabnine/guidelines/*.md
markdown
# Application Guidelines
## Architecture
- This is a monorepo managed with Turborepo
- Apps: web (Next.js), api (Express), mobile (React Native)
- Shared packages: ui, config, types
## Code Standards
- TypeScript strict mode in all packages
- Use barrel exports (index.ts) for public APIs
- No default exports; use named exports everywhere
- Prefer async/await over raw Promises
## API Design
- RESTful endpoints follow /api/v1/{resource} pattern
- All responses use { data, error, meta } envelope
- Validate request bodies with Zod schemas
- Return 4xx for client errors, 5xx for server errors
## Database
- Use Prisma ORM for all database operations
- Migrations checked into source control
- Soft-delete pattern: use deletedAt timestamp, never hard delete
- All timestamps stored as UTC
## Testing
- Jest for unit tests, Playwright for E2E
- Test files colocated: foo.ts -> foo.test.ts
- Mock external services, never call real APIs in tests
KEY DIFFERENCES
Google Antigravity: Supported. Tabnine: Not supported.
Google Antigravity: Not supported. Tabnine: Supported.
Google Antigravity: Supported. Tabnine: Not supported.
WHICH SHOULD I USE?
Choose based on your IDE/CLI preference. If you use Google Antigravity, configure AGENTS.md. If you use Tabnine, configure .tabnine/guidelines/*.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
SEE ALSO
Tool pages:
File references:
agentconfig.ing2026-03-18COMPARE(1)