Antigravity Tool Guide
Updated July 2026
Antigravity is an AI coding workspace. PromptDC Desktop rewrites selected requests in place in Antigravity and also works in the integrated terminal.
Antigravity tool guide
Rewrite prompts in place inside Antigravity.
Works everywhere
PromptDC Desktop works in any app on Mac or Windows. The Chrome extension covers any website.
In-Place Rewrites
Transform rough notes into clear, structured instructions instantly.
See PromptDC in Action
This demo shows the standard PromptDC flow, and it works the same way in Antigravity.
Why Use PromptDC with Antigravity?
What changes when you rewrite prompts with PromptDC inside Antigravity.
Rewrite in Antigravity
Select a draft in Antigravity, press Command+Shift+E on Mac or Ctrl+Shift+E on Windows, review the rewrite, and choose Replace.
Structured Antigravity Requests
The Code profile turns a rough Antigravity request into implementation-ready instructions covering task, files, constraints, edge cases, and acceptance checks.
Integrated Terminal
PromptDC Desktop also rewrites selected text in the integrated terminal, so you can refine shell or coding instructions without leaving Antigravity.
Default Profile for Antigravity
Set Code as the default profile for Antigravity, and assign per-profile shortcuts for other rewrite tasks.
Reusable Project Rules
Use Always Include to carry repository conventions, protected files, and required commands into each Antigravity rewrite.
Formats and Languages
Choose Text, JSON, XML, or YAML for the rewritten Antigravity request, and select its output language.
Before and after prompts for Antigravity
See how specific context, constraints, and outcomes turn a rough request into a prompt Antigravity can act on.
Repair a Next.js checkout
Before PromptDC
Fix the checkout page. It sometimes submits twice.
After PromptDC
Task: Stop duplicate checkout submissions in a Next.js 15 app. Files: app/checkout/CheckoutForm.tsx and app/actions/orders.ts. Keep the Server Action and Stripe flow; add no dependencies. Handle rapid clicks, pending state, and action errors. Acceptance: one order, disabled pending button, regression test.
Why this is better: Exact files, versions, constraints, edge cases, and acceptance criteria give the coding agent a testable finish line.
Trace an auth regression
Before PromptDC
Login broke after my changes. Find out why.
After PromptDC
Investigate the auth regression introduced by the last commit. Inspect middleware.ts, app/login/page.tsx, and lib/auth/session.ts. Reproduce with an expired cookie and with no cookie. Report the root cause before making the smallest safe fix. Run auth tests and list every changed file.
Why this is better: A bounded investigation and evidence-first sequence reduce speculative edits.
Migrate an API client
Before PromptDC
Update our API client to the new version.
After PromptDC
Migrate src/lib/api/client.ts from Acme SDK v2 to v3. Update call sites under src/features/billing only. Preserve BillingResult and the current retry behavior. Do not touch generated files or unrelated lint issues. Acceptance: typecheck and billing tests pass with the v3 error shape.
Why this is better: Version scope, compatibility rules, exclusions, and checks make the migration safe.
Frequently Asked Questions
Learn shortcuts & usage?
Read the shortcuts docs
Need assistance with Antigravity?
Contact help & support
Write better with AI
Enhance any text you select on the desktop, on the web, in your editor or terminals.
Download PromptDC