plugin-structure

Plugin Structure for Antigravity

Overview

Antigravity plugins follow a standardized directory structure with automatic component discovery. Understanding this structure enables creating well-organized, maintainable plugins that integrate seamlessly with Antigravity.

Key concepts:

• Conventional directory layout for automatic discovery
• Manifest-driven configuration in .antigravity-pluginplatform-install.json
• Component-based organization (commands, agents, skills, hooks)
• Portable path references using ${GEMINI_PLUGIN_ROOT}
• Explicit vs. auto-discovered component loading

Directory Structure

Every Antigravity plugin follows this organizational pattern:

plugin-name/
├── .antigravity-plugin/
│   └── plugin.json          # Required: Plugin manifest
├── commands/                 # Slash commands (.md files)
├── agents/                   # Subagent definitions (.md files)
├── skills/                   # Agent skills (subdirectories)
│   └── skill-name/
│       └── SKILL.md         # Required for each skill
├── hooks/
│   └── hooks.json           # Event handler configuration
├── .mcp.json                # MCP server definitions
└── scripts/                 # Helper scripts and utilities

Critical rules:

1. Manifest location: The plugin.json manifest MUST be in .antigravity-plugin/ directory
2. Component locations: All component directories (commands, agents, skills, hooks) MUST be at plugin root level, NOT nested inside .antigravity-plugin/
3. Optional components: Only create directories for components the plugin actually uses
4. Naming convention: Use kebab-case for all directory and file names

Plugin Manifest (plugin.json)

The manifest defines plugin metadata and configuration. Located at .antigravity-pluginplatform-install.json:

Required Fields

{
  "name": "plugin-name"
}

Name requirements:

• Use kebab-case format (lowercase with hyphens)
• Must be unique across installed plugins
• No spaces or special characters
• Example: code-review-assistant, test-runner, api-docs