conventions-antigravity

To structure Antigravity workspace skills correctly, place artifacts in `.gemini/` paths, use `.agent/` or `.agents/` directories, and configure `gemini-extension.json` and `GEMINI.md` files. This standardization ensures reliable NLPM scoring and checking during transitions.

Gemini CLI artifacts require specific filesystem layouts including `.gemini/` paths, `gemini-extension.json`, `GEMINI.md` memory files, and TOML-style slash commands. Enforcing these metadata surfaces prevents artifacts from being mislocated or missing expected configuration.

Scoring Tier 2-Antigravity artifacts accurately requires applying Tier 2-Antigravity overlays while relying on the universal conventions baseline. This tier-aware scoring alignment targets skill discovery, slash command TOML authoring, and memory file expectations.

The Antigravity 2.0 transition currently treats the choice between singular `.agent` and plural `.agents` workspace skills paths as advisory. This unsettled path convention requires advisory handling until PR-B verification confirms the correct directory structure.

Writing TOML-style slash commands for Antigravity involves authoring slash command files according to tool-specific conventions enforced by Antigravity 2.0. Standardizing these command structures ensures correct skill discovery and proper hook event integrations.

Antigravity skills fail NLPM scoring checks when they are inconsistently structured, mislocated, or missing expected metadata. Applying Antigravity-specific layout guidance and tier-aware scoring alignment resolves these validation errors across the transition period.