aktonay/skillz / skills/ide-meta/agy-customizations
agy-customizations
VerifiedComprehensive guide and reference for the Antigravity Customization System. Use to explain how customizations work, their loading priority, discovery mechanisms, and to guide the creation of skills, rules, plugins, hooks, and MCP servers.
Antigravity Customization System Guide
The Antigravity Customization System allows you to tailor the agent's behavior, teach it new workflows, enforce guidelines, and integrate it with external tools. By customizing the agent, you can transition it from a general-purpose assistant to an expert pair programmer specialized in your project's codebase and processes.
Customization Types: Quick Reference
Choose the right customization type based on your goal:
| Type | Config File/Folder | Scope | Best For | Learn More |
|---|---|---|---|---|
| Rules | GEMINI.md, AGENTS.md | Contextual / Hierarchical | Enforcing coding styles, API restrictions, and local guidelines. | Rules Guide |
| Skills | skills/<name>/SKILL.md | On-Demand (Progressive) | Teaching the agent multi-step procedures, runbooks, and tool workflows. | Skills Guide |
| Plugins | plugins/<name>/plugin.json | Bundle | Packaging related skills, rules, and MCP configs into a single unit. | Plugins Guide |
| Hooks | hooks.json | Lifecycle Event | Running scripts/commands at specific agent lifecycle points (e.g., pre-tool execution). | Hooks Guide |
| MCP Servers | mcp_config.json | Tool Integration | Connecting the agent to external services and custom tool providers. | MCP Guide |
Customization Discovery and Locations
Antigravity automatically discovers customizations by traversing specific directories.
Discovery Locations
- Workspace Customizations (Project-Specific):
- Path:
.agents/(or.agent/,_agents/,_agent/) at the root of your project. - Use this to share customizations with your team by checking them into version control (VCS).
- The agent walks from your current working directory up to the repository
root (e.g., the folder containing
.git) to find these directories.
- Path:
- Directory & Project Rules (Hierarchical):
- Paths:
GEMINI.md,AGENTS.md,.agents/rules/*.md - As you open or edit files, the agent walks up from the file's directory to the repository root, loading all rules it finds.
- Paths:
- Global Configuration (Machine-Local):
- Path:
~/.gemini/config/ - Applies to all projects and workspaces run on your machine.
- Path:
Loading Priority and Precedence
When multiple customizations are discovered, they are loaded and applied in a specific order. If there are naming conflicts (e.g., two skills with the same name), the higher-priority customization overrides the lower-priority one.
The priority order (from highest to lowest) is:
- Workspace Project: Hierarchical discovery walking up from the CWD to the repository root.
- Declared Configurations: Customizations explicitly listed in
skills.jsonorplugins.jsonin your workspace. - Global Discovery:
~/.gemini/config/ - Built-in Customizations: Default skills bundled with the application.
- Global Declared Configurations: Explicitly listed in global JSON configs.
How Customizations are Applied
Progressive Disclosure (Skills and Rules)
To prevent overwhelming the model's context window, Antigravity uses progressive disclosure:
- Skills are not loaded into the context window by default. Only their names and descriptions are injected. The full content of a skill is only loaded if the model (or the user) explicitly decides to activate it.
- Rules with
trigger: model_decisionbehave similarly. Onlyalways_onrules are loaded unconditionally.
Deduplication
All customizations (especially rules) are deduplicated by their resolved file paths. A rule file will never be injected more than once in a single conversation turn, even if it matches multiple trigger conditions.
Advanced Management: JSON Configs
For customizations stored in non-standard locations, you can use skills.json
and plugins.json to explicitly register them and inherit from shared
configurations.
- Learn how to configure these in the JSON Configurations Guide.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 467k | Updated | Claude CodeCodex | Verified | Install |
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 467k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |