Skip to content

antigravity-setup.md

Latest commit

 

History

History
184 lines (126 loc) · 6.89 KB

antigravity-setup.md

File metadata and controls

184 lines (126 loc) · 6.89 KB
Raw

Setup: Antigravity CLI

Integration guide for using test-automation-skills-agents with Antigravity CLI (agy).

Note: Antigravity CLI replaces Gemini CLI as of June 18, 2026. If you are migrating from Gemini CLI, run agy plugin import gemini to convert your existing extensions. Your GEMINI.md context file keeps working — Antigravity CLI reads it natively.

Installation

Option A: GEMINI.md Configuration (Recommended)

Add to your project's GEMINI.md:

## QA Automation Skills & Agents

This project uses test-automation-skills-agents for QA automation guidance.

### Key Conventions

- Playwright (TypeScript) for E2E and API testing
- Selenium + REST Assured (Java 21+) for Java-based testing
- Custom fixtures for dependency injection (Playwright)
- Explicit waits with WebDriverWait (Selenium) — never Thread.sleep()
- Follow Test Orchestration Pattern for AI-driven test workflows

### Skills Location

Skills are in: /path/to/test-automation-skills-agents/skills/
Agents are in: /path/to/test-automation-skills-agents/agents/
Instructions are in: /path/to/test-automation-skills-agents/instructions/

Option B: Clone and Reference

git clone https://github.com/fugazi/test-automation-skills-agents.git

Then reference specific files in your Antigravity CLI sessions:

"Read /path/to/test-automation-skills-agents/skills/playwright-e2e-testing/SKILL.md and follow its workflow to write tests for the login page"

Option C: Copy into Project

Copy the skills and instructions you need directly into your project:

# Copy skills to .agents/skills/ (Antigravity convention)
cp -r test-automation-skills-agents/skills/ .agents/skills/

# Copy instructions
cp -r test-automation-skills-agents/instructions/ .agents/rules/

# Copy agents
cp -r test-automation-skills-agents/agents/ .agents/agents/

Reference these directories in your GEMINI.md.

Option D: Migrate from Gemini CLI

If you have an existing Gemini CLI setup:

# One-command migration of extensions
agy plugin import gemini

# Move workspace skills to the new location
mv .gemini/skills/ .agents/skills/

Your GEMINI.md keeps working as-is.

How Skills Work with Antigravity CLI

Antigravity CLI discovers skills through configuration. The SKILL.md frontmatter description field tells Antigravity when to activate each skill. Skills are loaded from:

  • Global: ~/.gemini/config/skills/
  • Project: <project-root>/.agents/skills/

To enable skill auto-discovery, list your skills in GEMINI.md:

### Available Skills

| Skill                          | When to Use                                |
| ------------------------------ | ------------------------------------------ |
| playwright-e2e-testing         | Writing Playwright E2E tests               |
| api-testing                    | Creating REST/GraphQL API tests            |
| webapp-selenium-testing        | Writing Selenium Java tests                |
| a11y-playwright-testing        | Accessibility testing with Playwright      |
| accessibility-selenium-testing | Accessibility testing with Selenium        |
| playwright-regression-testing  | Regression suite strategy and optimization |
| qa-manual-istqb                | QA artifacts and ISTQB test design          |
| grill-me-qa                    | Adversarial review of QA strategies/plans  |
| playwright-cli                 | Browser automation via CLI                 |

Activating Skills

Reference skills explicitly in your Antigravity CLI prompts:

"Follow the playwright-e2e-testing skill to create tests for the checkout flow"
"Use the api-testing skill to design REST Assured tests for the /orders endpoint"
"Apply the a11y-playwright-testing skill to audit the login page for WCAG compliance"

Using Agents

Reference agent files in your Antigravity session:

"Read agents/playwright-test-planner.agent.md and use that persona to create a test plan for the user registration flow"

Or paste agent content directly:

"Act as the Playwright Test Healer agent defined in agents/playwright-test-healer.agent.md. Investigate why this test fails intermittently:

[Test code or error output]"

Agent Quick Reference

Agent Invocation
Playwright Test Planner "Use the playwright-test-planner agent to create a test plan for..."
Playwright Test Generator "Use the playwright-test-generator agent to generate tests from this plan..."
Playwright Test Healer "Use the playwright-test-healer agent to fix this failing test..."
API Tester Specialist "Use the api-tester-specialist agent to design API tests for..."
Selenium Test Specialist "Use the selenium-test-specialist agent to create Java tests for..."
QA Orchestrator "Use the qa-orchestrator agent to coordinate this multi-step testing workflow..."
Test Refactor Specialist "Use the test-refactor-specialist agent to refactor this test suite..."

Customization

Project-Specific GEMINI.md

Tailor the configuration to your project:

## QA Automation Configuration

### Tech Stack

- Framework: Playwright 1.40+
- Language: TypeScript 5.x
- Runner: @playwright/test
- Base URL: http://localhost:3000

### Conventions

- Page Objects in: src/pages/
- Tests in: tests/
- Fixtures in: tests/fixtures/
- Test data via: environment variables

### Agent Preferences

- Default agent: playwright-test-generator
- For flaky tests: playwright-test-healer
- For API work: api-tester-specialist

Skill Selection

Only reference the skills relevant to your project:

  • Playwright + TypeScript project: playwright-e2e-testing, api-testing, a11y-playwright-testing, playwright-regression-testing
  • Selenium + Java project: webapp-selenium-testing, accessibility-selenium-testing, api-testing
  • Mixed stack: Include all relevant skills

Tips

  • GEMINI.md is your entry point. Antigravity CLI reads it natively. Keep it concise but specific.
  • Reference files, don't paste them. Use file paths in prompts — Antigravity CLI can read files directly.
  • Use the agent pattern. Start with "Read agents/[name].agent.md and use that persona" for consistent specialist behavior.
  • Combine skill + instruction. "Follow the playwright-e2e-testing skill AND the playwright-typescript instructions" gives Antigravity the most context for high-quality output.
  • Accessibility: use skills (a11y-playwright-testing, accessibility-selenium-testing) instead of instructions — they load on-demand and include deeper content.
  • Migrating from Gemini CLI: run agy plugin import gemini and move .gemini/skills/ to .agents/skills/.