Help us improve
Share bugs, ideas, or general feedback.
From antigravity-awesome-skills
Configure and orchestrate parallel agents using the standalone Antigravity 2.0 Agent Manager alongside Antigravity IDE for multi-project coordination.
npx claudepluginhub sickn33/antigravity-awesome-skills --plugin antigravity-bundle-aas-mobile-app-builderHow this skill is triggered — by the user, by Claude, or both
Slash command
/antigravity-awesome-skills:antigravity-agent-managerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
A playbook for orchestrating multi-agent systems using the standalone **Antigravity 2.0 Agent Manager** (white icon) in parallel with the **Antigravity IDE** (black icon).
Orchestrates parallel AI coding agents in isolated Git worktrees using Agency CLI. Create, list, merge tasks; attach files; manage tmux sessions for simultaneous coding.
Designs hosted agent infrastructure: sandboxed execution, remote coding environments, warm pools, session persistence, multiplayer collaboration, and self-spawning agents.
Drives the AgentOps loop (claim→work→validate→close→persist) on Google's Antigravity CLI harness (AGY), supporting Gemini, Claude, and GPT models through AGY's plugin/skill/subagent architecture.
Share bugs, ideas, or general feedback.
A playbook for orchestrating multi-agent systems using the standalone Antigravity 2.0 Agent Manager (white icon) in parallel with the Antigravity IDE (black icon).
Starting with version 2.0, Google decoupled the Agent Manager from the main IDE interface, removing the "Open Agent Manager" button. This skill outlines how to install, configure, and operate the two environments side-by-side to direct multiple AI agents on front-end and back-end projects simultaneously.
C:/Users/erwinpzocikk/Dev/GroupProjects/intIntercatedraAdmin) in both apps.frontend-agent, backend-agent, qa-validator).backend-agent to the server directory (e.g., /server or /api).frontend-agent to the frontend directory (e.g., /client or /src).When configuring the Agent Manager dashboard, specify the target files or directories in the prompts to keep agents from colliding:
Backend Agent Task Prompt:
Role: Backend Developer Agent
Workspace Target: /server
Task: Add a new POST /api/v1/students endpoint in server/routes/students.js and update database/models/student.js. Do not edit files outside the /server directory.
Frontend Agent Task Prompt:
Role: Frontend UI Agent
Workspace Target: /client
Task: Build the student registration form under client/components/StudentForm.jsx. Consume the /api/v1/students endpoint. Do not edit files outside the /client directory.
Since agents write code in parallel, sync their work using git in your IDE terminal:
# In the Antigravity IDE terminal, check the changes written by the agents
git status
# Review diffs before committing
git diff
# Commit stable checkpoints so both agents stay in sync with main branch
git add .
git commit -m "feat: synchronize parallel front-end and back-end agent changes"
Ctrl+R or developer reload).@antigravity-workflows - To guide the agent through sequential multi-agent execution.@antigravity-skill-orchestrator - For task complexity assessment and general skill routing.@gitops-workflow - To coordinate commits and branch merges in team environments.