Skip to content
Remote Control
Customizations command (/agy-customizations)2-0Antigravity AppFeaturesCustomizations command (/agy-customizations) Antigravity App FeaturesAntigravity AppAntigravity CLIAntigravity IDE
Available on:
Antigravity AppAntigravity CLIAntigravity IDE

Customizations command (/agy-customizations)

Section titled “Customizations command (/agy-customizations)”

Load the Antigravity customization reference into the agent’s context before you ask it to create, change, or explain a rule, skill, plugin, hook, or MCP server configuration.

/agy-customizations is a built-in skill available in the Antigravity App, the Antigravity CLI, and the Antigravity IDE. Running the command gives the agent the Antigravity Customization System Guide for the rest of the conversation, so the agent works from the documented formats, locations, and precedence rules. The agent can also load the guide on its own when a request is about customizations; running the command makes sure it does. The guide covers:

  • Customization types: what rules, skills, plugins, hooks, and MCP servers are for, and which file or folder defines each one.
  • Discovery and precedence: where Antigravity looks for customizations, such as the .agents/ folder in your project and ~/.gemini/config/, and which one wins when two have the same name. For the full rules, refer to Customization discovery.
  • How customizations are applied: progressive disclosure for skills and model_decision rules, and deduplication of rule files.
  • Discovery manifests: loading skills and plugins from other folders with skills.json and plugins.json. For all manifest types and fields, refer to Discovery manifests.

Each customization type links to a detailed guide that the agent reads on demand, so the reference adds little to the context window until a request needs it.

Type /agy-customizations followed by a request. The agent loads the guide, reads the sections that apply, and carries out the request as it would any other prompt:

/agy-customizations create a PreToolUse hook that blocks git push --force
/agy-customizations my deploy skill never shows up as /deploy, figure out why
/agy-customizations should this be a rule or a skill?

To load the reference without a request, for example before a longer conversation about your project’s setup, run the command on its own.

Explore related documentation: