Module 03: Global vs. Local: The Hierarchy of Control

As you work across multiple projects, different repositories require radically different tech stacks, coding styles, and deployment targets. Antigravity solves this with a strict, predictable configuration hierarchy.

1. The Three Layers of Intelligence

Antigravity structures its operating environment across three clear tiers:

• Rules (Behavioral Laws): Absolute constraints the agent must obey on every prompt without exception (e.g., conventional commits, file size boundaries).
• Skills (Procedural Playbooks): Context-aware tools and guides loaded on-demand when matching keywords or intents are detected.
• MCP Servers (System Interfaces): Live JSON-RPC protocol bridges providing tool calls into databases, cloud consoles, browser drivers, and hosting APIs.

2. Global vs. Local File Layout

Global Configuration (Applies to all workspaces):
~/.gemini/antigravity/
├── config/
│   ├── skills/          # Global skills accessible across all projects
│   └── plugins/         # Global installed plugins
└── user_rules           # Global invariant rules (e.g., RULE[user_global])

Local Workspace Configuration (Project-specific):
your-project-root/
├── .gemini/
│   ├── rules/           # Local rules (overrides global defaults)
│   └── skills/          # Local project-specific scripts and workflows
└── package.json / .env  # Project files

3. The Rule Resolution Hierarchy

When Antigravity initializes, it evaluates rules in a deterministic priority order:

1. Active User Prompt Constraints: Real-time instructions provided in the current turn.
2. Workspace Local Rules (.gemini/rules/): Project-specific design standards, directory conventions, and language versions.
3. Global User Rules (RULE[user_global]): Fundamental engineering standards that apply across all projects.
4. System Default Guidelines: Antigravity's core safety and programming baseline.

4. Production Template for user_global

Here is an battle-tested global rule set for sovereign engineers:

<RULE[user_global]>
# Sovereign Engineering Guardrails
1. Responsive First: All UI code must adapt progressively across mobile, tablet, and desktop.
2. Modular Architecture: Never let code files exceed 300 lines; refactor common logic into helpers.
3. Security First: Never hardcode credentials. Leverage .env or host environment variables.
4. Conventional Commits: All git commits must follow standard format: type(scope): description.
5. Verbose Thinking: Briefly explain architectural choices and trade-offs before executing code.
</RULE[user_global]>