What Doesn't Belong in a Persistent Instruction
A free lesson from Swipe AI · Prompt Engineering, level 2 · updated October 2026
By the Swipe team, founded by Colin · how we make lessons
Just as important as knowing what belongs in a persistent instruction is knowing what doesn't. Anything that changes from request to request — the actual subject matter, the specific document, the particular question — has no business living in the persistent layer, because it will be wrong or irrelevant the very next time you use the tool.
The name of today's client, the specific paragraph you need rewritten, the particular error message you're debugging, the exact recipe you're adapting — these are all one-time details. They belong in the user message precisely because next time they'll be completely different.
Bury a one-time detail inside the persistent layer, and it silently attaches itself to every unrelated future request. Ask an AI tool to 'always compare this to last year's Q3 numbers,' set as a persistent instruction, and it'll keep trying to bring up Q3 numbers even when you're asking about something totally unrelated six months later.
Belongs only in a user message (changes every time): - The specific email you want rewritten - The meeting agenda for today - The complaint from this one customer - The particular code file with the bug
Why is a specific one-time detail, like the exact document you want summarized today, a bad fit for a persistent instruction?
A detail that changes every time you use a tool, like the exact document to summarize, belongs in the ____ message, not the persistent instruction.
It is fine to put a one-time task detail into a persistent instruction, since you can always delete it later.
Free ai tools
Keep your streak going in Swipe AI
Swipe through every level of Prompt Engineering on your iPhone — with XP, stars, streaks, a personal advisor and the full track beyond these free levels.
Get the Swipe apps →