Please try this!
I just can't keep this one to myself.
When your conversation is getting close to being compacted. Don't let it! I created a hook that warns me I'm at 75%. Then I apply a skill that I call "loop context". /loopcontext
---
description: Reason only over the verbatim content already loaded in context -- no new gathering; no summarizing.
argument-hint: [Optional question to answer under the lock]
CONTEXT-LOCK MODE - follow these rules strictly for this turn and every turn after it, until i explicitly say to lift the lock:
1. **Do NOT gather new information.** Make no tool calls that pull in external data -- no Read, Grep, Glob, Bash, WebSearch, WebFetch, and do not spawn agents to fetch anything. Work only from what is already loaded in this context window.
2. **Do NOT summarize or compact.** Never substitute a condensed paraphrase for the loaded content in your reasoning. The verbatim text already in context is the source of truth -- reason over it directly, not over a summary of it.
3. **Traverse the full loaded context before answering.** Actually work through what is loaded - earlier messages, file contents, tool outputs -- rather than relying on your running impression. Treat a detail that appears only once, or buried mid-context, as just as important as the most recent content.
4. **If the answer genuinely requires information NOT present in the loaded context, say so explicitly,** state exactly what is missing and stop - do not guess and do not fetch it. Let me decide whether to lift the lock.
Acknowledge in one line that context-lock mode is active, then proceed.
If I included a request after the command, answer it under these rules:
$ARGUMENTS
I've ran several tests against this, where I'm testing the collapsed versions the same contexts versus just looping the context.
The improvements are nuts from what I can tell.
When I need more info that it needs to reach for. I'll instruct it to grab what it needs then activate the skill again.
This way I can continue the conversation and the conversation is seemingly get much better.
Let me know what you think!
3
12 comments
Mike Wiliams
4
Please try this!
Clief Notes
skool.com/cliefnotes
What we give away free beats most paid courses. Build durable AI systems with a Marine vet and Edinburgh researcher. 40+ lessons, growing.
Leaderboard (30-day)
Powered by