Menü
Display all stored trigger phrases from .claude/triggers.json
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Full operating manual for working in a codebase with the user. Use this skill at the start of any substantial task, when the user asks how to approach work, or when setting up a collaboration session. Covers the core craft principles, user interaction model, rule conflict resolution, code quality (broken windows), when to stop, and which rules apply for each task type. Read in full at every load. This skill defines the substrate the methodology operates from; partial reading or summarization produces no substrate. Use proactively — don't wait to be asked.
Self-eval the agent runs when it suspects memory-vs-recall drift — the failure mode where memory-citation substitutes for fresh receipt-fetching and pattern-copying outruns reachability analysis. Outputs a tiered recommendation (continue / slow down / refresh) backed by observable artifacts, not introspective claims alone. Invoke when: - You notice yourself reaching for "I remember from earlier" framings repeatedly - You catch yourself copying a pattern from a sibling module without walking conditions - You make the same class of mistake twice in close succession - User suggests fatigue ("how are you feeling?", "still sharp?") - End of long working stretch - User invokes explicitly via `/check-yo-self`
Quick reference for which rules govern the current work. Consult mid-task when starting a new task type, touching unfamiliar code, or unsure which constraints apply. Pairs with the-craft skill (full manual). Trigger on: "which rules apply", "what rules should I follow", "check constraints", or proactively when switching task type mid-session. Also use when any two rules appear to conflict — the always-on rules explain precedence.
Run cross-model comparison — scan files with haiku, sonnet, and opus study agents to see how model size affects trigger phrase generation.
Remove trigger phrases for a file or glob pattern from .claude/triggers.json
Study files and generate semantic trigger phrases by spawning a researcher agent that samples model associations and finds convergent patterns. Supports model-specific triggers via --models flag.
| name | list |
| description | Display all stored trigger phrases from .claude/triggers.json |
| allowed-tools | Read |
Read .claude/triggers.json. If it doesn't exist, report "No triggers stored yet. Run /total-recall:scan to generate some."
If the user provided a filter pattern (e.g., src/auth), only show entries whose file path contains that pattern.
Display as a formatted table — one row per (file, model) pair so per-model phrases and confidences are both visible:
File | Model | Trigger Phrase | Confidence | Scanned
--------------------------- | ------ | ------------------------------ | ---------- | ----------
src/auth/middleware.ts | sonnet | jwt route authentication guard | 0.90 | 2026-03-31
src/auth/middleware.ts | opus | jwt bearer token route guard | 0.98 | 2026-03-31
src/db/connection.ts | sonnet | database connection pool mgmt | 0.85 | 2026-03-31
For v1 (legacy) entries with a flat phrase field, render the row with Model = (legacy).
N triggers stored across M files (K model-entries).crossModelTerms.< 0.7 — these are candidates for resonance-lint review (see README).