القائمة
Use when Emu fires a Drift Alert. Explains what drift means and how to break out. Auto-triggers on: "drift alert", "going in circles", "stuck", "keeps reading same file", "test won't pass".
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Reconstructs session working state from the last saved checkpoint and remember.md. Use immediately after compaction when context is lost. Auto-triggers when: files being edited are unknown, project instructions are unclear, or user says "what happened" / "what were we doing".
Auto-loads when context usage feels high or compaction is approaching. Teaches token-efficient behavior. Triggers on: "context is low", "running out of space", slow responses, or after 30+ turns in a session.
Reduces output token usage by injecting terse-mode instructions. Removes filler phrases, trailing summaries, and converts prose to bullets. Configurable: off / lite / full / ultra. Auto-triggers at session start or when context is running low.
Reference when user asks why output was truncated or how to bypass compression. Also use before every bash command compression decision.
| name | drift-awareness |
| description | Use when Emu fires a Drift Alert. Explains what drift means and how to break out. Auto-triggers on: "drift alert", "going in circles", "stuck", "keeps reading same file", "test won't pass". |
| allowed-tools | ["Read","Grep","Bash"] |
<decision_tree> IF pattern is "read_loop": The file doesn't have what you're looking for. → Ask: "What specific info are you searching for in [file]?" → Try: search the codebase with grep instead of re-reading. → Try: ask the user for context you might be missing.
IF pattern is "edit_revert": You're oscillating between two solutions. → Pick approach A. Implement it fully. Run tests. → If A fails completely, THEN try B. Don't alternate. → /emu:checkpoint the current state before switching.
IF pattern is "test_fail_loop": The same approach won't produce a different result. → Read the error output carefully — what changed? → If nothing changed: the fix isn't addressing root cause. → Try: explain the error to the user and ask for guidance. </decision_tree>
<escalate_to_sonnet> IF drift pattern is unclear or mixed: "ESCALATE_TO_SONNET: ambiguous drift pattern" IF user is frustrated and needs human-quality response: "ESCALATE_TO_SONNET: user frustration, needs empathy" </escalate_to_sonnet>
