AN

antigravity-manager

Technical reference for Antigravity Manager development.

Install

mkdir -p .claude/skills/antigravity-manager && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/8535" && unzip -o skill.zip -d .claude/skills/antigravity-manager && rm skill.zip

Installs to .claude/skills/antigravity-manager

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Comprehensive guide to Antigravity Manager architecture, workflows, and development. Use this to understand how to work on the project.
135 charsno explicit “when” trigger
Intermediate

Key capabilities

  • Provide architectural overview of Electron/NestJS stack
  • Manage IPC communication via ORPC
  • Handle SQLite database access
  • Facilitate account rotation and OAuth logic

How it works

The skill acts as a reference guide for the project's modular architecture, providing context on IPC, services, and build workflows.

Inputs & outputs

You give it
Development task or architectural question
You get back
Guidance on implementation or project structure

When to use antigravity-manager

  • Learn the project architecture
  • Find where to add new services or routes
  • Understand the IPC communication flow

About this skill

Antigravity Manager Developer Guide

🏗️ Architecture Overview

Antigravity Manager is a hybrid Desktop Application built with Electron, React, and NestJS. It follows a modular architecture where the frontend (Renderer) communicates with the backend (Main) via type-safe IPC (ORPC).

graph TD
    User[User Interface] -->|React/Vite| Renderer[Renderer Process]
    Renderer -->|ORPC Client| IPC[IPC Layer]
    IPC -->|ORPC Router| Main[Main Process]
    Main -->|Bootstraps| Server[NestJS Server]
    Main -->|Calls| Services[Service Layer]
    Services -->|Read/Write| DB[(SQLite Database)]
    Services -->|HTTP| Cloud[Cloud APIs (Google/Anthropic)]

Key Technologies

  • Frontend: React 19, TailwindCSS v4, TanStack Router, TanStack Query.
  • Backend: Electron (Main), NestJS (Core Logic), Better-SQLite3 (Data).
  • Communication: ORPC (Type-safe IPC wrapper around Electron IPC).
  • Build: Electron Forge + Vite.

📂 Directory Structure

  • src/main.ts: Electron Main Process entry point.
  • src/preload.ts: Bridge between Main and Renderer.
  • src/renderer.tsx: React App entry point.
  • src/components/: Reusable React UI components (Radix UI based).
  • src/ipc/: IPC Routers and Handlers (Domain logic).
    • router.ts: Main ORPC router definition.
    • account/, cloud/, database/: Domain-specific handlers.
  • src/server/: NestJS application modules (proxies/gateways).
  • src/services/: Core business logic (framework agnostic).
    • GoogleAPIService.ts: Gemini/Cloud interactions.
    • AutoSwitchService.ts: Account rotation logic.
  • src/routes/: Frontend routing definitions (File-based).

🚀 Development Workflow

Prerequisites

  • Node.js 18+
  • npm (Project uses package-lock.json)

Common Commands

  • Start Dev Server: npm start
  • Lint Code: npm run lint
  • Unit Test: npm run test:unit
  • E2E Test: npm run test:e2e
  • Build Production: npm run make

🧠 Core Concepts

IPC Communication (ORPC)

The project uses orpc for type-safe communication.

  • Define: Create a router in src/ipc/router.ts with Zod schemas.
  • Implement: Add logic in handlers (e.g., src/ipc/account/handler.ts).
  • Call: Use the generated client in React components.

Database Access

Data is stored in a local SQLite file.

  • Use Better-SQLite3 for direct access.
  • Logic should be encapsulated in src/services or src/ipc.

Account Management

  • Accounts are added via OAuth (Google/Claude).
  • GoogleAPIService handles token exchange and refreshing.
  • AutoSwitchService monitors usage and switches active accounts automatically.

⚠️ Critical Rules

  1. Type Safety: strict TypeScript usage; Zod for runtime validation.
  2. Components: Use src/components/ui (Radix primitives) for consistency.
  3. Async: Handle all IPC/DB calls asynchronously with try/catch.
  4. Security: Never commit secrets. API keys are user-provided or encrypted locally.

When not to use it

  • Projects outside the Antigravity Manager architecture

Prerequisites

Node.js 18+

Limitations

  • Strict adherence to project-specific type safety and component rules required
  • Secrets must not be committed

How it compares

It provides project-specific architectural context rather than generic framework documentation.

Compared to similar skills

antigravity-manager side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
antigravity-manager (this skill)04moNo flagsIntermediate
typescript282moNo flagsBeginner
typescript-skills36moReviewIntermediate
fullstack-guardian13moNo flagsAdvanced

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry