SUMMARY
Google Antigravity (IDE) uses markdown configuration while Firebase Studio (Platform) uses text. They differ on 5 of 11 compared features. Both tools provide AI-assisted development but take different approaches to project configuration.
FEATURE COMPARISON
| Feature | Google Antigravity | Firebase Studio |
|---|---|---|
| Config format | markdown | text |
| Hierarchy support | ✓ | ✗ |
| Global config | ✗ | ✗ |
| Project config | ✓ | ✓ |
| Subdirectory scoping | ✓ | ✗ |
| File inclusion / imports | ✗ | ✗ |
| Ignore file | ✗ | ✗ |
| IDE integration | ✓ | Platform |
| Schema / structure | Free-form (Markdown) | unknown |
| Git committed | ✓ | ✓ |
| Encoding | UTF-8 | UTF-8 |
KEY DIFFERENCES
Google Antigravity: markdown. Firebase Studio: text.
Google Antigravity: Supported. Firebase Studio: Not supported.
Google Antigravity: Supported. Firebase Studio: Not supported.
Google Antigravity: Supported. Firebase Studio: Platform.
Google Antigravity: Free-form (Markdown). Firebase Studio: unknown.
WHICH SHOULD I USE?
Choose based on your IDE/CLI preference. If you use Google Antigravity, configure AGENTS.md. If you use Firebase Studio, configure .idx/dev.nix. Many projects include config files for multiple tools so each team member can use their preferred editor.
PORTABILITY TIP
# Maintain a single source of truth:
cp AI-INSTRUCTIONS.md CLAUDE.md
cp AI-INSTRUCTIONS.md .cursorrules
cp AI-INSTRUCTIONS.md AGENTS.md