NotebookLM + Antigravity started working way better for me when I stopped using them the obvious way
I kept running into the same problem using AI for coding stuff:
I’d ask for something small → get an answer
Then ask for the next thing → it kind of forgets
Then I have to explain everything again
After a while it just feels slow and… weirdly inefficient.
---
I didn’t change tools.
I just changed how I use them.
---
What I started doing instead:
I dump everything into NotebookLM first.
Not just code, but also:
- rough ideas
- random notes
- half-baked architecture decisions
Basically anything that gives context.
Then instead of asking for small things, I ask for a full breakdown in one go.
Like “what would this feature actually look like end-to-end?”
---
The difference is bigger than I expected.
NotebookLM feels way more stable when it has all the context loaded.
It doesn’t feel like I’m restarting the conversation every 2 prompts.
---
Then I take that output and move to Antigravity.
At that point I’m not asking it to think.
Just to execute parts of what’s already defined.
---
That separation helped a lot:
NotebookLM → thinking
Antigravity → doing
---
Before it felt like:
ask → answer → lose context → repeat
Now it’s more like:
load context once → think properly → execute step by step
---
I’m using fewer prompts overall and getting more consistent results.
Nothing crazy or “hacky”.
Just stopped trying to do everything in one place.
---
Curious if anyone else is doing something similar or if I just overcomplicated this for no reason.
Posted May 5, 2026, 5:28 PM UTC