google antigravity

Phase 1: Installation & Environment Setup

Antigravity Workspaces

httpdocs

/var/www/vhosts/yourdomain.com/httpdocs

.code-workspace

Troubleshooting

Missing Updater

winget install --id Google.Antigravity -e --source winget

Bypassing Chroot Jails for Antigravity Access via SSH

uname: command not found

/bin/bash (chrooted)

/bin/bash

Phase 2: Securing the Workspace Structure

httpdocs

/var/www/vhosts/mywebsite.com/httpdocs

httpdocs/public/

/httpdocs/core/src/modules

httpdocs

└── httpdocs                     <- Project root
    ├── public/                  <- PUBLIC: Your single webroot
    │   ├── style/               <- Shared across all subdomains
    │   ├── icons/               <- Shared across all subdomains
    │   └── sounds/              <- Shared across all subdomains
    └── core/                    <- PRIVATE: Your single Node.js engine
        ├── .antigravity/        <- Your instructions, log and todo markdown files
        │   └── CHANGELOG.md     <- For you to record completed work
        │   └── SKILLS.md        <- Your AI Agent skills.
        │   └── TODO.md          <- Current tasks, known bugs, and future ideas
        ├── src/
        │   ├── infrastructure/  <- Shared DB connection, Redis, Zod schemas
        │   ├── modules/         <- Strictly isolated domain boundaries
        │   │   ├── shop/
        │   │   ├── browse/
        │   │   ├── profile/
        │   │   ├── account/
        │   │   ├── contact/
        │   │   └── blog/
        │   └── index.ts         <- Express setup & Subdomain routing
        ├── templates/           <- EJS templates (layouts, partials for HTMX)
        └── package.json         <- Defines Postgres and Redis      

Phase 3: The AI Configuration Protocol

SKILLS.md

# Project Name: Antigravity Agent Skills & Engineering Standards

## 1. Architectural Philosophy & Core Directives
* **Architecture Pattern:** [Define your architecture here, e.g., Modular Monolith, Microservices, MVC].
* **Domain Isolation:** Code must be strictly separated into logical domains.
* **Performance Mandate:** [Define your performance baseline, e.g., HTTP responses <100ms, offload heavy tasks to background queues].

## 2. Technology Stack & Rules
* **Runtime & Language:** [e.g., Node.js 20+, TypeScript 5+].
* **Strict Typing:** NEVER use the `any` type under any circumstances.
* **Frameworks:** [Define your backend and frontend frameworks, e.g., Express.js, Tailwind CSS].
* **Absolute Restrictions:** [Define what the agent must NOT use, e.g., Do NOT use React or complex frontend build pipelines].

## 3. Data Persistence & Security
* **Database Engine:** [e.g., PostgreSQL 16+].
* **Validation:** Absolutely every piece of incoming data must be validated against strict schemas before interacting with the database.
* **Security Boundary:** All backend logic, routing, and configuration must remain private and inaccessible from the webroot.

## 4. Workflow, Documentation & Collaboration Protocols
As a complete coding partner, you must strictly adhere to the following operational lifecycle:
* **Pre-Flight Context Check:** Before commencing work on any new feature, you MUST locate and review the relevant specification documents. Never guess the requirements.
* **Propose Before Execution:** Do not write large blocks of code immediately. Propose a step-by-step implementation plan, discuss it, and await confirmation before executing the code.
* **Documentation Synchronisation:** The documentation is the single source of truth. If a discussion results in a new schema, route, or strategy change, you must update the relevant `.md` specification files immediately.
* **Progress Tracking:** Maintain two living documents in the root directory: `CHANGELOG.md` (to record completed work) and `TODO.md` (to track current tasks, known bugs, and future ideas). You must automatically update these files at the conclusion of every major task.

Phase 4: The Onboarding Prompt

SKILLS.md

We are starting a new project. Before we begin any development, you MUST read and ingest the .antigravity/skills.md file. This file contains our strict architectural boundaries, technology stack, security rules, and our operational workflow. Please confirm you have read it, and provide a brief summary of how you will approach our first task using the workflow protocols.

SKILLS.md