antigravity-protocol

Use a protocol that bans full-file rewrites and conversational preambles, requiring chunk-based search-and-replace edits against exact line numbers. Large tasks go through a plan artifact first, and substantial output is moved into local Markdown files instead of chat.

Strict Planning Mode requires the assistant to silently trace dependencies, write an implementation_plan.md listing files as [NEW], [MODIFY], or [DELETE], then halt for user approval before executing any code changes via a task.md checklist.

Yes, the verification phase runs the project's own build or test command such as npm run build or flutter test after edits. Terminal commands are restricted to tests, servers, and package installation only.

Generic shell commands for reading or editing files consume excessive tokens and produce imprecise results. The protocol enforces a tool hierarchy prioritizing built-in read, search, and edit tools, reserving the terminal for builds and tests.

Avoid it for open-ended exploration, learning-oriented explanations, or tasks needing detailed discussion of tradeoffs. The protocol suppresses explanatory output and stops to ask questions rather than reasoning through ambiguity at length.