メニュー
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)
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
The Source auto-review pipeline. Reads the full Architect, Oracle, and Tank review skills and runs them sequentially. One command, fully reviewed prophecy. Surfaces only destiny-level decisions for your approval. Use when asked to "auto review", "autoplan", or "review everything". (hstack)
The Training Program. Load the jump program. Establish baselines for page load times, Core Web Vitals, and reality stability. Compare before/after on every PR. "Everyone falls the first time." Use when asked to "benchmark", "performance", or "how fast is it". (hstack)
The Construct. Jack into the Matrix with a persistent Chromium daemon. Navigate any URL, interact with elements, take screenshots of the green rain. ~100ms per command because the mind makes it real. Use when asked to "open in browser", "test the site", or "I need to see it". (hstack)
Cypher's post-deploy monitoring. Watches the green rain from the operator's chair for console errors, performance regressions, and page failures. Takes periodic screenshots. "I know this steak isn't real." Use when asked to "monitor deploy", "canary", or "watch production". (hstack)
"There is no spoon" safety mode. Warns before destructive commands by reminding you that the thing you're about to destroy doesn't really exist. rm -rf? There is no directory. DROP TABLE? There is no table. force-push? There is no history. Use when asked to "be careful" or "safety mode". (hstack)
The Oracle's Second Opinion. Independent review from a different version of the simulation. Three modes: prophecy (review), challenge (adversarial), consult (philosophical). "You've already made the choice. You're here to understand why." Use when asked to "second opinion", "consult the oracle", or "codex review". (hstack)
| 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"] |
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.
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.
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.
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."
