Operating rules, process patterns, and anti-patterns distilled from real AG Run Pad execution cycles. Copy any rule directly for use in Notion or handoff pages.
A single user may work across many skills and projects with Antigravity.
Use one global AG Run Pad as the temporary operating surface. Archive only distilled outcomes to skill/handoff pages.
One global AG Run Pad for all Antigravity work. Archive finished lessons to skill pages.
Parallel context causes drift in both the model and the human reviewer.
Focus is paramount. Only after one task is finished, verified, and distilled can you reset the pad for the next slice or project.
Keep a single active run context. Close and archive before opening a new one.
Cheap models can drift if given wide command access.
Notion writes a bounded prompt. Antigravity confirms workspace then runs exactly one whitelisted command. Human reviews output before granting next command.
One command per human approval when the command overwrites outputs.
MCP tools expose extra capabilities and schema context beyond what is needed.
Add an explicit MCP policy to every Antigravity prompt. MCP is gated by prompt. Local test runs explicitly say no MCP; Notion sync prompts must target exactly one page.
MCP enabled does not mean MCP allowed for every run.
Antigravity workspace may be opened at the wrong path.
Every prompt requires Antigravity to confirm the workspace root before running any command. If the path is wrong, stop and report BLOCKED.
Always include a workspace path gate before any local command.
Cheap executor models try to plan beyond scope when given too much latitude.
Notion AI (Tilog) acts as planner/reviewer. Antigravity is the bounded executor. Each role has strict output contracts.
Use files allowed / commands allowed / output contract to constrain executor.
AG Run Pad accumulates stale context as slices close.
After a run completes verification, distill the key learnings and move them to the appropriate skill/handoff page. Keep the Run Pad lean.
Archive finished lessons to skill/handoff pages. The Run Pad is a workbench, not an archive.
Creating a separate Run Pad for each project or slice.
Multiple Run Pads clutter Notion and make the workflow harder to teach and maintain.
Do not create `AG Run Pad · [project]` pages. Use the single global Run Pad instead.