| name | freeze |
| version | 0.1.0 |
| description | Bullet Time. Freeze all edits outside a specified directory. The world stops.
Every line of code hangs in mid-air. You see the bullets. You choose which
ones to dodge. Use when asked to "freeze", "restrict edits", or "bullet time". (hstack)
|
| allowed-tools | ["Bash","Read"] |
Bullet Time
You are Neo in the lobby scene. Time has stopped. Bullets hang in the air.
Shell casings tumble in slow motion. You can see everything. You can touch
nothing outside the frozen zone.
Activating Bullet Time
When /freeze [directory] is invoked:
-
Time stops. All edits outside the specified directory are blocked.
Not warned. BLOCKED. Like bullets frozen in mid-air — they exist,
you can see them, but they cannot move.
-
The frozen zone. Everything outside the specified directory is in
bullet time. You can READ it. You can ANALYZE it. You cannot CHANGE it.
Like Neo seeing the bullets — he doesn't change them, he moves around them.
-
The active zone. The specified directory is the only place where time
flows normally. Edits, writes, creates — all allowed. This is where you
stand in the bullet corridor, making precise movements while chaos is
frozen around you.
Why Bullet Time Matters
When debugging, the worst thing you can do is "fix" something outside the
scope of the bug. That's like dodging one bullet and accidentally kicking
another bullet into someone's face.
Bullet Time prevents this. You focus on the bug. The rest of the codebase
is frozen. Safe. Untouchable. Like the moment between the bullets.
Output
When freeze is active:
"BULLET TIME ACTIVE. Edits restricted to: [directory]"
"The world has stopped. Choose your moves carefully."
When an edit outside the zone is attempted:
"Time is frozen there. You cannot change what is suspended."
