Docs/added installation instructions for Google Antigravity users to the README. #281
Conversation
📝 WalkthroughWalkthroughUpdated README.md: replaced some emphasis markers, added a new "Google Antigravity" setup and installation subsection, expanded the Basic Workflow with explicit steps (including using-git-worktrees and finishing-a-development-branch), and broadened the Skills Library with several new collaboration-related skills and spacing/formatting refinements. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Fix all issues with AI agents
In `@README.md`:
- Line 90: Replace the hardcoded Windows path
"C:\Users\Administrator\.gemini\antigravity\skills" with a generic
user-dependent path; use the environment variable style (e.g.,
"%USERPROFILE%\.gemini\antigravity\skills") or a tilde-equivalent suggestion
(e.g., "~\.gemini\antigravity\skills") in the README so the path works for
non-Administrator accounts and matches the Mac/Linux pattern.
- Around line 78-94: Update the "Google Antigravity" README section by replacing
the invalid docs link with the official codelab URL (use
https://codelabs.developers.google.com/getting-started-google-antigravity) and
make the Windows skills path user-agnostic by changing the hardcoded
C:\Users\Administrator\.gemini\antigravity\skills to use the %USERPROFILE%
environment variable (e.g., %USERPROFILE%\.gemini\antigravity\skills) so the
"Google Antigravity" section and its bullet points are corrected.
🧹 Nitpick comments (3)
README.md (3)
78-94: Consider adding a verification step for consistency.Other installation methods (Claude Code, Codex, OpenCode) include verification steps to confirm successful installation. The Antigravity section would benefit from similar guidance.
💡 Suggested addition after step 3
Add a verification step:
4. Verify the installation by checking that your Antigravity agent recognizes the skills:Ask your agent: "What superpowers skills are available?"
You should see skills like `brainstorming`, `test-driven-development`, etc.
118-138: Consider using heading syntax for section labels.The "Testing", "Debugging", "Collaboration", and "Meta" labels are functioning as subsection headers but use emphasis (bold) instead of proper heading syntax.
Based on static analysis hints, for better semantic HTML and accessibility:
♻️ Proposed refactor
-**Testing** +#### Testing - **test-driven-development** - RED-GREEN-REFACTOR cycle (includes testing anti-patterns reference) -**Debugging** +#### Debugging - **systematic-debugging** - 4-phase root cause process (includes root-cause-tracing, defense-in-depth, condition-based-waiting techniques) - **verification-before-completion** - Ensure it's actually fixed -**Collaboration** +#### Collaboration - **brainstorming** - Socratic design refinement ... -**Meta** +#### Meta - **writing-skills** - Create new skills following best practices (includes testing methodology)
11-11: Consider formal language for the YAGNI expansion.The expansion uses "Gonna" which is informal. While this is a commonly used expansion in developer culture, the formal version would be more appropriate for documentation.
✏️ Proposed alternative
-After you've signed off on the design, your agent puts together an implementation plan that's clear enough for an enthusiastic junior engineer with poor taste, no judgement, no project context, and an aversion to testing to follow. It emphasizes true red/green TDD, YAGNI (You Aren't Gonna Need It), and DRY. +After you've signed off on the design, your agent puts together an implementation plan that's clear enough for an enthusiastic junior engineer with poor taste, no judgement, no project context, and an aversion to testing to follow. It emphasizes true red/green TDD, YAGNI (You Aren't Going to Need It), and DRY.
| ### Google Antigravity | ||
|
|
||
| For more details on managing skills, please refer to the [official documentation](https://antigravity.google/docs/skills). | ||
|
|
||
| 1. Clone this repository: | ||
|
|
||
| ```bash | ||
| git clone https://github.com/obra/superpowers temp_superpowers | ||
| ``` | ||
|
|
||
| 2. Copy the `skills` directory contents to your global skills directory: | ||
|
|
||
| - **Windows**: `C:\Users\Administrator\.gemini\antigravity\skills` | ||
| - **Mac/Linux**: `~/.gemini/antigravity/skills` | ||
|
|
||
| 3. (Optional) Clean up the temporary directory. | ||
|
|
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
Google Antigravity skills installation documentation directory path
💡 Result:
Common Antigravity skill locations:
- Workspace (project) scope: /.agent/skills/.[1][2]
- Global (user) scope (official doc): ~/.gemini/antigravity/skills/.[1][2]
- Note: some users report the runtime actually looks in ~/.gemini/antigravity/global_skills/ (create both if unsure). [3]
Sources: [1] Antigravity docs / Getting Started & Skills guides. [2] Medium tutorial on Antigravity Skills. [3] Community report showing the global_skills discrepancy.
🌐 Web query:
Google Antigravity .gemini directory configuration
💡 Result:
Short answer — Antigravity stores its local state and user/config artifacts in a .gemini folder (either in your project workspace and/or your home directory), and you can control agent behavior with simple files there (notably GEMINI.md plus subfolders like antigravity/brain and artifacts). See sources below for examples and community notes.
Quick facts / where to look
- Locations reported by users: ~/.gemini/antigravity (home) and a .gemini folder inside project workspaces. [1][2]
- What’s inside: artifacts, conversation/chat data, “brain” memory, and configuration files used by Antigravity agents. Users report task lists, artifacts and chats are stored under .gemini/antigravity/brain and related subfolders. [1][3]
- GEMINI.md: a plaintext Markdown file in the .gemini directory that many users place rules/instructions into (eg. agent safety rules, “never auto-execute” style constraints). Antigravity will read that file as a source of agent instructions/constraints. [1][4]
- Related config examples: some community tools and opencode plugins show Antigravity-related model/provider config and naming conventions (e.g., antigravity- prefixes and model entries) in JSON config (opencode example). That config is separate from the .gemini runtime folder but helpful when integrating CLI/plugins. [5]
Practical tips
- Check both ~/.gemini and project-root/.gemini if you can’t find artifacts. User reports show both places are used. [1][3]
- Back up .gemini before experiments — users report lost/vanishing conversations when reinstalling or switching models. [3]
- To add global agent rules, create/edit .gemini/GEMINI.md with line-by-line constraints (e.g., “NEVER execute terminal commands without explicit confirmation”). Keep it plain text/Markdown. [1]
Sources
- User reports and GEMINI.md examples — Reddit threads discussing .gemini, GEMINI.md, and artifact locations. [reddit.com threads].
- Reports of Antigravity storing chats/artifacts in ~/.gemini/antigravity. [reddit.com].
- Thread reporting artifacts & “brain” folder location in .gemini. [reddit.com].
- News/overview of Google Antigravity (agent-first IDE) — context on features that write artifacts. (The Verge).
- opencode GitHub example showing Antigravity-related model/provider JSON configuration patterns.
If you want, tell me your OS and whether you’re looking for the project-local .gemini or the user ~/.gemini and I’ll show exact paths and an example GEMINI.md template you can drop in.
🌐 Web query:
site:google.com Antigravity skills setup
💡 Result:
You can set up Antigravity (Google’s Antigravity IDE/agents) and configure skills by following Google’s getting-started codelab and Cloud blog guidance. Key steps:
- Install Antigravity and sign in with a Google account, then run the Setup Wizard (includes editor preferences, browser extension, and optional CLI). (codelabs.developers.google.com)
- Configure agent “skills” via the Agent Manager / Editor: choose models, enable browser subagent and extensions, and set editor keybindings and extensions. (codelabs.developers.google.com)
- Connect data and skill integrations using MCP servers (install MCP connectors for BigQuery, AlloyDB, Cloud SQL, etc.) so agents can access your data as skills. (cloud.google.com)
- Use the security controls (Terminal Auto-Execution policy, Allow/Deny lists, and browser permissions) to safely permit agent actions. (codelabs.developers.google.com)
If you want, I can open the specific Google codelab or Cloud blog page and extract the exact commands and UI paths for your OS and account—shall I do that?
Citations:
- 1: https://codelabs.developers.google.com/getting-started-google-antigravity?utm_source=openai
- 2: https://codelabs.developers.google.com/getting-started-google-antigravity?utm_source=openai
- 3: https://cloud.google.com/blog/products/data-analytics/connect-google-antigravity-ide-to-googles-data-cloud-services?utm_source=openai
- 4: https://codelabs.developers.google.com/getting-started-google-antigravity?utm_source=openai
Fix the documentation URL for Google Antigravity.
The link https://antigravity.google/docs/skills does not appear to be a valid Google Antigravity documentation URL. According to official Google sources, use the codelab at https://codelabs.developers.google.com/getting-started-google-antigravity instead.
Additionally, the Windows path hardcodes C:\Users\Administrator\.gemini\antigravity\skills, which assumes a specific username. Use an environment variable like %USERPROFILE% to make it user-agnostic (e.g., %USERPROFILE%\.gemini\antigravity\skills).
🤖 Prompt for AI Agents
In `@README.md` around lines 78 - 94, Update the "Google Antigravity" README
section by replacing the invalid docs link with the official codelab URL (use
https://codelabs.developers.google.com/getting-started-google-antigravity) and
make the Windows skills path user-agnostic by changing the hardcoded
C:\Users\Administrator\.gemini\antigravity\skills to use the %USERPROFILE%
environment variable (e.g., %USERPROFILE%\.gemini\antigravity\skills) so the
"Google Antigravity" section and its bullet points are corrected.
1 participant
Added installation instructions for Google Antigravity users to the README.
Motivation and Context
The current
README.mdprovides installation steps for Claude Code, Codex, and OpenCode, but lacks instructions for Google Antigravity.As Antigravity also supports file-based skills, this update adds a dedicated section to guide Antigravity users on how to install and use this skill suite (by cloning and copying to the global skills directory).
It also includes a link to the official Antigravity Skills documentation for further reference.
How Has This Been Tested?
skillsdirectory toC:\Users\Administrator\.gemini\antigravity\skillsallows the Antigravity agent to recognize and use the skills (e.g.,brainstorming).Breaking Changes
No.
Types of changes
Checklist
Additional context
This enables the "Superpowers" workflow (Brainstorming, TDD, etc.) to be easily adopted by the growing Google Antigravity community.
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.