Menü
<short summary>. Use when <trigger condition>.
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
| name | <kebab-case-skill-name> |
| description | <short summary>. Use when <trigger condition>. |
Use ONLY when the user explicitly asks for it — e.g. "explain this code," "walk me through this module/feature/API," "review this for me," "/explain-code," or points at a file/function/snippet and asks what it does. Produces a short, high-level report on existing (already-committed, no-diff) code: what it does, how it's structured, non-obvious behavior, edge cases, risk flags, open questions, and where to look next. Do NOT trigger automatically just because code is present in context or was recently discussed — wait for the user to ask.
Use ONLY when the user explicitly asks for it — e.g. "practice IELTS speaking", "IELTS speaking practice", "help me with IELTS", "IELTS part 1/2/3", or similar direct requests. Do NOT trigger on general mentions of IELTS or English speaking unless the user explicitly invokes this skill by name.
Use ONLY when the user explicitly asks for it — e.g. "mock interview me", "do a mock interview", "practice interview questions", "interview me", "drill technical Q&A", or similar direct requests. Do NOT trigger on general interview-related discussion unless the user explicitly invokes this skill by name.
Use ONLY when the user explicitly asks for it — e.g. "create a product brief", "flesh this out", "turn this idea into a product brief", or similar direct requests. Do NOT trigger on general product discussions or idea sharing unless the user explicitly invokes this skill by name.
Use ONLY when the user explicitly asks for it — e.g. "document this API", "hand off this endpoint", "prepare FE integration notes", or similar direct requests. Do NOT trigger automatically when documenting or summarizing code — wait for the user to ask.
Use ONLY when the user explicitly asks to enter brainstorming mode by name (e.g. "brainstorm first", "let's brainstorm", "start a brainstorming session"). Do NOT trigger on general discussion, questions, requests for suggestions, or solution exploration unless the user explicitly invokes this skill by name.
