Antigravity Setup and Usage Guide

Google Antigravity 2.0 discovers workspace customizations from the project-local .agents/ directory. ECC's Antigravity target installs native rules, workflows, skills, and custom agents into that directory.

Native Antigravity 2.0 installation requires ECC 2.2.0 or newer. ECC 2.1.0 uses the legacy .agent/ adapter and does not provide the native layout described below.

Quick start

Verify that 2.2.0 is readable from the registry, then run the pinned package from the project you want to configure:

npm view ecc-universal version
npx ecc-universal@2.2.0 install --profile minimal --target antigravity

Source checkout alternative

# Run every command below from the project you want to configure.
# Keep the ECC source checkout separate and use its absolute path.
ECC_ROOT="/absolute/path/to/ECC"

# Install the minimal profile
"$ECC_ROOT/install.sh" --profile minimal --target antigravity

# Compatibility syntax: common rules plus only these language packs
"$ECC_ROOT/install.sh" --target antigravity typescript python go

PowerShell uses the same project-root working-directory contract:

$EccRoot = "C:\absolute\path\to\ECC"

& "$EccRoot\install.ps1" --profile minimal --target antigravity
& "$EccRoot\install.ps1" --target antigravity typescript python go

Start a new Antigravity conversation after installing so the agent receives the updated skill inventory.

Native install mapping

ECC source	Antigravity destination	Purpose
rules/	.agents/rules/	Workspace rules, flattened with collision-safe names
commands/	.agents/workflows/	User-invoked slash workflows
skills/<name>/	.agents/skills/<name>/	Agent Skills with a required SKILL.md
agents/<name>.md	.agents/agents/<name>.md	Custom main agents and subagents

ECC does not copy the repository's .agents/ directory wholesale. That source tree is Codex packaging and contains Codex-specific marketplace metadata. An