gemini-antigravity-conventions

Applies Antigravity app conventions for plan delivery, model tiers, and skill discovery.

Updated Aug 25, 2026
One-click install
npx skills add https://github.com/hyvanmielenpelit/SharedAgentSkills --skill gemini-antigravity-conventions-hyvanmielenpelit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gemini-antigravity-conventions
Source: https://github.com/hyvanmielenpelit/SharedAgentSkills/tree/main/skills-gemini/gemini-antigravity-conventions
Command: npx skills add https://github.com/hyvanmielenpelit/SharedAgentSkills --skill gemini-antigravity-conventions-hyvanmielenpelit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Working in the Antigravity Standalone App requires platform-specific conventions that differ from Claude Code and Codex: plans must be delivered both to the artifact directory and the shared plans repository, model tiers must be resolved against the models the session actually offers, and skill discovery works through skills.json rather than directory junctions. This Skill encodes those rules so agents behave correctly in this harness. ## Core Features & Use Cases - Dual plan delivery: Creates artifacts in the artifact directory, copies them to the shared plans repository with versioned naming, commits the round, and presents every document as a clickable link. - Cross-application plan implementation: Reads the latest _v<N> plan authored in another application and follows its step order, asking rather than improvising when ambiguous. - Tier-to-model resolution and spawn boundary: Maps deep/standard/mechanical/inherit tiers to models available in the current session and enforces the rule that only this vendor's models can be spawned. - Use Case: An agent in Antigravity receives a plan written in Claude Code, resolves the 'standard' tier to an available mid-tier model, implements the steps, and delivers the walkthrough both as an artifact and as a committed copy in C:\hmp\plans. ## Quick Start Read this skill before planning or implementing any task in the Antigravity Standalone App so plans, links, and model choices follow the correct conventions.

Frequently Asked Questions about gemini-antigravity-conventions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deliver an implementation plan in the Antigravity app?

Create the document in the artifact directory first, then copy it to the shared plans repository under <organization>/<repository>/YYYY-MM-DD/task_name/ with a _v<N> suffix, and commit the round. Present every document as a clickable Markdown link using an absolute forward-slash path.

How do I implement a plan written in Claude Code inside Antigravity?

Read the latest _v<N> version of the plan for the specific task from the plans repository first, then the repository's .plans/ fallback. Follow the plan's step order exactly, and ask the user rather than improvising when the plan is ambiguous.

Can Antigravity spawn subagents using Claude or Codex models?

No. Antigravity can only spawn its own vendor's models, and no configuration changes that. Work targeted at another application is handed over by a person opening that application, with the plan document as the interface.

How does skill discovery work in Antigravity?

Global skills must be declared in the entries array of ~/.gemini/config/skills.json with absolute paths; directory junctions are not used. Project-level skills are auto-discovered in .agents/skills/ or declared via a workspace-relative .agents/skills.json.

Why are my Antigravity global rules out of date?

The inlined ~/.gemini/config/AGENTS.md is a generated copy of the shared rules files, refreshed only when setup.ps1 or sync.ps1 runs. Compare the marked region against the source rules and run setup.ps1 to regenerate it.