give-me-tips

# give-me-tips - explain any senpi tip, in depth ## Purpose Senpi shows the user tips: startup tips, working tips, and `Tip:` lines injected by omo components. When the user asks about any of them - "what was that Tip: line", "what does this tip mean", "how does that feature work" - this skill produces a DEEP explanation of that exact tip, in the USER'S language (match the language they asked in, always). Specific over generic, every time. "It retries on failure" is a failure of this skill. "It detects the refusal from the stopDetails on the assistant message_end event, gates on the architect category in your .omo/omo.json, and only then injects the directive" is the bar. The user asked because the tip made them curious; reward that curiosity with the real mechanism, not a summary of the tip text they already read. ## Query the live tip list FIRST Never explain from memory. Get the ground truth of what tips exist: 1. Run `senpi --list-tips`. It prints JSON: `[{id, text, requiresCommand?}]`. Match the user's tip against this list by id or by text fragment. 2. If the flag is unavailable on this senpi version, fall back to reading the catalog sources directly at `packages/coding-agent/src/modes/interactive/tips/catalog/` inside the installed `@code-yeongyu/senpi` package (find it via the senpi install path or node_modules) or in a local clone of code-yeongyu/senpi. Then - and this is the part most explanations get wrong - **available tips DIFFER per user**. Th...