Antigravity 2.0 added /btw (by the way), so you can slip context in mid-task with a quick "by the way." It is handy. When an agent starts drifting slightly off course, a single line rights it without rewriting everything.
But this convenience has a trap. Pile everything into /btw and stopgap asides accumulate until the agent loses track of which rule is actually in force. Context does not help just because you add more of it. Context placed in the wrong spot lowers accuracy instead. This article builds a design that routes context into three layers and places each one correctly.
Context has three lifespans
You hesitate over "where to write context" because you are not attending to differences in lifespan. A rule you always want followed, an instruction just for this once, and a course-correction right now each have different lifespans. Put each where its lifespan belongs and the agent does not get confused.
| Layer | Lifespan | Where it lives | Example |
|---|---|---|---|
| Persistent rule | Always, across the whole project | AGENTS.md / Guide skill | "Write in polite form," "Tables as HTML," "Never touch production URLs" |
| Task instruction | For the duration of this work | The initial prompt | "This article's topic is X," "The target is Y" |
| In-the-moment aside | Just this one move | /btw | "By the way, that function name is stale; the new one is Z" |
The crux of this routing is: do not repeat a persistent rule in /btw every time. Repeating it every time is the signal that it belongs in the persistent layer.
The persistent layer is the "always-on foundation"
Write things you want honored across every piece of work in AGENTS.md, once. What you write here is always in force without restating it in /btw.
# AGENTS.md (excerpt)
## Always follow
- Write Japanese body text in polite form (desu/masu)
- Write tables as HTML <table>, not Markdown
- Never connect to the production host (app.example.com); verify on staging only
- Always format external links as [display text](URL) (no bare URLs)
## Output conventions
- Do not open with a boilerplate intro like "In this article"
- The conclusion is not a recap; write exactly one next stepA thin persistent layer forces you to re-add the same caution via /btw every time. A persistent layer that is too thick freezes one-off circumstances and gets in the way of other work. Use "is this true for every piece of work?" as your test, and place only what is always true.