Google Antigravity vs Kiro | agentconfig.ing

Google Antigravity vs KiroComparisonUpdated 2026-03-18

SUMMARY

Google Antigravity (IDE) uses markdown configuration while Kiro (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	Google Antigravity	Kiro	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

FILE MAPPING

Purpose	Google Antigravity	Kiro
Project instructions	AGENTS.md	.kiro/steering/*.md
Project instructions	GEMINI.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)

Kiro

.kiro/steering/*.md

markdown

---
inclusion: always
---

# Project Standards

## Stack
- TypeScript 5.x with Node.js 22
- AWS CDK v2 for infrastructure
- DynamoDB for data, S3 for assets

## Conventions
- Use ESM imports, not CommonJS
- Lambda handlers export a named `handler` function
- Use middy middleware for cross-cutting concerns
- All API responses follow JSON:API format

## Testing
- Unit tests with vitest
- Integration tests with aws-testing-library
- E2E tests use deployed staging environment

KEY DIFFERENCES

1. Global config

Google Antigravity: Not supported. Kiro: Supported.

2. Subdirectory scoping

Google Antigravity: Supported. Kiro: Not supported.

WHICH SHOULD I USE?

Recommendation

Choose based on your IDE/CLI preference. If you use Google Antigravity, configure AGENTS.md. If you use Kiro, configure .kiro/steering/*.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