kit

Use when the user wants to learn a technical topic through structured, multi-session tutoring with prerequisite tracking and knowledge graphs. Activates on "I want to learn X", "teach me X", "let's study X", or resuming a previous learning session. Do NOT activate for quick reference lookups or one-off coding questions — only for sustained learning goals.

Use when the user mentions 'hamsurang presentation', 'hamsurang PPT', 'hamsurang slide', '함수랑 발표', '함수랑 슬라이드', '함수랑 PPT', 'hamsurang 발표', or any presentation request in a Hamsurang (함수랑산악회) context — even if they don't explicitly say 'slide'.

Use when the user wants to manage velog.io blog posts from the terminal. Activates when the user mentions velog, wants to publish a blog post, list their velog posts, create or edit articles, manage drafts, or check trending posts on velog.io. Also use when the user writes markdown content and wants to publish it as a blog post, or when they ask about their velog account status. Even if they just say "post this to my blog" or "publish this", consider activating if velog-cli is installed.

Use when the user explicitly requests their personal vault notes as conversational context. Activates on "이전에 정리한 거 있어?", "내 노트 참고해서 답해줘", "check my notes about", "I wrote something about this before", "what do my notes say about". Do NOT trigger for vault management (creating, moving, editing, searching notes) — those belong to the obsidian skill. Do NOT trigger for generic Obsidian or Zettelkasten questions.

Use when the user mentions Obsidian, vault, daily notes, wikilinks, frontmatter, backlinks, graph view, or obsidian-cli. Activates for searching, creating, editing, moving notes in an Obsidian vault, managing YAML frontmatter, setting up Zettelkasten vault structure, or syncing vaults via Obsidian Headless (ob CLI). Also trigger on Korean phrases like "노트 만들어줘", "vault 동기화", or "frontmatter 수정해줘". Do NOT trigger for generic Markdown editing (README, docs) or other note apps (Notion, Bear). Do NOT activate when the user wants to use vault notes as conversational context (e.g., "내 노트 참고해서 답해줘", "check my notes about X", "이전에 정리한 거 있어?") — that belongs to the obsidian-brain skill.

Use when the user asks questions about a GitHub repository's architecture, API, or internals, or mentions deepwiki-cli or DeepWiki. Activates when the user needs to understand a codebase they haven't cloned locally, or asks how a library or framework works. Do NOT activate for local codebases already accessible on disk or private repositories.

Use when working with GitHub from the command line using the gh CLI tool. Trigger on "create PR", "open pull request", "list issues", "check CI", "merge PR", "review PR", "create issue", "release", "gh auth", "clone repo", "fork repo", "close issue", "view workflow run", or any GitHub operation from the terminal. Do NOT trigger for GitHub web UI actions or direct REST API calls without gh.

Use when the user wants to contribute to an open-source library, says "analyze this library for contribution", "I want to contribute to X", "help me contribute to", "contribution readiness", or "기여하고 싶다". Do NOT activate for general "how does X work" questions (use deepwiki-cli instead).

Use when reviewing a skill file for quality before publishing, merging, or deploying to a marketplace. Triggers on "review this skill", "skill review", "check my SKILL.md", "review the skill at [path]", or when the user wants structured feedback on whether a skill meets best practices.

Use when the user asks to write, run, or debug tests using Vitest, asks about vitest.config.ts or vite.config.ts test configuration, asks how to mock modules, functions, timers, or globals with the `vi` utility, asks about test coverage setup or thresholds, references Vitest API (describe, it, test, expect, beforeEach, afterAll, etc.), or encounters failing Vitest tests and needs help diagnosing them.